Cross-platform: market

Vacancy

an open job that cleared the quality gate and lists at least two technologies

Observed candidate

a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter

Matchable candidate

not counted yet

Window

jobs open at the moment the snapshot was built

Cross-platform mobile is a more accessible entry point than Native (Flutter doesn't require a Mac for an Android-only build). Junior → Middle jump — pick a framework + one state-management + one cloud-backend (Firebase). A Senior is often polyglot — knows Flutter + Native basics. Mobile Architect — cross-platform strategy at the team level, rare-skill premium. Career flow: Junior → Middle (framework pick) → Senior → either Tech Lead in a specific framework, Mobile Architect (cross-platform), or Full-stack (Dart server-side via Shelf/Serverpod).

Top 5 common technologies: react, react native, kotlin, swift, flutter. Native: Swift for iOS, Kotlin for Android, Java for legacy Android. Platform Channels / Native bridges — required for platform-specific features. Mobile architecture patterns: Clean Architecture + feature-module separation + one state-management. Firebase (Google's mobile backend — most common) or AWS Amplify (for AWS-stack teams). Mobile DevOps: Fastlane (CI/CD automation), Bitrise / GitHub Actions / Codemagic (CI). Mobile testing: framework-specific + Firebase Test Lab + BrowserStack App Live for real devices. Mobile analytics: Firebase Analytics, AppsFlyer, Amplitude Mobile. Performance monitoring: Firebase Performance, Sentry Mobile, Datadog RUM Mobile.

Flutter (Dart) — best performance among cross-platform (own Skia/Impeller rendering engine). Dominant in the startup segment + CIS banks (Alfa Mobile). One codebase → iOS + Android + Web + Desktop. Kotlin Multiplatform Mobile (KMM) — JetBrains' approach. Share business logic between Android/iOS in Kotlin, UI stays native (Compose for Android, SwiftUI for iOS). Growing trend in native-Android teams 2024–2026. Premium skill +15-20% over Flutter Senior. React Native (JS) — best for teams with React background. JS-bridge architecture (with New Architecture 2024+ improved). Used by international startups. Strategy: Flutter — startup MVP-first or CIS team; KMM — if you already have a native Android team and want code-sharing with iOS; RN — if React background. A polyglot Senior (knows all three) — the most valuable mobile career for cross-platform Architect.

This role is ideal for: 1) Juniors who haven't yet picked a framework and want to try mobile via a simple entry (Flutter recommended — no Mac needed). 2) Polyglot Seniors who have worked with 2+ frameworks and prefer gigs where you can pick the tool per task. 3) Mobile Architect level — cross-platform strategy for the team (Flutter for a new MVP + native for legacy + KMM for code-sharing). 4) Founding Mobile Engineer at a startup — you pick the stack per product roadmap. Pay is slightly below specialised Native iOS Senior but above Flutter Junior. Career strategy: specialise first in one framework up to Senior, then expand into cross-platform. A Junior who is "cross-platform" from the start risks shallow knowledge across all frameworks.

Yes, 48% of Cross-platform Mobile jobs are full-remote or hybrid. Mobile development is cloud-friendly. Startups — full-remote. Russian product companies — hybrid or remote. Relocant hubs: Dubai, Cyprus, Lisbon, Tbilisi, Bali. English — must for international remote with a +25-40% premium.

General Mobile Engineer (this page) — broad niche for jobs without an explicit framework lock-in. Includes Android/iOS/Flutter developers in a common pool. Good for Juniors who haven't picked a framework yet, or for polyglot Seniors. Specialised pages: Android (Kotlin) — Native Kotlin/Android specific; iOS (Swift) — Native Swift/iOS specific; Flutter — Dart/Flutter specific. If you know your framework — check the specialised page for exact pay + framework-specific Q5/Q6 questions. Mobile Architect — not a specialisation but a career level: designs cross-platform strategy for the team, knows 2-3 frameworks deeply.

Roadmap for a Junior without mobile experience: 1) Pick ONE framework to start. Recommendations: Flutter — the most accessible entry (no Mac needed for an Android-only build, Hot Reload <1s, single codebase). Android Native (Kotlin) — if you want native performance + Compose + ready for the Russian market (banks/product companies require Native). iOS Native (Swift) — if you have a Mac (16GB M-series) and want the premium segment. 2) Get the chosen framework to Junior-Middle level (6-12 months). Details — on the specialised android/ios/flutter roadmap pages. 3) After Senior level — expand into a second framework for a polyglot career. 4) Mobile Architect target — know 2-3 frameworks deeply + cloud-mobile backends (Firebase + AWS Amplify). Courses for the chosen framework — listed on the specialised pages. Time to Junior in any framework — 6-12 months full-time. Cross-platform Senior — 3+ years after Junior.

528 active open Mobile Engineer positions (cross-platform / framework-agnostic). Geography: Russia / remote / Poland. This is a general niche — the pool overlaps with the specialised android/ios/flutter segments. The real market is wider than the sample thanks to the international remote segment. Time to close a Senior — 3-5 weeks.

A Senior Cross-platform Mobile owns the full mobile development cycle + 2-3 frameworks. One framework deeply: either Flutter (see /research/mobile/flutter Senior skills), Native Android (see /research/mobile/android), or Native iOS (see /research/mobile/ios). Second framework at the "read code + add a feature" level: if the first is Flutter — the second is Kotlin Multiplatform or RN; if first is Native Android — second is Flutter or KMM; if first is Native iOS — second is Flutter. Platform Channels / Native bridges: writing native code (Kotlin for Android + Swift for iOS) for platform-specific features from a cross-platform framework. Mobile architecture: Clean Architecture for cross-platform team, modular structure, feature-module separation, state-management strategy choice. Mobile DevOps: Fastlane mastery, Bitrise or Codemagic CI/CD, automated screenshot testing, beta distribution via Firebase App Distribution. Performance: cross-platform performance comparison + profiling tools per framework. Mobile backend services: Firebase deep (Crashlytics + Analytics + Remote Config + Cloud Messaging + Firestore + Auth + Functions) or AWS Amplify. Soft: code review for multiple frameworks, mentoring Juniors in any framework, communication with designers (HIG + Material Design). English for Senior+ must — the mobile community is predominantly English-speaking.