Light Mode Development for Mobile Apps

Light Mode (Light Theme) Development for Mobile Apps

A client recently came to us with a fitness tracker project: a SwiftUI app, 50+ screens, the dark theme was ready, but the light theme simply inherited colors from design mockups without a system. After a month of testing, users complained that text was unreadable in bright sunlight and buttons blended into the background. A typical situation: a light theme is not just inverting colors, but a well-thought-out color system with semantic tokens, contrast relationships, and adaptation for different screens. We took on the project and rebuilt the entire color architecture in 3 days — now the app works on both OLED and LCD screens in various lighting conditions. Over 7 years, we have implemented light mode for 30+ projects, from fitness trackers to banking apps, and semantic tokens have consistently accelerated redesigns by 5–10 times compared to direct HEX values.

Why Semantic Tokens Are the Foundation of a Light Theme

A typical mistake early in a project is using concrete HEX values directly in components. It works initially, but at the first redesign or when adding a dark theme, it turns into a nightmare: 200 places with #F5F5F5 that need to be found and replaced. Direct color assignment is technical debt that dramatically increases maintenance costs.

The right approach is semantic tokens from the start. Token names describe the purpose of the color, not its appearance:

• background.primary — main screen background
• background.secondary — card backgrounds, sidebar
• surface.default — component surfaces
• text.primary, text.secondary, text.disabled
• accent.default, accent.pressed, accent.disabled
• border.default, border.focused

Tokens are stored in a single source of truth — on iOS that's UIColor named colors in Asset Catalog (Color Set with one Light variant now, Dark later). In SwiftUI, we use Color("backgroundPrimary") or a custom extension Color. On Android, use Material Design 3 ColorScheme via MaterialTheme. Flutter — ThemeData with a full ColorScheme. Maintenance time savings with this approach reach 70%.

How to Properly Build a Typographic Scale?

The typographic scale is part of the light theme. Not just "font size", but a full specification: font family, size, weight, line height, letter spacing for each text style. A minimal set includes Display / Large Title, Headline, Body, Body Small, Caption, Overline. Each style should be defined in a single object — for example, Font.TextStyle in SwiftUI or Typography in Material Design.

On iOS, the font scale is built on UIFont.preferredFont(forTextStyle:) — that's Dynamic Type, which automatically scales according to the user's accessibility settings. Ignoring Dynamic Type means breaking the app for people with visual impairments and risking rejection by Apple per App Store Review Guidelines Section 4.2.

How to Ensure Contrast Across Different Screens?

Contrast is a critical parameter for readability. WCAG AA requires 4.5:1 for text up to 18pt and 3:1 for large text and UI elements. For products with a broad audience, we strive for AAA (7:1) where possible without harming design. We check contrast at every stage — from mockups to final build.

Verification tools: Figma plugin A11y - Color Contrast Checker, Xcode Accessibility Inspector, Android Accessibility Scanner. We check not only the main text but also placeholder text in fields (often guilty of low contrast), disabled states, icons, and borders.

Shadows and Elevation: The Invisible Hierarchy

In light mode, shadows are the primary way to show layer hierarchy. Material Design 3 uses elevation + shadowColor. iOS UIKit uses layer.shadowOffset, shadowRadius, shadowOpacity. The mistake is using the same shadow for all components. The rule: 3–4 levels of shadows, from subtle (card in a list) to prominent (modal, bottom sheet). Our engineers tune shadow parameters so they look natural on any screen and don't wash out under different lighting.

Common mistakes when implementing shadows:

• Using a single shadow for all elements (flat hierarchy)
• Too high opacity (shadow looks dirty)
• Ignoring shadowColor on Android (default is black — better to specify a tint)

What's Included in Our Work

When you order light theme development, you get:

• A color design system — a complete set of semantic tokens with documentation and usage examples for iOS (SwiftUI/UIKit), Android (Jetpack Compose), Flutter.
• A typographic scale with specifications for each style, including Dynamic Type.
• Shadow configuration with 3–4 levels and elevation recommendations.
• Contrast checks per WCAG AA/AAA with a report.
• Source files in Asset Catalog / ThemeData — ready for integration.
• Documentation on migration and future dark mode addition.
• Support for two weeks after delivery.

Timelines and How to Start

Estimated time: from 1 to 3 days depending on the app size and whether a design system already exists. The cost is calculated individually after analyzing the current code and mockups. We guarantee that the light theme will pass Apple and Google Play reviews without accessibility issues.

Contact us to evaluate your project. Get a consultation on implementing semantic tokens and a contrast color scheme — this takes no more than an hour.

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.