Senior Mobile Application Engineer (iOS & Android)

Senior Mobile Application Engineer (iOS & Android) at YesAstrology

YesAstrology is hiring a Senior Mobile Application Engineer (iOS & Android) on a full-time, fully remote basis, open to candidates worldwide, within the Mobile Engineering department. The role is to lead the architecture, development, and launch of YesAstrology's flagship native mobile applications across both iOS and Android, delivering fluid animations, interactive charts, and seamless in-app subscriptions.

Millions of people rely on YesAstrology for daily guidance, cosmic calendars, and deep chart analysis. This position exists to carry that same depth of experience from the responsive web ecosystem into a tactile, high-performance mobile application — one where a seeker can spin a natal chart wheel with a thumb, glance at a daily transit on a lock screen, and move through a reading without a single dropped frame.

The team's preferred stack is a modern cross-platform architecture, such as React Native or Expo with native modules, backed by TypeScript and Supabase. Candidates should expect to work across both operating systems rather than owning a single platform, architecting a unified codebase that targets parity between iOS and Android while still reaching into native Swift and Kotlin territory where widgets, live activities, and billing demand it.

This is a senior individual-contributor role with architectural ownership. If the idea of translating planetary geometry, ephemeris-driven chart wheels, and layered astrological interpretation into native mobile craft appeals to you, explore the wider platform at YesAstrology to see the product surface you would be shaping.

Role Overview and Engineering Responsibilities

The Senior Mobile Application Engineer owns five core responsibility areas: architecting and deploying production-grade cross-platform and native mobile applications with 60fps responsiveness; building interactive graphical charts, gestures, and fluid touch interactions with modern animation frameworks; creating native OS integrations including home screen widgets, lock screen live activities, and push notification architectures; implementing and scaling in-app purchase and subscription funnels via StoreKit, Google Play Billing, and RevenueCat; and establishing mobile CI/CD pipelines, automated testing, crash reporting telemetry, and performance profiling.

The chart-rendering work is the technical heart of the role. YesAstrology's web ecosystem carries over 170 calculation engines and personalized insights, and the mobile app must present that output — house cusps, planetary placements, aspect grids — as something a user can pinch, rotate, and tap. Whether a chart is drawn in Placidus, Whole Sign, or Equal House, the app receives computed cusp degrees and must render them faithfully; a chart cast with an exact birth time shows precise Ascendant and Midheaven degrees, while a chart defaulting to solar noon still preserves accurate planetary signs and aspects. The mobile layer must respect those distinctions visually rather than flattening them.

Native integrations carry the daily-return experience. Lock Screen Live Activities and Android Glances can surface a transit of the day — say Saturn contacting the natal 10th house, or the Moon moving through the 6th — while push pipelines deliver timely, personalized notifications. Subscription monetization runs through StoreKit and Google Play Billing via RevenueCat, and the engineer is expected to treat billing flows, offline-first caching, and native bridge communication as first-class architecture rather than afterthoughts.

What We Look For

• 4+ years of professional mobile development experience shipping consumer applications on iOS and Android
• Demonstrated expertise with modern cross-platform frameworks (React Native, Flutter) or native Swift / Kotlin architectures
• A proven track record with at least one published, highly rated consumer application on both the Apple App Store and Google Play Store
• Deep understanding of mobile subscription architectures, in-app billing flows, offline-first caching, and native bridge communication
• An uncompromising eye for UI/UX craft, typography, accessibility, and micro-interactions

Craft matters here in a specific way: the interface must feel as considered as the astrology beneath it. Typography that honors long-form interpretation, accessibility that keeps chart data legible to screen readers, and micro-interactions that make a gesture feel responsive all shape whether a reading lands. If you want to see the breadth of tools and interpretive surfaces the app will eventually carry, browse the astrology tools available on the platform.

iOS and Android Application Development

The Senior Mobile Application Engineer at YesAstrology builds and ships the flagship native applications on both iOS and Android, delivering interactive chart wheels, fluid touch gestures, native widgets and in-app subscriptions from a unified codebase. The role is full time and fully remote, open to candidates worldwide within the Mobile Engineering department, and it carries architectural ownership rather than single-platform specialization. The engineer works across both operating systems, reaching into native Swift and Kotlin only where widgets, Live Activities, Glances and billing demand it.

The chart-rendering surface is where the astrology becomes tangible. YesAstrology's web ecosystem carries more than 170 calculation engines and personalized insights, and the mobile layer must present house cusps, planetary placements and aspect grids as objects a user can pinch, rotate and tap at a steady 60fps. A chart cast with an exact birth time renders precise Ascendant and Midheaven degrees, while a chart defaulting to solar noon still preserves accurate planetary signs and aspects — the interface must visually honor that distinction rather than flattening it. Whether the wheel is drawn in Placidus, Whole Sign or Equal House, the app receives computed cusp degrees and must render them faithfully.

