3 min
A ChatGPT-style chat: composer, drawers, orbs
ChatGPT is the one people send me most. I look for the composer, the drawers, and the orbs that show up while it thinks.
You want a chat app that looks like ChatGPT. Composer. Drawers. Thinking orbs. Those are three different screens wearing one app icon, and I keep them together in the Chat facet.
React Native ChatGPT is the most asked topic I get
Not a chatbot API. The product on the phone. If you are building an AI chat app, this is the screenshot people send. The model behind it changes every few months. The three surfaces below do not.
A composer is not a text field
The bar at the bottom is the product for half a second. Plus. Photos. Files. Send. It has to sit on the keyboard and still look like ChatGPT. A login TextInput is not this job.
While a reply is streaming, send goes quiet. Attachments still have to work. Voice still has to be one tap away. The ChatGPT inspired chat composer is the piece to watch first, because it grows with the message while the keyboard moves under it.
That second part is its own problem, and the keyboard write-up covers why the button and the field have to move separately. Get the composer wrong, and nothing else in the clone matters.
Drawers hold the other chats
ChatGPT is not one thread. It is a list of them. A drawer you pull from the side. A row you swipe away. History you can find again when the new chat is a mess.
Skip the drawer and you have a demo. One conversation. No memory of the last ten. People notice that before they notice your bubble radius.
The thread is an inverted list
The messages themselves are the part people underestimate. A chat starts at the bottom and grows up, so most React Native chat screens render the thread as a FlatList with inverted set. Newest message at index zero, scroll anchored to the composer, older history loading as you scroll up. A normal list fights you on every one of those.
Streaming makes it harder. The last bubble keeps changing height while the reply arrives, half a code block at a time. If the list re-measures every row on each token, the scroll jitters. Keep the streaming bubble its own component and let the rest of the thread sit still.
Thinking orbs are their own screen
The orb is not a spinner inside a bubble. Voice mode. Thinking. A fluid thing sitting in the middle of the phone. People remember that motion more than they remember the markdown. The ChatGPT voice profile fluid orbs are a good one to watch with that in mind.
A good ChatGPT-like chat app has that surface. It is a different stack from the thread, often a shader or a canvas rather than a view. Skip it, and the clone feels unfinished even when the bubbles are perfect.
Build it in the order people notice
Composer, then drawer, then orb. If your app is not a ChatGPT clone but a chat with Claude, Gemini, or Grok behind it, the chat UI post splits what those apps share and where they differ.