Ziwwi

A name with possibilities.

Drafting onboarding screens for a chat app

A practical guide to writing the first three screens of a friendly chat app, using a worked example for a small-circle service so that new users know what to do within a minute.

Ziwwi name artwork
Ziwwi.com
Decide the single first action — ZiwwiA conceptual researchidentity

01

Decide the single first action

Before writing any copy, choose the one action a new user should take: usually inviting a friend or joining a group. Everything else can wait. For a small-circle app, the first action might be creating a space and sending one invitation. Write that action as a short verb phrase, such as Start a circle, and let each screen point toward it. Remove screens that explain features users have not yet needed. If you cannot say the first action in one sentence, the onboarding is trying to do too much, and the copy will feel crowded and slow.

Write each screen as promise, proof, prompt — ZiwwiZiwwiProductDescriptorContext

02

Write each screen as promise, proof, prompt

Give every screen three short lines. The promise says what the person gets, the proof shows how it works in plain words, and the prompt tells them what to tap. Worked example: Screen one, promise: Chat with the people you actually know. Proof: Only people you invite can join. Prompt: Next. Screen two, promise: Say it with a sticker. Proof: Tap the face beside the message box. Prompt: Try one. Screen three, promise: Bring your first friend. Proof: Share a link, no sign-up needed to peek. Prompt: Send invite. Keep headlines under seven words and buttons to one or two.

Test tone, permissions and the skip path — ZiwwiA useful path from inputto understanding

03

Test tone, permissions and the skip path

Read the copy aloud to a friend and note where they hesitate or smile. Playful wording should never hide something serious, so ask for notification and contact permissions in plain language and only at the moment they matter, explaining the reason in one sentence. Always offer a visible skip option and a way back, because rushed users abandon forced tours. After a small trial, compare how many people reach the first action, then adjust the screen where they stop. Treat any results as your own findings from testing, and revise one screen at a time so changes stay easy to read.

ziwwi.com

Explore Ziwwi

Held for potential development. Acquisition inquiries may be considered.

Domain inquiry ↗