Native OS integrations carry the daily-return experience. iOS Lock Screen and Live Activities and Android Glances can surface a transit of the day — Saturn contacting the natal 10th house, or the Moon moving through the 6th — while push notification pipelines deliver timely, personalized guidance. Subscription flows run through StoreKit and Google Play Billing via RevenueCat, and offline-first caching keeps a natal chart readable when a seeker opens the app without a connection.

Craft is measured in specifics: typography that honors long-form interpretation, accessibility that keeps chart data legible to screen readers, and micro-interactions that make a gesture feel immediate. Candidates should bring at least 4 years of professional mobile development experience, demonstrated expertise with React Native, Flutter, Swift or Kotlin, and at least one published, highly rated consumer app on both the Apple App Store and Google Play Store. To see the interpretive surfaces the app will eventually carry, browse the astrology tools on the platform.

Mobile App Architecture and Technical Leadership

The Senior Mobile Application Engineer sets the architectural standards the rest of the mobile practice follows, establishing CI/CD pipelines, automated testing, crash reporting telemetry and performance profiling for YesAstrology's native apps. The team's preferred stack is a modern cross-platform architecture such as React Native or Expo with native modules, backed by TypeScript and Supabase, targeting parity between iOS and Android while preserving native reach where platform APIs require it. This is a senior individual-contributor role with architectural ownership, not a management track.

Architecture decisions map directly onto astrological fidelity. House cusp calculation methods — Placidus, Whole Sign, Equal House — produce different cusp degrees from the same birth data, and the app's data layer must carry the chosen system through rendering, caching and widget snapshots without silently normalizing it. When birth time is incomplete, a solar-noon chart default preserves accurate planetary signs and aspects even though the Ascendant and Midheaven remain approximate; the interface should communicate that limitation honestly rather than presenting a false precision. Timing cycles — planetary transits, solar arcs and progressions — activate this potential over time, and the notification and Live Activity layers must schedule against those computed windows rather than generic daily triggers.

Technical leadership shows up in the unglamorous places: billing flows through StoreKit and Google Play Billing via RevenueCat treated as first-class architecture, native bridge communication documented and tested, offline-first caching designed before the first screen ships, and crash telemetry wired so a rendering fault on a specific device is visible within hours. The engineer also owns the standards for accessibility and typography that determine whether a long-form reading actually lands on a small screen.

What the Role Requires

• 4+ years of professional mobile development experience shipping consumer applications on iOS and Android
• Demonstrated expertise with modern cross-platform frameworks (React Native, Flutter) or native Swift / Kotlin architectures
• At least one published, highly rated consumer application on both the Apple App Store and Google Play Store
• Deep understanding of mobile subscription architectures, in-app billing flows, offline-first caching and native bridge communication
• An uncompromising eye for UI/UX craft, typography, accessibility and micro-interactions

Candidates who have built chart-like or data-dense visualizations will find the interactive wheel work familiar territory. Application details are handled through YesAstrology's official careers process on yesastrology.com; prepare evidence of shipped apps on both stores alongside examples of your architecture and UI craft.

API Integration and Backend Services

The Senior Mobile Application Engineer at YesAstrology integrates the mobile clients with a backend built on TypeScript and Supabase, consuming the output of more than 170 calculation engines and rendering it as interactive chart wheels, aspect grids and personalized insights. The integration layer is not a thin REST wrapper: it must carry computed house cusp degrees, planetary placements and timing windows from server to device without loss, and it must keep the same data consistent across the app, home screen widgets, iOS Lock Screen and Live Activities, and Android Glances.

Astrological fidelity begins at the data contract. A chart cast with an exact birth time returns precise Ascendant and Midheaven degrees, while a chart defaulting to solar noon preserves accurate planetary signs and aspects but leaves the angles approximate. The API response must expose that distinction explicitly — a flag on angle precision, the selected house system (Placidus, Whole Sign or Equal House), and the raw cusp degrees — so the mobile layer never silently normalizes one system into another. For instance, a natal chart with a Scorpio Ascendant under Placidus and the same birth data under Whole Sign will place planets in different houses; the payload has to say which system produced which placement, or a user comparing a reading across devices will see contradictions.

