Offline by default
No required account. Sensitive tracking data is designed to stay on-device.
Ayush MishraMobile Product Engineer
I ship mobile products.
I build mobile products and spend a lot of time on the messy parts that show up after people start using them: product behavior, edge cases, debugging, testing, releases, and iteration.
React Native / ExpoOffline-first systemsProduction ownership
Primary product proof
Petal Chan
Creator & Mobile Product Engineer · June 2025—Present
A privacy-first, offline period and cycle tracker shipped on iOS and Android. I own the product from behavior and architecture through React Native / Expo delivery, debugging, releases, monetization, and iteration.
Live product / iOS + Android
Privacy is product behavior.
Six-month Google Play view
265K
Play impressions
~3K
Device acquisitions
900+
Monthly active devices
The engineering story
A setting became a system.
Petal Chan has changed a lot since its first version. Real user feedback exposed assumptions in the tracking model that looked fine on paper but did not work for everyone.
People with irregular cycles, people using birth control, and people focused on symptoms needed something more flexible than conventional calendar predictions. That led to context-sensitive and symptom-only tracking modes, with changes to the product behavior underneath the interface.
Behavior, not a toggle
Different tracking modes changed underlying assumptions instead of adding a cosmetic setting.
Tested through real flows
Edge cases move through reproduction, review, hands-on testing, and production validation.
Maintained after launch
Store releases, a one-time upgrade, user feedback, and production iteration are part of the work.
How I work
The messy parts are the work.
My strongest work is deciding what a product should do, finding why it does not do that yet, and staying with the problem until the fix holds up in real use.
01
Define the behavior
Start with what the user should be able to do, what can go wrong, and which edge cases actually change the product.
02
Shape the system
Make architecture and data-flow decisions around the real behavior, including offline state, integrations, and release constraints.
03
Review the implementation
Use agent-assisted implementation and independent reviews, then reproduce warnings and failures instead of accepting a clean-looking diff.
04
Validate the product
Test the actual flow, correct what breaks, ship carefully, and let production feedback decide what needs to change next.
AI-augmented workflow
I use coding agents heavily for implementation and independent review. The product decisions, failure investigation, hands-on testing, and responsibility for what ships stay with me.
More shipped work
Products, not placeholders.
Smaller utilities still matter. They show repeatable product delivery across different workflows without competing with the depth of the Petal Chan story.
Legal workflow utilityLive
02
Deposition Timer
An offline iOS utility for deposition timekeeping, objection logging, and export-ready session records.
Shipped on iOSOffline-firstPDF + CSV exports
View on the App StorePrivate archive utilityLive
03
KeepDM
A local viewer for Instagram export data with search, media browsing, and biometric protection.
Shipped on iOSOn-device dataBiometric access
View on the App StoreAyush Mishra · India
Professional profile
I stay close to the problem.
I work best where product judgment and engineering meet: defining a useful behavior, shaping how it should work, finding the failure nobody expected, and seeing the fix through to production.
Current experience
Creator & Mobile Product Engineer — Petal Chan
June 2025—Present
Product behavior, architecture, releases, debugging, testing, monetization, and user-led iteration across iOS and Android.
Supporting client proof
NFC guard / access application — Mobile developer
A mobile scan-to-record workflow connecting real-world access events with database-backed information for an operational use case.
Mobile
- React Native
- Expo
- iOS + Android releases
- Native integrations
Product delivery
- Architecture
- Debugging
- Testing
- User-led iteration
Systems
- Offline-first behavior
- In-app purchases
- APIs
- Databases
Web + data
- TypeScript
- React / Next.js
- Supabase
- Cloudflare
Available for the right fit
Let's talk mobile products.
I'm open to remote mobile and product engineering roles, with full-time and strong long-term contracts preferred. I'm based in India and also open to European relocation with sponsorship.
Email AyushSelective client work
Have a focused product problem that needs an owner?