Mobile: 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

Top-5 technologies in Mobile postings: kotlin, swift, react, java, react native. For iOS: Swift (advanced), SwiftUI (modern UI, 2026 standard) or UIKit (legacy in large codebases), Xcode, Core Data or SwiftData, Combine for reactivity, XCTest. For Android: Kotlin (Java rare in new projects), Jetpack Compose (modern UI) or XML, Android Studio, Room (DB), Coroutines + Flow, JUnit, Espresso. Cross-platform: Flutter (Dart, single codebase) or React Native (JS/TS+React, for web teams).

Depends on your career goal. iOS (Swift + SwiftUI) — premium ecosystem, higher average pay, less competition. Downside: a Mac is required for development. Android (Kotlin + Jetpack Compose) — more open-source projects, easier to land a Junior role, you can develop on any OS. Flutter (Dart) — a growing trend, single codebase for iOS+Android+web, actively used in startups and mid-market products. By job volume: Android > iOS ≈ React Native > Flutter. By pay: iOS ≈ Senior Flutter > Android ≈ Senior RN. A Senior cross-platform specialist (iOS + Android native) — top pay for flexibility.

Yes: 36% of Mobile jobs are full-remote. Mobile development is remote-friendly by nature: code is written in Xcode/Android Studio locally, builds via CI/CD (Fastlane/Bitrise), deployment to App Store/Google Play through web consoles. Especially common at international product companies and startups. Local banks more often require hybrid because of compliance on work with banking APIs. For iOS development a Mac is required (the company usually issues a MacBook on remote). For Android — any OS. Remote pay is often higher than office pay thanks to the international candidate pool, especially for Senior with App Store cases in the portfolio.

Native (iOS-Swift or Android-Kotlin) — separate code per platform. Pros: maximum performance, full access to platform-specific APIs (ARKit, CoreML, HealthKit on iOS; Camera2, ML Kit on Android), native look-and-feel. Cons: 2× the resources to develop, two teams needed. Flutter (Dart) — single codebase, rendering via its own Skia engine. Pros: effective 90%+ code reuse, identical UI on iOS+Android, fast development. Cons: larger bundle size, sometimes does not match native UX patterns. React Native (JS/TS+React) — single codebase, uses native UI components. Pros: a familiar stack for web developers, code can be shared with web. Cons: the JS-to-native bridge sometimes adds a performance penalty. Choice: for a startup MVP — Flutter/RN; for large products with millions of DAU — native.

The optimal path — pick one platform (do not try to learn both at once). Android Kotlin: easier entry, no Mac required, more Junior openings. Learn: Kotlin → Jetpack Compose → Coroutines + Flow → Room (DB) → Retrofit (HTTP) → Hilt (DI) → Firebase. iOS Swift: premium market, Mac required. Learn: Swift → SwiftUI → Combine → Core Data/SwiftData → URLSession → Firebase. Pet project that looks good in interviews: a published application in the App Store or Google Play (not a tutorial clone) that solves a real problem. Bonus — open-source UI library or contributions to popular libraries (Coil, Ktor, Alamofire). Books: Big Nerd Ranch Guides, Hacking with Swift (Paul Hudson). At Middle — architecture (MVVM/MVI), CI/CD (Fastlane), accessibility, performance profiling.

As of the latest data refresh, the Zorky CRM sample contains 2857 active open Mobile positions across CIS and Eastern Europe. These are postings published in the last 90 days — companies actually hiring. Geography is distributed; the leaders are US, PL, IN. Data is collected from 101 job boards and 15 780 company career sites: Telegram channels (especially for niche Flutter/React Native positions), specialised job sites (HH, Habr Career, Djinni, DOU, NoFluffJobs, JustJoin.it, Pracuj.pl), and career pages of major product teams. Mobile is a niche but consistently high-paying specialisation: each major app requires a separate team per platform.

The main driver of the gap is contract currency and company type. iOS pays slightly higher than Android everywhere. Local Russian banks on rouble contracts have closed the gap to the Polish market for Senior Mobile over 2 years. Georgia (Tbilisi) attracts many remote relocants.

A Senior Mobile owns one platform deeply plus architectural patterns. For iOS Senior: Swift (advanced — generics, protocols, async/await), SwiftUI + UIKit (both), Combine, Core Data/SwiftData, XCTest + UI tests, Instruments for performance profiling. For Android Senior: Kotlin (coroutines, flow, sealed classes), Jetpack Compose + XML, Hilt (DI), Room, Retrofit + OkHttp, JUnit + Espresso, Android profiler. Cross-cutting for all: architectural patterns (MVVM, MVI, Clean Architecture), CI/CD (Fastlane, Bitrise), App Store + Google Play publishing, App Store Review Guidelines compliance, Firebase (Auth, Crashlytics, Analytics, Remote Config), accessibility, performance optimisation (memory leaks, app size, launch time). Soft skills: mentoring juniors, design review.