nanachatBack to nanachat ↗
NANACHAT FIELD NOTEREAD SLOWLY

Product journey · How it works

Browse or match. Talk when it connects. Return by choice.

nanachat is designed as a sequence of clear decisions, not one long promise. Each step should tell you what has happened and what has not.

Choose an entry

There are two useful starting points. Browse profiles when context matters. Use quick match when you want the product to move faster. Neither path changes the need for a real connection on the other side.

  • →Browse: review the profile information that is actually available.
  • →Quick match: choose an available conversation mode and enter the matching flow.
  • →You can leave either journey when it no longer fits the moment.

Prepare your device

For video or audio, the browser needs permission to use the relevant device. A local preview helps you confirm framing and basic capture before the conversation begins.

  • →Permission granted does not mean connected.
  • →A visible preview does not mean remote media has arrived.
  • →Text, audio, and video options only appear when the product enables them.
Keep in mind

If the browser cannot use your camera or microphone, the help guide explains the most common recovery steps without asking you to weaken device privacy.

Understand the connection state

The matching flow separates preparation, assignment, connection, incoming media, and conversation. That distinction prevents a loading screen from being presented as a successful interaction.

  • →Waiting: the system is still preparing or searching.
  • →Connecting: the room is being established.
  • →Conversation: remote media or messages are actually available to engage with.

Keep a return path

When a conversation is worth remembering, available relationship tools can make it easier to return. Follow, favorite, messages, and call history serve different purposes, and none of them promise a reply.

  • →Follow or favorite for deliberate discovery later.
  • →Use messages when the action is available and you want to continue asynchronously.
  • →Use history to find a previous call context without treating it as a live-status indicator.

Know the paid boundary

If an action leads to a paid product, the offer and checkout are separate from the person you are speaking with. Payment success, wallet or entitlement delivery, and service use are also separate states.

  • →A purchase never guarantees a person, reply, match, or relationship.
  • →Prices, duration, bonuses, and benefits must come from the current server offer.
  • →Do not repeat an unresolved payment until its final state is known.

Questions, answered

What people need to know before they continue.

Do I have to browse before matching?+

No. Browse and quick match are parallel entry paths. Choose the one that suits your current intent.

Will every profile offer the same actions?+

No. Missing fields and unavailable actions should remain hidden rather than being replaced with synthetic information.

What should I do if the connection fails?+

Leave the current attempt, check device and network conditions, and retry only when the interface indicates that the previous attempt has ended.

nanachat

Choose your way in.