Timing cycles drive the notification and widget pipelines. Planetary transits, solar arcs and progressions are computed server-side and delivered as scheduled windows, so a Live Activity surfacing Saturn contacting the natal 10th house fires on the computed date rather than a generic daily trigger. The engineer designs the caching and sync strategy around these windows: ephemeris-derived data changes slowly and can be cached aggressively, while transit-of-the-day content and push payloads need freshness guarantees. Offline-first caching keeps a saved natal chart readable when a seeker opens the app without a connection, and the sync layer reconciles local edits to birth data against the server without duplicating charts.

Billing and identity sit in the same integration surface. Subscription state flows through StoreKit and Google Play Billing via RevenueCat, and the backend must treat entitlement checks as authoritative so a restored purchase unlocks the same chart depth on a second device. Native bridge communication between the cross-platform layer and Swift or Kotlin modules is documented and tested, because a widget snapshot or a billing callback that crosses that boundary is where integration faults surface first. Candidates can review the interpretive surfaces these services ultimately feed by browsing the reports available on the platform.

Mobile Performance, Security, and Scalability

The Senior Mobile Application Engineer owns the standards that keep YesAstrology's native apps at 60fps, secure in their billing and identity flows, and scalable across both platforms from a unified codebase. Performance is treated as a rendering contract: chart wheels, gestures and touch interactions must hold frame rate on mid-range Android devices as well as recent iPhones, and performance profiling, crash reporting telemetry and automated testing are wired into CI/CD so a regression on a specific device is visible within hours rather than after a store review.

Security concentrates on the surfaces that carry user trust. Birth data — date, time and place — is among the most personal information a seeker shares, and the app must handle it with encrypted transport, minimal local retention and clear handling of the solar-noon fallback when time is unknown. Subscription entitlements validated through StoreKit and Google Play Billing via RevenueCat are verified server-side so a tampered client cannot unlock paid chart depth, and native bridge boundaries are treated as trust boundaries: any Swift or Kotlin module receiving chart data or billing callbacks validates its inputs rather than assuming the cross-platform layer sanitized them.

Scalability is architectural rather than incidental. The team's preferred stack — React Native or Expo with native modules, backed by TypeScript and Supabase — targets parity between iOS and Android, which means a single fix to cusp rendering or accessibility reaches both stores at once. Offline-first caching is designed before the first screen ships, so growth in saved charts and cached ephemeris data does not degrade cold-start time. Widget and Live Activity snapshots are generated from the same computed data as the in-app view, preventing the drift that appears when each surface fetches independently.

Accessibility and typography are part of the performance and quality bar, not a later pass. Chart data must remain legible to screen readers, long-form interpretation must set cleanly on small screens, and micro-interactions must feel immediate without blocking the main thread. The role requires at least 4 years of professional mobile development experience, demonstrated expertise with React Native, Flutter, Swift or Kotlin, and at least one published, highly rated consumer app on both the Apple App Store and Google Play Store. Application details are handled through YesAstrology's official careers process on yesastrology.com.

Cross-Platform Development and Code Optimization

Cross-platform development at YesAstrology means architecting a single unified codebase that targets parity between iOS and Android while reaching into native Swift and Kotlin only where widgets, Live Activities, Glances and billing demand it. The team's preferred stack is a modern cross-platform architecture such as React Native or Expo with native modules, backed by TypeScript and Supabase. The engineer works across both operating systems rather than owning a single platform, and code optimization is treated as a rendering contract rather than a late-stage cleanup task.

Optimization decisions map directly onto astrological fidelity. House cusp calculation methods — Placidus, Whole Sign and Equal House — produce different cusp degrees from identical birth data, and the shared data layer must carry the chosen system through rendering, caching and widget snapshots without silently normalizing it. For instance, a chart with a Scorpio Ascendant under Placidus and the same birth data under Whole Sign will place planets in different houses; if the cross-platform layer collapses that distinction, a user comparing a reading on an iPhone and an Android tablet will see contradictions. When birth time is incomplete, a solar-noon chart default preserves accurate planetary signs and aspects even though the Ascendant and Midheaven remain approximate, and the interface should communicate that limitation honestly rather than presenting false precision.

Performance work concentrates on the chart-rendering surface, where house cusps, planetary placements and aspect grids must respond to pinch, rotate and tap gestures at a steady 60fps on mid-range Android devices as well as recent iPhones. Ephemeris-derived data changes slowly and can be cached aggressively, while transit-of-the-day content and push payloads need freshness guarantees; timing cycles such as planetary transits, solar arcs and progressions are computed server-side and delivered as scheduled windows, so a Live Activity surfacing Saturn contacting the natal 10th house fires on the computed date rather than a generic daily trigger. Offline-first caching is designed before the first screen ships, keeping a saved natal chart readable without a connection and preventing growth in cached ephemeris data from degrading cold-start time.

