What you’ll do
We build platforms for government and enterprise operations, and the mobile app is where field teams and citizens actually touch them — often on a mid-range device, often with patchy connectivity. You will own that app end to end, from the first screen to the store listing. We care more about how you build than what you build in: Flutter, React Native, or native Swift and Kotlin are all welcome, provided you know one of them deeply.
Building the app:
- Build and ship applications for iOS and Android — cross-platform with Flutter or React Native, or native with Swift and SwiftUI, Kotlin and Jetpack Compose, whichever the project calls for.
- Turn designs into precise, responsive interfaces — including right-to-left layouts and Arabic localisation from the first screen, not as a retrofit.
- Structure the app for change: a consistent architecture and state approach — Riverpod or Bloc, Redux or Zustand, MVVM with Combine or Flow. Which one matters far less than applying it consistently.
- Integrate the REST APIs our backend teams build: authentication, pagination, error and retry behaviour, and streaming responses from AI features.
- Work close to the platform where it matters — platform channels or native modules, background execution, permissions, and the OS differences that only appear on a real device.
Working offline, on real devices:
- Design for connectivity that comes and goes: local persistence with SQLite, Room, Core Data, Drift or Realm, queued writes, and sensible conflict resolution when the network returns.
- Use device capabilities where the work demands them — camera and document capture, geolocation and maps, file handling, biometrics, push notifications.
- Profile and fix performance and battery drain on the mid-range Android hardware people actually carry, not only the newest iPhone.
Security and compliance:
- Handle sensitive data properly: secure storage in Keychain, Keystore or EncryptedSharedPreferences, biometric and PIN authentication, session handling, certificate pinning where required.
- Support what government and enterprise work demands — data residency, audit trails, and accessibility with VoiceOver, TalkBack and dynamic type.
Shipping:
- Own releases end to end: signing and provisioning, versioning, App Store Connect and Google Play Console, staged rollouts, TestFlight and internal testing tracks.
- Automate builds and distribution in CI — fastlane, Codemagic, Xcode Cloud, GitHub Actions or Azure DevOps.
- Write tests where they pay for themselves, and act on what crash reporting shows: Crashlytics or Sentry, watched rather than installed.
We look for
Required:
- Three years or more building and shipping mobile applications.
- Depth in at least one mobile stack: Flutter and Dart, React Native and TypeScript, native iOS with Swift, or native Android with Kotlin.
- Apps you have published to the App Store or Google Play and can point to.
- A working grasp of the platforms underneath the framework: app lifecycle, permissions, background work, navigation, and store review rules.
- REST API integration, JSON handling, and sane behaviour around errors, timeouts and retries.
- Local persistence and genuine offline behaviour, beyond caching a list.
- An architecture and state approach you can defend, and the judgement to know when it is overkill.
- Git, code review and CI as daily habits.
- Tests where they earn their place, and crash reports you actually read.
- Attention to design detail — spacing, motion, and the difference between working and finished.
- Good communication in English; Arabic is an advantage, particularly for right-to-left work.
Nice to have:
- A second mobile stack, or the appetite to pick one up — we choose per project, not per engineer.
- Both cross-platform and native experience, so you know what each one costs.
- Right-to-left and Arabic localisation shipped in production.
- Offline-first synchronisation and conflict resolution for field use.
- Maps and geolocation-heavy applications.
- Push notifications across FCM and APNs, including deep linking.
- Firebase, or Azure-hosted mobile backends.
- A mobile CI and release pipeline you built rather than inherited.
- Consuming LLM or AI endpoints — streaming responses and token-by-token interfaces.
- Mobile accessibility: VoiceOver, TalkBack, dynamic type, contrast.
- Government, banking or other regulated environments.