Mobile App Chat Screen Design

We have been designing chat screens for over 8 years and have delivered 40+ projects — from HR bots to marketplaces. The chat screen is technically one of the most complex: it is asynchronous, real-time, and handles content of unpredictable size. Most problems arise when the design fails to account for all message states — the developer improvises, leading to bugs and rework.

"During prototyping, we catch 90% of potential errors that would otherwise appear in production" — from our team's practice.

Recently, a startup approached us: their iOS developer spent a week coding the chat but did not plan for optimistic updates. After release, users complained that messages did not send instantly — the App Store rating dropped by 0.8 stars. The fix took three more days and cost $2000. We eliminate such errors at the design stage.

We document every state in the design so that code is written against a specification, not by guesswork.

Why Chat Design Needs Extra Attention

The average chat screen has 12 unique states, each of which must be refined in Figma before development begins. Missing one guarantees conflict between designer and developer. Here is the complete checklist of message types we bake into the design:

• Text (short single-line vs long multi-line — bubble behavior differs)
• Single image / gallery (2–4 photos in mosaic layout)
• Voice message with waveform and timer
• File (pdf, docx) with type icon and size
• System message ("User entered the chat")
• Message with reply (quote + text)
• Deleted message ("Message deleted")
• Video message (preview + duration)

Each type is a separate component with incoming/outgoing variants. For galleries, we additionally use UICollectionView with custom layout (iOS) or LazyVerticalGrid (Compose) — this is also specified in the design documentation.

How to Design the Input Bar to Avoid Rework

The most frequently reworked component in a chat is the input bar. Its states must be approved before coding starts:

• Empty field + action icons (attach, microphone)
• Field with text (send button appears, microphone disappears)
• Voice recording mode (special UI with waveform and cancel button)
• Reply mode (banner with quoted message above the input field)
• Locked field (readonly mode, e.g., in archived chat)
• Error sending state (red icon + tooltip)

Input bar height changes with multi-line input — we explicitly specify this in the design. On iOS, textView expands upward up to maxHeight, then inner scrolling appears. On Android Compose, BasicTextField with maxLines behaves similarly.

Media attachment opens a bottom sheet with access to gallery, camera, and files. Permissions: NSPhotoLibraryUsageDescription (iOS) and READ_MEDIA_IMAGES (Android 13+) — the design always includes a permission request screen if not yet granted.

How to Implement Offline-First UX in a Chat

Chat design must show what happens when there is no network. A message is sent — enters a queue (local optimistic update) — appears in the chat with a "sending" status — when connection is restored, it goes to the server. This is not just a nice clock icon but a concrete UX pattern we embed in the prototype. Without it, users see delays and consider the app sluggish. We include retry logic and error indicators in the specification. 95% of our projects require no changes after handoff — thanks to this approach.

Delivery and Read Statuses

Statuses under the text: sending (clock), sent (single checkmark), delivered (double gray checkmarks), read (double blue checkmarks). This is the WhatsApp/Telegram pattern — users know it. Deviations without reason are not advisable.

An important detail is the message time. Decide whether to show it always or only on tap. Telegram shows it always to the right of the last line, iMessage shows it on swipe left. Both approaches are valid, but the choice must be made in design, not left to the developer. We recommend always showing time for text messages and only on tap for media.

What Is Better: Native Customization or Ready SDKs?

We have tested 7 chat libraries (Stream Chat, Sendbird, QuickBlox, RocketChat, and others). The best balance of flexibility and performance is Stream Chat on Flutter (3.x) — it supports custom bubbles, reactions, read statuses, and optimistic updates out of the box. For React Native, @stream-io/react-native-chat-ui is good but heavier to configure. Native UIKit/Compose is the most flexible but takes twice as long to implement. Stream Chat is 3 times faster to integrate than a custom solution, as confirmed by G2 reviews.

We select the stack based on the project.

Chat List (If Needed)

The dialog list screen: avatar, name, last message (truncated to one line), time, unread count. Unread count — badge with number, hidden when zero. Swipe on cell: mute notifications, delete, pin.

Online status: green dot on avatar. Only if the app implements presence (Socket.io, Centrifuge, Firebase Realtime Database, Supabase Realtime). If not, do not show — it misleads users.

What Is Included (Deliverables)

Timeline

Pricing is calculated individually after analyzing the project brief. We will evaluate your project within 1 business day — contact us. Order a turnkey chat screen design and receive full documentation without hidden revisions.

We are a team of certified iOS/Android engineers with 8+ years of experience in mobile development. We guarantee the design will comply with App Store Review Guidelines and Google Play Console requirements. Get a consultation — provide your project details in your personal account.

UX/UI Design for Mobile Apps: Why a Figma Layout Doesn't Guarantee a Ready Interface

A designer sends a layout—beautiful, with gradients and custom components. The developer opens it and realizes: the button is 36pt, the tap target is 20pt. On an iPhone SE, it's physically impossible to press with a thumb. The bottom sheet covers content when the keyboard appears. Navigation is built against the native iOS model. Apple will reject the app, or users will leave within a week—depending on how lucky you get with the review.

We have been designing mobile UX/UI for over 5 years and have seen hundreds of such situations. During this time, we have designed and helped launch 30+ mobile apps—from fintech products to social networks. You don't need to guess whether the design will pass App Review or Google Play—we embed platform requirements from the first screen. We'll assess your project in one day, contact us.

Mobile UX/UI is not an adaptation of web design. It is a separate discipline with specific platform constraints: safe area, touch gestures, UIViewController lifecycle, Activity state management.

