There is a moment in every mockup review where someone says "it doesn't look real yet", and the feedback usually is not about the content. It is about geometry.
If you have ever built a chat interface in Figma, Sketch or a component library, you already know the list of things that make it look fake. Here is that list, in the order that usually matters.
The bubble itself is not a rounded rectangle
A real chat bubble is a shape with at least four independent decisions: the corner radius of each corner, which corner carries the tail, the radius of the tail, and the padding around the text. Get the radius wrong by a few pixels and the bubble reads as "web UI" rather than "app".
The tail is the detail people notice without being able to name it. WhatsApp tails, iMessage tails and Telegram tails are different shapes. A tail that is too wide, too short, or attached to the wrong corner instantly reads as a sticker.
Then there is the grouping rule: consecutive messages from the same sender within a short window group into a single visual unit, with tighter spacing between them than between messages from different people. And the last message in a group often drops its tail entirely, because the bubble sits alone.
Status bar, carrier and clock
Every real phone has a status bar. Most mockups skip it and then look like a floating widget.
The status bar is not decoration either: the clock sits in a fixed position, the signal and battery icons have a specific weight, and the whole bar has a background tint that differs between light and dark mode. On Android it carries the carrier name and sometimes a second icon. On iOS the battery is on the right, on Android on the left.
Get one of these wrong and the screenshot reads as "a design mockup of a phone" rather than "a phone".
Light and dark are different layouts
The most common mistake in mockups is treating dark mode as a color swap. It is not.
A bubble in dark mode has a different radius in some apps, different padding, a different border, and a different shadow, because shadows do not exist on dark surfaces - separation comes from the background tint instead. Text colors, the timestamp gray, the read-receipt blue and the reaction pill all need their own dark-mode values.
If a set of mockups has to work in both appearances, budget for two separate renders, not one render plus a filter.
Timestamps, receipts and reactions
Read receipts live in one of two places: inside the bubble, or below it, and the position depends on the app and on whether the message is the last in the conversation. The color of "Read" versus "Delivered" versus "Sent" is another app-specific value, and mixing them up is instantly recognizable.
Reactions are a pill under the bubble with an emoji and a count, separated from the text by a small gap. They are not round avatars floating next to the message.
Line breaks, links and media
Message bubbles have a maximum width, and long messages wrap. Link previews expand into a card with a title, a domain and sometimes an image, and they sit flush with the bubble's edges rather than inside the text. Voice notes, images and files each have their own inline shape.
One detail that reads as "real": the content inside the bubble is not perfectly aligned to a grid of identical widths. Bubble widths vary with content, which is exactly what makes a real conversation look real.
The practical takeaway
Each of those details is cheap to get right once you know it is there, and expensive to discover one at a time. If you are producing these mocks repeatedly - for ads, product pages, onboarding screens, social posts - the details are worth encoding into a tool rather than re-measuring them per export.
That is the approach behind MockupChat: 16 messaging apps, each skin rebuilt bubble by bubble with its own radii, tail shapes, grouping rules, receipt positions and status bar, in light and dark, exported as PNG or as an animated MP4 from the browser. There is a public REST API and an MCP server if you want to script it, and the format documentation is on the developer page.
How to review a mockup in five minutes
- Look at the tail first, then the corner radii.
- Check the spacing between grouped messages against the spacing between different senders.
- Compare the status bar against a screenshot of a real phone of the same platform.
- Read the receipt colors out loud - sent, delivered, read - and check whether they are the right ones for that app.
- Then look at the content. If it survives that, the rest is copy.
Getting these details right is what turns "a screenshot of a chat" into something people read as a conversation.

