Mobile Applications Developer (Flutter / Android / iOS) interview questions

I've been doing mobile development for six years, three in Oman. Started with native Android in Java at an Indian app studio, transitioned to Flutter around 2021, and for the past three years I've been senior mobile developer at an Omani digital banking team. My current stack is Flutter for cross-platform plus native iOS (Swift) and Android (Kotlin) modules for platform-specific features (biometric auth, native payment integrations). I've shipped two major banking apps from concept through to App Store and Play Store presence with combined 200K+ active users.

Layered approach. Local widget state for UI-only concerns (form fields, modal open/closed). Provider or Riverpod for app-wide state that crosses multiple screens. For server state I use Riverpod's async providers or a separate Repository pattern with caching. I avoid putting too much state in one provider; small, focused providers are easier to reason about. State should live as close to where it's used as possible. Bloc is fine for some teams but I find it heavier than I need for most apps.

Layered. Unit tests for business logic (calculations, validations). Widget tests for UI components in isolation. Integration tests with patrol or flutter_driver for critical user journeys (login, transaction, payment). Manual exploratory testing on physical devices across iOS and Android, multiple screen sizes. I run unit tests on every commit, integration tests nightly. Coverage target around 70% for business logic, lower for pure UI. Mobile testing is harder than web; emulators don't catch device-specific issues.

Use a proper routing solution (GoRouter for Flutter, or platform routers for native). All deep links defined as routes with parameter parsing. Universal Links on iOS and App Links on Android configured for our domain so the browser can hand off to the app. Authentication state handled at the router level; deep links to authenticated screens redirect through login if not authenticated and resume after. Test deep links from various entry points (push notification, web link, copy-paste URL) because each has subtle differences in how the OS hands them to the app.

Mobile teams often blame backend, and vice versa; I try to bridge that. I attend backend planning when API changes affect mobile, contribute to API design (mobile-friendly response shapes, batched endpoints to reduce round-trips). I provide clear bug reports with full reproduction steps including network traces, not just 'doesn't work'. I treat backend devs as partners. The mobile experience depends as much on backend quality as on mobile code; the relationship matters.

For a senior mobile developer role in Oman fintech I'd target OMR 1,500 to 1,900 total package depending on the project mix and platform breadth. Roles requiring true native depth alongside cross-platform pay more. I'm on 60 days' notice. Beyond pay I care about the app quality I'd be working on; shipping a banking-grade app is a different challenge from internal CRUD apps.