Adapting Mobile App Design to Any Screen Resolution

Mobile design made for a single screen size — iPhone 15 Pro 393×852pt — is half the job. In reality, the app runs on iPhone SE with 375×667pt, on Android budget devices with 360×640dp, on flagships with 430pt width. A layout that looks perfect on a designer frame cuts off buttons on small screens and leaves empty spaces on large ones. We face this every day: a client sends a Figma file with one size, and tests reveal that the "Buy" button slides under the Tab Bar. This leads to App Store Review rejections and loss of conversion.

How Design Adaptation for Different Screens Is Done

Adaptation of mobile app design starts with an audit of current layouts. We identify problem areas: content overflow, unaccounted Safe Area, unreadable typography. Then we create control frames for 3–4 key sizes and adjust margins, image scales, and column count. The result is a Figma file with configured Auto Layout and a guide for developers.

What Exactly We Adapt

Key breakpoints are not sizes but proportions. iPhone SE screen with 16:9 vs iPhone 15 Pro Max with 19.5:9 — significant difference. Bottom-anchored elements (Tab Bar, floating buttons, sticky footer in forms) must work correctly on both. Safe Area is a separate story. On iPhone with Dynamic Island — 59pt on top. On iPhone without notch (SE 3rd gen) — 20pt. On Android, notch varies or is absent. Content that "sticks" to the status bar without considering Safe Area is guaranteed to get a App Store Review rejection.

Typography on small screens: text at 16sp is readable on a 6-inch display, but on a 4.7-inch screen at 326 ppi — borderline. Minimum size for body text on mobile — 14pt/sp, and this is not a recommendation but a practical minimum for most fonts. We use dynamic typography: on small screens, headings decrease by 2pt, on large screens, increase.

How to Adapt for iOS and Android Simultaneously?

Approaches differ. iOS uses Auto Layout with ratios (Aspect Ratio, Multiplier), Android uses ConstraintLayout with percent or Guideline. We design in Figma using Auto Layout and Constraints, then prepare separate guides for each platform. In practice, Auto Layout in Figma + SwiftUI Layout is better than frames with hard constants — difference in adaptation speed up to 50%. For Android we use Jetpack Compose with Modifier.fillMaxWidth() and Modifier.weight(), but testing on real devices is still mandatory.

How We Format Adaptation in Figma

We create frames for control sizes:

Each key screen is checked on the extreme sizes. Not all 50 screens — only those with content overflow, Bottom Sheet, complex forms, fixed-height images. Additionally, we prepare layouts for the widest and narrowest screens so developers see the boundaries.

Comparison of Approaches: Auto Layout vs Adaptive Layouts

Why Auto Layout Isn't Enough?

Auto Layout doesn't scale images, doesn't change column count in a grid. On iPhone SE, product cards in 2 columns turn into 1 column — this must be accounted for in design. We use adaptive layout with breakpoints: on width up to 375pt — one column, up to 430pt — two, above — three. This requires separate handling of each screen, but the user won't see "truncations".

What's Included in the Work

1. Audit of current layouts for adaptation issues (Safe Area, overflow, typography).
2. Creation of control frames for 3–4 sizes (iOS + Android).
3. Adjustment of margins, alignment, image scales.
4. Preparation of a developer guide with constraints and notes.
5. Testing on real devices (we have a fleet of 15+ devices).
6. Final Figma file with configured Auto Layout and variables.
7. Consultation with the development team on layout.

We work with design at all stages: from design to handoff to development. 5+ years of experience, over 20 completed projects for iOS and Android. We guarantee that after our adaptation, there will be no rejections under Section 4.2 of App Store Review and Google Play Console.

Work Process

• Analysis: study current layouts and identify problem areas.
• Design: create control frames and adaptive variants.
• Implementation: adjust elements and prepare guide.
• Test: check on real devices and simulators.
• Deploy: hand off the Figma file and guide to developers.

Estimated Timeframes

Adaptation of existing design for 3–4 control sizes (key screens, not full project) — from 1 to 3 business days. Full adaptation of entire project (up to 50 screens) — from 5 to 10 business days. Cost calculated individually, depends on number of screens and complexity. We will assess your project for free — just contact us.

Get a consultation on adapting your mobile app design. We help avoid common mistakes: incorrect Safe Area calculation, ignoring screen proportions, unreadable typography. Order design adaptation — your product will look perfect on any screen.

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.