React Native Developer for Advanced Notification Architecture

Looking for an experienced React Native / mobile developer to help stabilise and complete an app already in development.

I'm a Service / UX Designer and entrepreneur with experience leading teams and delivering digital products. I’ve built an MVP for a cycle-aware reminder app and have reached the point where I need an experienced mobile developer to take over the architecture side and get it production ready.

The app was initially built using the AI development platform Replit to rapidly prototype, validate ideas, and accelerate development. That approach worked well for getting an MVP live quickly, but I've now reached the stage where the underlying architecture needs experienced mobile engineering input.

Current state:

• UI largely complete
• Core reminder logic exists
• App is running on real devices
• Product direction and UX are well defined
• Existing codebase and architecture documentation available

The app itself is quite far along. The challenge is the notification engine and underlying architecture rather than the product.

The app relies heavily on notifications, so reliability is critical. It needs to:

• work offline
• continue working when the app is fully killed
• process notification actions correctly
• not depend on users reopening the app
• avoid duplicate or missed reminders

Current stack:

• React Native / Expo
• expo-notifications
• expo-sqlite
• Express + PostgreSQL backend
• EAS builds
• RevenueCat

Features already implemented:

• cycle-based reminders
• interval/day reminders
• weekday reminders
• multiple reminder times
• Take / Skip / Snooze actions
• reminder history
• local persistence

Current issues:

• unreliable killed-state behaviour
• notification actions failing intermittently
• duplicate notifications from rescheduling flows
• scheduling depends too heavily on JS runtime behaviour
• offline reliability not strong enough for a medication/reminder product
• Expo-managed limitations appear to be becoming a blocker

The current architecture uses a hybrid local notification / server push approach. Through debugging and architecture reviews, there are signs that parts of the scheduling system may be fundamentally flawed, including backend scheduling behaviour in autoscaling environments.

I’m open to keeping parts of the current stack if it makes sense, but I’m not looking to layer more workarounds on top. Priority is getting the architecture right.

Looking for someone who can:

• review the current setup
• identify what should stay vs be reworked
• implement a reliable native notification architecture
• help get the app production ready

Open to freelance, ongoing collaboration, or potentially a longer-term role if there’s a strong fit.