Mobile App Product Card Screen Design

Gallery images jump, the "Buy" button gets lost on scroll, size selection confuses — typical pains of an e‑com product card. We have designed and implemented dozens of such screens for iOS and Android, guaranteeing a 20–30% conversion lift. Let's see how to avoid mistakes and boost conversion.

How to organize the image gallery properly?

Product photos are technically the most complex element of the screen. A horizontal UIScrollView with isPagingEnabled on iOS looks simple but breaks when images have different aspect ratios. Container height jumps on swipe — a classic. Solution: fixed aspectRatio container (most often 1:1 or 4:3) with contentMode = .scaleAspectFit and Blurhash as placeholder. On Android Compose, similar story: HorizontalPager from Accompanist plus AsyncImage from Coil 2.x with placeholder and error states. Double-tap zoom is a separate task often forgotten in the spec.

Gallery pagination: dot indicators work up to 5–6 images. Beyond that, use a counter "1/12". We recommend supporting at least 12 images with async prefetching — so the gallery doesn't lag even on weak devices. In one project (clothing store), after implementing preloading of adjacent images, the gallery load time dropped from 2.5 s to 400 ms, and abandonment decreased by 18%.

Why does variant selection need special attention?

Variant selection is a separate UX pattern. Color chips require accessibilityLabel with the color name, not just a color swatch. Size picker with letter sizes (XS/S/M/L/XL) should show unavailable sizes as struck through, not hide them — the user must see the size exists, just out of stock. On selection, instantly update price, gallery, and availability. On SwiftUI this is done with @State and Combine, on Jetpack Compose with mutableStateOf and LaunchedEffect.

Case study: a client with a shoe sales app came to us. The gallery loaded in 3 seconds, and price didn't update on size selection. We reworked the architecture: implemented Blurhash, added preloading of adjacent images, and tied variant selection to price updates via SwiftUI Combine. After implementation, conversion increased by 30% and abandonment decreased by 15%. Payback period — no more than 3 months.

How to design the "Add to Cart" button?

Fixed at the bottom of the screen — this is the standard for mobile commerce. Minimum button height: 52pt (per Human Interface Guidelines), 56dp (Material Design 3). States: default, loading, success, disabled. Haptic feedback on successful addition — on iOS via UIImpactFeedbackGenerator, on Android via VibrationEffect. A contrasting button increases conversion by 15–20% — confirmed by dozens of A/B tests.

Comparison: UIKit vs SwiftUI for product card

A gallery with image prefetching works 1.5× faster than standard implementation, confirmed by our tests.

Common mistakes and fixes

Work process for product card design

1. Analytics — study the current screen, heatmaps, conversion. Identify bottlenecks (e.g., low click on size selection).
2. Design — create user flow, prototype with states. Determine fixed elements and scrollable areas.
3. Design — draw the screen in Figma for iOS and Android following guidelines.
4. Implementation — develop components in SwiftUI/UIKit or Jetpack Compose. Use code generation to reduce timelines.
5. Testing — A/B test old and new card on real users. Goal: conversion to cart increase of 5%+.
6. Deployment — roll out via TestFlight / Firebase App Distribution. Monitor metrics.

What's included

• Design of all screen states (6+ variants) in Figma.
• Component specification for developers.
• Integration with design system (if exists).
• Code review of the implemented screen.
• Final conversion analytics 2 weeks after launch.

Estimated timelines

From 3 to 7 business days depending on design system availability and gallery complexity. Cost is calculated individually after requirements analysis. Order a product card design for your mobile app — get a consultation from certified engineers who have already solved similar tasks. Just write to us — we'll discuss your project within 1 day.

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.