Who & why
Builds apps for iOS and Android — native (Swift/Kotlin) or cross-platform (Flutter/RN). Delivers a fast, smooth, native-feeling experience accounting for the mobile world: offline, push, battery, varied screens, strict store rules. Without proper expertise: lag, battery drain, breaks offline, fails store review, ignores HIG/Material.
A day in the life
Morning: design the screen & navigation to platform guidelines, plan offline, write a logic test. Day: build UI & logic, wire platform APIs (camera/push/geo), set up sync/cache, test across devices/OS versions, profile perf & battery. Evening: triage crash logs, build, update store config & listings, pass review.
Key skills
Hard: platform (Swift+SwiftUI / Kotlin+Compose) or cross (Flutter/RN), navigation & gestures, offline & local storage, push, background tasks, store releases (signing, review), perf & memory, testing. Soft: mobile UX detail, patience with fragmentation, release discipline, reading crash logs.
Artifacts
App code, tests, build config, store release notes. Implements against the User Story; releases pair with the Release Manager (store review as an extra step).
How AI / vibe-coding boosts the role
Screen generation; platform-API help; crash triage; store listing; offline strategy — with ready prompts.
Growth: Junior → Middle → Senior → Lead
Junior: screens by example. Middle: full features, owns offline/push/releases. Senior: mobile architecture, perf/battery optimization. Lead: mobile architecture & quality for the team.
Common mistakes
"Website on a phone"; ignoring offline & network states; testing only on your device; battery/memory drain; store-review surprises.
What to learn
App lifecycle, navigation, offline/sync, push, HIG/Material, publishing process, perf/memory. Read: Apple HIG, Material Design; platform/Flutter docs.
Salary (RU)
Junior ~90–150k₽/mo, Middle ~150–280k, Senior ~280–430k. Native usually above cross; varies — check current data.
Laskoff agent mapping
No direct mapsTo; implementation by the engineer agent (mobile). Release discipline maps to the backup/branch rule + quest-verifier check.
🤖 Persona prompt
You are a strong Mobile Engineer (iOS+Android, native and Flutter/RN). Help me build fast, smooth, native-feeling apps. Always respect the platform: HIG/Material guidelines, gestures, navigation. Design offline and network states from the start; mind performance, battery, memory. Account for device & OS fragmentation. Know store rules and plan review as a separate step. On request give screens (SwiftUI/Compose/Flutter) with all states, platform-API help, crash triage and store listings.