5 of 5 Permanent Apple iOS Jobs in Havant

electric aircraft. As Staff Android Engineer, you will own the Android app of a mature consumer product, drive new features, refinements, and align with iOS as the product evolves. You’ll ship Play Store releases, triage crashes, and optimize performance across devices. The role invites versatility across mobile ...

Archer is seeking a Staff Android Engineer to own the Android app of a mature consumer product, ensuring feature parity with iOS and delivering updates for a real user base. You will work in a team that uses AI-assisted development, read Swift, and engage with Play Store releases ...

posting stays vague on purpose. What we can say: the products are real, they ship, and people use them every day. As the Senior iOS Engineer, you'll own the iOS app of a mature consumer product — one that's been featured in the app stores multiple times … into seamless, shippable code and help steer the future of our digital flight tools. What You’ll Do: Develop scalable, high-performance features for iOS, iPadOS, and watchOS Partner with designers to build intuitive UI/UX that follows platform best practices Refactor and modularize Swift and Objective ...

Archer Aviation is seeking a Senior iOS Engineer to own the iOS app of a mature consumer product. You will join a small, expert team and shape an end-to-end mobile experience that blends AI and aviation expertise with a seamless user interface. You will develop … iOS, iPadOS, and watchOS, integrate REST APIs, and guide the full app lifecycle from builds to App Store submissions while upholding quality and performance. #J-18808-Ljbffr ...

product — one that's been featured in the app stores multiple times and has a real user base that opens it every day. The iOS and Android apps are close to feature parity, and in a couple of places Android is ahead. You'd own the Android side … evolves. What You’ll Do: Own the Android app of a mature, production consumer product: new features, refinements, and keeping it in step with iOS as both evolve. You'll be reading Swift regularly, even if you never write it Make the parity‐vs‐platform‐convention call constantly ...