About the role
The 🤫 One app is where most people will meet their agent, and it has to feel like it belongs on the device rather than like a website in a shell. You will own iOS or Android, or both, in a codebase where the agent runs partly on the phone itself, which makes battery, memory, and latency product decisions rather than optimisations you do at the end.
What you’ll do
- Build the Agent One app end to end in Swift / SwiftUI (iOS) and Kotlin / Jetpack Compose (Android) - native where it counts
- Nail performance: instant cold start, 120Hz ProMotion smoothness, memory, battery, and flawless offline-first sync
- Ship voice-first, on-device AI experiences (Core ML and on-device runtimes) with privacy by construction
- Wire Sign in with Apple, passkeys, Secure Enclave / Keystore, and the on-device consent layer (PCHP)
- Obsess over accessibility (VoiceOver, Dynamic Type, TalkBack) so a 6-year-old and a grandparent both succeed
What we need to see
- You have shipped and maintained a native app real people used, through the store, through the bad reviews, through the fixes
- Deep platform fluency in Swift and SwiftUI, or Kotlin and Compose
- You treat performance, battery, and memory as part of the design rather than as a cleanup pass
- Comfort with an app whose backend, model, and permissions model are all moving at once
Nice to have
- Both platforms rather than one
- On-device inference, Core ML, or similar
- Background execution, notifications, and the permission surfaces that decide whether an agent is useful or annoying
What winning looks like
- App Store / Play Store rating and crash-free rate
- Cold-start time, frame rate, and battery within target
- Activation and weekly-active retention on mobile
Where and how we work
In the office together five days a week, in any of these cities. Remote-friendly around your family, arranged one person at a time.