Dynamic Themes for Mobile Apps

Why users abandon apps due to theme issues

Users expect the app to adapt to their preferences: dark theme in the subway, accent color matching the phone wallpaper, at least two modes. If theme switching has a delay or flash, the user leaves. We've seen projects where implementing themes took 3 months and resulted in 5 buggy screens. Over 10 years we've developed an architecture that works on all platforms and doesn't tolerate mistakes. One common problem is the flash of wrong theme: on first launch, the screen flashes light theme, then switches to the saved dark theme. This happens if the theme is read asynchronously. On iOS it's solved by synchronous reading of UserDefaults in AppDelegate, on Android via SplashScreen API. Proper implementation eliminates this effect and retains the user.

Contact us for an estimate of your project — we will analyze your current architecture and propose the optimal solution.

Architecture of the theme system

The key decision is how to store the current theme and how to pass it to components.

iOS (SwiftUI)

We use @Environment + custom EnvironmentKey. Create AppTheme as ObservableObject, publish via environmentObject, all components read via @EnvironmentObject var theme: AppTheme. When theme.colorScheme changes, SwiftUI automatically redraws the entire tree. Switching is instant, without UIApplication.shared.windows hacks.

iOS (UIKit)

More complex: UIAppearance proxy for global settings + traitCollection override. Or a custom ThemeManager via Notification Center: on theme change, all subscribed components call applyTheme(). Downside: need to explicitly unsubscribe, easy to get retain cycles.

Android (Compose)

MaterialTheme(colorScheme = currentColorScheme) in the root of composition. CompositionLocalProvider(LocalAppTheme provides theme). When remember { mutableStateOf(lightColorScheme) } changes, Compose re-composes only the subtrees that read the theme. Very efficient.

React Native

ThemeContext via React Context API + useContext. Or a ready-made solution via styled-components/native with ThemeProvider. On theme change, all components subscribed to the context re-render. To prevent unnecessary renders: React.memo + useMemo for the theme object.

Flutter

MaterialApp(theme: lightTheme, darkTheme: darkTheme, themeMode: themeMode). Custom themes — ThemeExtension<T>. ThemeMode.system / .light / .dark managed via setState or Provider/Riverpod.

How to ensure theme persistence without restart?

The chosen theme needs to be saved. iOS: UserDefaults + @AppStorage in SwiftUI. Android: DataStore<Preferences> (recommended over SharedPreferences). React Native: AsyncStorage or MMKV for synchronous access. Flutter: SharedPreferences or Hive.

Critical point: on first launch, the theme must be applied before the user sees the first frame. Otherwise there will be a flash of wrong theme — the screen flashes from the default theme to the saved one. On iOS it's solved by synchronous reading from UserDefaults in AppDelegate / @main before the window is drawn. On Android — via SplashScreen API with the correct background color. We guarantee the absence of this effect.

How to avoid memory leaks when switching themes?

With active theme switching, it's easy to create many subscriptions and listeners that are not cleaned up. On iOS we use Combine with AnyCancellable and store(in: &cancellables), on Android — Flow with collect in lifecycleScope. We test on 10+ devices, checking for leaks via Instruments and Android Profiler. The savings on debugging can be significant — preventing bugs early pays off the investment.

How to implement dynamic themes: step-by-step plan

1. Audit the current UI: identify all places where colors, fonts, icons are used. Determine which components need adaptation.
2. Design the palette: define a set of colors (primary, secondary, background, surface, error) for light and dark schemes. If a custom accent is needed, plan generation from a seed color.
3. Choose the storage mechanism: based on the platform, select persistent storage (UserDefaults, DataStore, AsyncStorage, SharedPreferences). Ensure reading happens synchronously before the first frame renders.
4. Implement on the platform: integrate the theme system according to best practices (Environment, Context, ThemeProvider). Write tests to verify correct theme switching without flashing.
5. Test on 10+ devices: check on different OS versions, with different settings (System theme, accessibility). Use Instruments / Android Profiler for memory leaks.

How to test theme switching?

Test that reveals most issues: open a screen with complex UI → switch theme 5–10 times quickly → ensure no flash, no memory leaks (Instruments / Android Profiler), and all colors are applied correctly. Special attention: UIAlertController, UIActivityViewController, system components on iOS — they don't always react to custom themes and require separate handling.

Testing checklist for dynamic themes:

• Check switching light/dark theme on the main screen and all child screens.
• Switch theme rapidly 10 times in a row — no memory leaks, no flickering.
• Ensure system components (ActionSheet, ShareSheet) use the correct theme.
• Verify theme persistence after app restart.
• Test with Material You (Android 12+) — should pick up colors from wallpapers.
• On iOS — check with Dark Mode active in the system and without.

Custom accent color

Android 12+ supports Material You — a dynamic palette is generated from the user's wallpaper via DynamicColors.applyToActivitiesIfAvailable(this). Result: the app automatically adapts colors to the phone's personalization. Palette generation takes less than 5 ms, which is 10 times faster than custom color processing.

For a custom color picker inside the app: you need to generate a full ColorScheme from the selected seed color. On Android this is dynamicDarkColorScheme / dynamicLightColorScheme (API 31+) or the material-color-utilities library for API <31. On iOS — manual calculation of derived colors via HSL.

Common mistakes when implementing themes

What's included in dynamic theme development?

• Analysis of current app architecture
• Design of the theme system (palette, storage and propagation methods)
• Implementation on the chosen stack (iOS/Android/Flutter/RN) following best practices
• Integration of theme saving and restoration
• Testing on 10+ physical devices and emulators
• Documentation for maintenance and further development
• 30 days of free support after delivery

Developing dynamic themes is an investment that quickly pays off through increased user retention. Order dynamic theme implementation — and we'll ensure a seamless transition. Get 30 days of free support and consultations. Our team has 10+ years of experience in mobile development and Apple and Google certifications.

Additional information: Human Interface Guidelines — official Apple recommendations for working with color.

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.