Question 1

How do you handle state persistence, rehydration, and migration in a mobile app that needs to survive process termination and support app version upgrades?

Accepted Answer

Mobile applications face a unique challenge: the operating system can terminate your process at any time to reclaim memory, and users expect to return to exactly where they left off. Handling state persistence, rehydration, and migration across app versions requires a deliberate architecture.

State persistence begins with deciding what to persist. Not all state should survive process termination. Authentication tokens, user preferences, cached API responses, and in-progress form data are good candidates. Ephemeral UI state like scroll positions or animation progress typically is not worth p

Question 2

Explain the Provider pattern in Flutter and how it simplifies state management compared to passing data through constructors.

Accepted Answer

Provider is one of Flutter's most widely adopted state management solutions. It builds on top of InheritedWidget to offer a clean, declarative way to supply data down the widget tree without manually threading it through every constructor.

Without Provider, if a deeply nested widget needs access to a piece of data owned by an ancestor, you would have to pass that data as a constructor parameter through every intermediate widget. This is called prop drilling. It creates tight coupling between widgets that do not actually use the data and makes refactoring painful because changing the shape o

Question 3

Describe the process of migrating a React Native application from the old bridge architecture to the New Architecture with Fabric and Turbo Modules. What challenges should you anticipate?

Accepted Answer

Migrating to React Native's New Architecture is a significant undertaking that affects native modules, native components, and build configuration. The New Architecture introduces Fabric for rendering and Turbo Modules for native module communication, both powered by JSI. Planning the migration carefully prevents extended periods of instability.

The migration starts with an audit of your current native dependencies. List every native module and native component your application uses, both first-party and third-party. For each one, check whether a New Architecture compatible version exists. T

Question 4

What is a platform channel in Flutter, and why would you need to use one?

Accepted Answer

A platform channel in Flutter is the mechanism that allows Dart code to communicate with native platform code written in Swift, Objective-C, Kotlin, or Java. It provides a bridge between the cross-platform Flutter layer and the underlying iOS and Android operating systems.

The need for platform channels arises because Flutter's Dart runtime does not have direct access to all platform-specific APIs. While Flutter provides plugins for many common tasks like camera access, file picking, and location services, there are situations where you need to interact with APIs that no existing plugin cov

Question 5

What is lazy loading in mobile applications, and how does it improve performance?

Accepted Answer

Lazy loading is a strategy where resources, components, or data are loaded only when they are actually needed, rather than at application startup. This defers work to the point of use, improving startup time, reducing initial memory consumption, and making the application feel more responsive.

The concept applies at multiple levels in a mobile application. At the code level, lazy loading means splitting the application bundle into chunks and loading them on demand. Instead of downloading and parsing all JavaScript or loading all Dart isolate code at launch, only the code required for the in

Question 6

What does it mean for a mobile application to run at 60 frames per second, and why is this target important for user experience?

Accepted Answer

Running at 60 frames per second means the application renders a new visual frame every 16.67 milliseconds. This target matters because it is the threshold at which motion appears smooth to the human eye. When frames take longer than 16.67ms to render, the application drops frames, causing a visible stutter that users perceive as jank.

Most mobile displays refresh at 60Hz, meaning they update the screen 60 times per second. Some newer devices run at 90Hz or 120Hz, which tightens the frame budget to 11.1ms or 8.3ms respectively. But 60fps remains the baseline that all mobile applications shou

Question 7

How do you set up and manage code signing for both iOS and Android across a development team and CI/CD environment, and what are the common pitfalls?

Accepted Answer

Code signing is the process of cryptographically verifying that an application was built by an authorized developer and has not been tampered with. Both iOS and Android require signed binaries for distribution, and managing signing credentials across a team and CI environment is one of the most error-prone aspects of mobile development.

On iOS, code signing involves three components: a signing certificate that identifies the developer or organization, a provisioning profile that links the certificate to specific app IDs and device UUIDs, and an entitlements file that declares the app's capa

Question 8

What are the different levels of testing in a mobile application, and what does each level verify?

Accepted Answer

Mobile application testing follows the testing pyramid, where each level trades speed and isolation for realism. Understanding all three levels helps you build a test suite that catches bugs efficiently without being slow or brittle.

Unit tests form the base of the pyramid. They test individual functions, methods, or classes in complete isolation from the UI, network, and platform. Examples include testing a date formatting utility, a shopping cart calculation, a state management reducer, or an API response parser. Unit tests are fast because they run without a device or emulator, require n

Question 9

Design the data architecture for an offline-first mobile application that supports a product catalog with thousands of items, user-generated content, and image assets available offline.

Accepted Answer

Designing a data architecture that supports a large product catalog, user content, and offline images requires layered storage with intelligent sync and caching strategies. The architecture must balance data freshness, storage limits, and user experience across varying connectivity conditions.

The data model separates into three tiers based on ownership and sync characteristics. The first tier is the server-authoritative catalog: thousands of products with descriptions, prices, categories, and metadata. This data is read-only from the client's perspective and changes infrequently per item,

Question 10

What does it mean for a mobile application to be "offline-first," and why is this approach important?

Accepted Answer

An offline-first mobile application is designed to function fully or partially without an active network connection. Instead of treating offline mode as an error state, the application treats it as the default state and synchronizes with the server when connectivity becomes available. This fundamentally changes how you architect data flow, storage, and user interactions.

The importance of offline-first stems from the reality of mobile usage. Users interact with their phones in elevators, subways, airplanes, rural areas, and buildings with poor reception. Even in areas with cellular coverage

Mobile Developer

Topics

Advanced State Management

Native Modules & Platform Bridges

Mobile Performance Optimization

Mobile Testing & CI/CD

Offline-First & Local Storage

Mock Interview

Quick Stats