Mobile App Checkout Screen Development with Payments

Developing a Checkout Screen for Mobile Apps

The checkout screen is where users most often abandon the purchase. A long form with address fields, delivery options, and card entry on a mobile screen becomes a trial if not specifically designed for touch interaction. Our team develops such screens considering all platform specifics — from proper KeyboardAvoidingView handling to Apple Pay and Google Pay integration. Practice shows that up to 60% of users abandon checkout with a poorly designed form. Technically, it is the most complex screen in an e-commerce app: payment integration, real-time validation, keyboard handling, multiple scroll zones. In 5 years on the market, we have delivered over 50 checkout screens for iOS and Android, reducing abandoned cart rates by an average of 30-40%. Our experience ensures compliance with all App Store and Google Play requirements.

Why Checkout Is the Most Complex Screen?

The combination of payment requirements, UX nuances, and performance makes checkout a bottleneck. For example, on iOS you must correctly handle PKPaymentAuthorizationViewController on the main thread, otherwise the app crashes. On Android, you must check IsReadyToPayRequest before showing Google Pay. All fields must validate without blocking input, and the keyboard must not cover the active field. We solve these problems using proven patterns.

How We Ensure Payment Security?

PCI DSS prohibits transmitting raw card data through your own backend. Only tokenization via the provider's SDK is allowed. Apple App Review rejects apps with self-hosted card forms for this reason. We use ready-made SDKs: stripe-react-native or native Stripe SDK, CloudPayments SDK, YooKassa. For each provider, we configure tokenization and 3D Secure. As a result, card data never reaches your server.

Payment Integrations

This is the most labor-intensive part. Each provider has its own SDK with specific requirements.

Stripe — stripe-react-native or native Stripe iOS/Android SDK. The CardField component handles card input with auto-formatting and validation. PaymentSheet is a ready-made bottom sheet from Stripe, minimal customization but maximum reliability. For custom UI, use useStripe().confirmPayment() with a PaymentIntent client secret from the backend.

Apple Pay / Google Pay. On iOS — PKPaymentAuthorizationViewController, in React Native via @stripe/stripe-react-native with useApplePay(). On Android — PaymentsClient from Google Pay API + IsReadyToPayRequest. Both buttons are shown only if the payment method is available on the device — stripe.isApplePaySupported() / paymentsClient.isReadyToPay(). Savings on development using ready-made SDKs can reach up to 20%.

How Payment Integrations Affect Architecture?

Each provider requires its own scenario: Stripe needs a PaymentIntent, CloudPayments requires a cryptogram, YooKassa expects a token. We design a payment layer with an abstract protocol so that switching between providers does not affect the UI. For example, in React Native we use the Provider pattern with a common interface processPayment(token: String). This reduces the cost of modifications when changing the payment gateway.

Form Management

A checkout form typically contains 10–15 fields. Without proper navigation between fields (returnKeyType="next" + ref.focus() on the next input) it becomes unbearable. In React Native Hook Form — Controller + useRef array for fields + automatic setFocus on error after submit.

The keyboard is the main pain. KeyboardAwareScrollView from react-native-keyboard-aware-scroll-view works better than the standard KeyboardAvoidingView: it automatically scrolls to the active field and correctly handles height changes on orientation change.

On iOS, numeric fields (postal code, CVV) must open UIKeyboardType.numberPad. decimalPad for amounts. emailAddress for email. The wrong keyboardType is a small detail that all users notice but don't mention aloud.

Validation and UX

Real-time validation is only for fields with a deterministic format: phone, email, postal code, card number. For text fields (name, address) — only on blur (onBlur), otherwise an error like "invalid name" appears on the third letter.

Address autocomplete via Google Places Autocomplete API or Dadata API (for Russia) is a must. Manually entering street, house, and apartment in separate fields increases input time by 3-4 times and delivery errors. Autocomplete reduces form fill time from 3-4 minutes to 30 seconds and cuts delivery errors by 25%.

From practice: a delivery app, React Native + Stripe. When paying with Apple Pay on a physical iPhone XR, the app crashed with NSException immediately after authorization. The cause — PKPaymentAuthorizationController was called from a background thread. Moving it to DispatchQueue.main in the native module solved the problem. The React Native bridge does not guarantee the main thread for callbacks.

Why Is Real-Time Validation Critical?

The user expects instant feedback. If the error is shown only after pressing "Pay", they have to fix multiple fields at once, increasing the likelihood of abandonment. We implement validation on input for fields with a clear format, and for others after losing focus. This improves conversion by 10-15%.

Multi-Step Checkout

For a long checkout we use a stepper (steps: address → delivery → payment → confirmation). Each step is a separate component with its own validation. State is stored in a single store, not passed via props between screens. A ProgressBar on top shows the current step.

The "Back" button must preserve already entered data — do not reset the form when returning to a previous step.

What's Included in the Work

• Address form with autocomplete (via Places API)
• Delivery method selection with cost and time estimation
• List of saved user addresses
• Payment provider integration (Stripe, CloudPayments, YooKassa, and others)
• Apple Pay / Google Pay with availability check
• Real-time validation + API error handling
• Order confirmation screen with number and details
• Storage of last used address and card
• Integration documentation and post-release support

Timeline and Cost

3–5 business days — depends on the number of payment providers, complexity of discount logic, and address validation requirements. Integration of one provider with Apple Pay/Google Pay takes 2–3 days. Cost is calculated individually. We will assess your project for free — contact us to discuss details. Get an engineer's consultation and an accurate timeline estimate today.

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.