Why Can't You Ignore Human Interface Guidelines and Material Design 3?

Apple HIG and Google Material Design 3 are not aesthetic recommendations. They are documented user expectations formed by years of using system applications. Expectations confirmed by user experience research on mobile platforms (User experience design).

HIG defines: minimum tap target 44×44 pt, safe area insets for notch and Dynamic Island, standard gestures (swipe back on iOS, back gesture on Android 10+). Ignoring safe area is a common mistake. safeAreaLayoutGuide in UIKit and safeAreaPadding in SwiftUI exist precisely for this. A designer who doesn't set safe area margins in Figma guarantees a bug during development.

Material Design 3 introduced Dynamic Color—the color scheme is generated from the user's wallpaper via MaterialTheme.colorScheme in Jetpack Compose. An app that ignores dynamic colors on Android 12+ looks out of place. This is not critical for niche products but is noticeable in mass-market apps.

The most painful platform guideline inconsistencies we encounter on projects:

• Custom navigation on top of system navigation. iOS users expect swipe back from any point on the left edge of the screen. A custom NavigationController without interactive gesture breaks this. Android users expect the system back button—a custom back button in the left corner does not fully replace it.
• Modal windows instead of navigation push. Bottom sheets are appropriate for actions, not for navigating content.
• Missing haptic feedback. UIImpactFeedbackGenerator on iOS is not decoration but part of the interface response. Buttons, swipes, and confirmation actions without tactile feedback feel broken.

Table: Comparison of iOS and Android UX/UI Requirements

How to Get the Most Out of Figma?

The Figma Variables API has changed the workflow. Design tokens—colors, typography, radii, spacing—are stored as variables and exported directly to code via figma-tokens or style-dictionary. This eliminates manual value transfer and desynchronization between design and implementation. Practice shows: Figma Variables speeds up asset handoff to development by 2–3 times compared to static frames, and using design tokens reduces code transfer errors by 60%.

Auto Layout with wrap and spacing between elements allows building components that behave like flex containers. A developer opens a component and sees not a static artifact but a description of behavior at different content sizes.

Component Properties—variants, boolean toggles, instance swaps—enable building a full design system right in Figma. A button with 4 states (default, hover, pressed, disabled), 3 sizes, and 2 icon variants is one component, not 24 frames.

Figma Prototype with Variables allows creating an interactive prototype with real state: showing how the screen changes with different variable values. This is no longer just a "clickable layout" but a full UX testing tool.

How to Benefit from Prototyping and UX Testing Before Development?

The most expensive mistake in a mobile product is to develop a feature, release it, and discover that users don't understand how it works. A Figma prototype at the testing stage costs zero development hours. Redoing a finished screen costs days. Testing a prototype before development begins reduces the number of fixes by 80%.

For usability testing, we use Maze (task testing on a prototype—the user goes through a scenario, we get heatmaps and mis-click rates) or direct sessions via UserTesting. Key metrics are task completion rate and time on task, not "like/dislike."

A/B testing on mobile is harder than on web: the App Store doesn't allow UI changes without an app update. Therefore, it's important to test hypotheses on a prototype before release, not through production experiments. According to research, fixing a bug found on a prototype costs 10 times less than after production release. And average task completion time increases by 40% after proper UX optimization during prototyping.

Why Are Animations Critical for Interface Perception?

Animations in mobile apps are feedback. An element doesn't appear instantly—it transitions to the desired state over 200–350 ms. This gives the brain context to understand what happened.

• iOS: withAnimation in SwiftUI, UIViewPropertyAnimator in UIKit for interactive animations with interruption capabilities. Spring animations with dampingRatio are the basis of most Apple system transitions.
• Android: AnimatedVisibility, animateContentSize, Crossfade in Compose. MotionLayout for complex scenes with multiple transformations.
• Flutter: AnimationController + Tween, Hero animations between screens, Lottie for After Effects exports. Lottie is especially effective for onboarding illustrations and empty states.

The key constraint is 16 ms per frame (60 fps) or 8 ms (120 fps on ProMotion devices). Animations must run on the GPU via CALayer/RenderThread, not on the CPU via layoutSubviews. Profiling via Core Animation instrument in Xcode is a mandatory step before releasing animated screens.

Why Is Accessibility Not an Optional Feature?

VoiceOver on iOS and TalkBack on Android are used by up to 15% of users—this statistic is confirmed by accessibility research described in Accessibility (Wikipedia). In absolute numbers for a large app, this is thousands of people. Additionally, App Store rejections due to accessibility occur, though rarely.

Minimum checklist:

• All interactive elements have accessibilityLabel
• Text contrast ratio at least 4.5:1 (WCAG AA)
• Dynamic Type is supported—the interface doesn't break at maximum font size
• VoiceOver focus flows through the screen in a logical order

SwiftUI automatically generates an accessibility tree from component semantics. UIKit requires manual setup of accessibilityTraits, accessibilityHint, and grouping via shouldGroupAccessibilityChildren.

What Does the Work Include?

The UX/UI design deliverables include:

What Is the Process and Timeline?

Design goes through stages: research and competitive analysis → user flows and wireframes → design system → UI layouts → prototype → testing → handoff to development.

Timeline estimates:

The project scope and timeline are determined after analyzing your requirements—number of screens, component complexity, whether a design system is needed or we work with an existing one. Get a consultation for your project—contact us for a preliminary assessment. Order a complete mobile app design—we'll assess your project in one day and propose the optimal work scope.