Because a single fix to cusp rendering or accessibility reaches both stores at once, the cross-platform layer is also where quality standards are enforced: typography that honors long-form interpretation, screen-reader legibility for chart data, and micro-interactions that feel immediate without blocking the main thread. Native bridge communication between the shared layer and Swift or Kotlin modules is documented and tested, since a widget snapshot or billing callback crossing that boundary is where integration faults surface first. Candidates can review the interpretive surfaces this codebase ultimately feeds by browsing the YesAstrology blog.

Required Skills, Experience, and Qualifications

Candidates need at least 4 years of professional mobile development experience shipping consumer applications on iOS and Android, demonstrated expertise with modern cross-platform frameworks such as React Native or Flutter or with native Swift and Kotlin architectures, and at least one published, highly rated consumer application on both the Apple App Store and Google Play Store. An uncompromising eye for UI/UX craft, typography, accessibility and micro-interactions is required alongside architectural depth. The position is full time and fully remote, listed as Remote (worldwide) within the Mobile Engineering department, and it is a senior individual-contributor role with architectural ownership rather than a management track.

The technical bar extends into subscription and data depth: a deep understanding of mobile subscription architectures, in-app billing flows through StoreKit and Google Play Billing via RevenueCat, offline-first caching and native bridge communication. Architectural ownership means defending decisions about cusp calculation fidelity, offline caching and native bridge boundaries in review, not only writing code — for example, arguing why a Placidus cusp degree must survive a widget snapshot unchanged, or why a solar-noon fallback must be flagged in the payload rather than smoothed into a precise-looking Ascendant.

Core Requirements

• 4+ years of professional mobile development experience shipping consumer applications on iOS and Android
• Demonstrated expertise with modern cross-platform frameworks (React Native, Flutter) or native Swift / Kotlin architectures
• At least one published, highly rated consumer application on both the Apple App Store and Google Play Store
• Deep understanding of mobile subscription architectures, in-app billing flows, offline-first caching and native bridge communication
• An uncompromising eye for UI/UX craft, typography, accessibility and micro-interactions

Candidates who have built chart-like or data-dense visualizations will find the interactive wheel work familiar territory, and experience with ephemeris-driven or timing-sensitive interfaces is a strong signal. Application details are handled through YesAstrology's official careers process on yesastrology.com; prepare evidence of shipped apps on both stores alongside examples of your architecture and UI craft.

How to Apply for the Senior Mobile Application Engineer Position

Applications for the Senior Mobile Application Engineer (iOS & Android) role are handled through YesAstrology's official careers process on yesastrology.com. The position is full time and fully remote, listed as Remote (worldwide) within the Mobile Engineering department, so candidates can apply from anywhere in the world. There is no separate application portal, recruiter inbox or alternate address to use — the official careers process on the canonical domain is the single channel.

Before submitting, assemble the evidence reviewers actually weigh. The requirements are concrete: at least 4 years of professional mobile development experience shipping consumer applications on iOS and Android, demonstrated expertise with modern cross-platform frameworks such as React Native or Flutter or with native Swift and Kotlin architectures, and at least one published, highly rated consumer application on both the Apple App Store and Google Play Store. Pair store listings with architecture write-ups and UI samples — a walkthrough of how you kept a data-dense visualization at 60fps on a mid-range Android device, or how you structured a native bridge between a shared TypeScript layer and a Swift widget extension, says more than a claim of seniority.

Because the role carries architectural ownership rather than a management track, the strongest applications show judgment about fidelity and trade-offs. If you have worked with ephemeris-driven or timing-sensitive interfaces, describe it: how you carried a chosen house system — Placidus, Whole Sign or Equal House — through rendering, caching and widget snapshots without silently normalizing it, or how you flagged a solar-noon fallback in the payload instead of presenting an approximate Ascendant as precise. Experience with subscription flows through StoreKit and Google Play Billing via RevenueCat, offline-first caching and crash telemetry belongs in the same narrative, since those are first-class architecture here rather than afterthoughts.

Application Checklist

1. Confirm you meet the core bar: 4+ years of professional mobile development, cross-platform or native Swift/Kotlin depth, and a published, highly rated consumer app on both the Apple App Store and Google Play Store.
2. Gather links to both store listings plus any public evidence of UI/UX craft, typography, accessibility work and micro-interactions.
3. Prepare one or two architecture examples covering chart-like or data-dense rendering, native bridge boundaries, offline caching or billing integration.
4. Submit through YesAstrology's official careers process on yesastrology.com, referencing the Senior Mobile Application Engineer (iOS & Android) title and the Mobile Engineering department.

To understand the product surface you would be shaping — interactive chart wheels, aspect grids and layered interpretation — you can browse the products offered on the platform before you apply.