Mobile app Growth Engineer template
Connect onboarding, paywalls, crashes, reviews, RevenueCat, and code—then recommend one mobile growth change.
Product data preview
Signals to agent context
Funnels, instrumentation, and evidence your coding agent can act on.
A mobile app workflow for using onboarding, paywall, RevenueCat, Sentry, reviews, and code context in Growth Engineer runs.
Who this is for
Start here if the problem below sounds familiar. You do not need every connector on day one—just enough signal for the Growth Engineer to propose work you can review.
- Subscriptions with onboarding and paywall journeys
- React Native and Expo teams using agents
- Founders including store feedback and crashes in prioritization
How it works
The loop is the same across guides: connect evidence, let the agent read it, then ship a reviewed task with a verification metric.
- Query onboarding, paywall, purchase, and retention events.
- Add RevenueCat trial, churn, MRR, and subscription summaries.
- Add Sentry crashes, App Store reviews, and release notes.
- Ask for the smallest change that moves one metric.
What you get back
The output should be concrete enough to review without opening five dashboards.
- Mobile use cases for onboarding, paywalls, and React Native.
- RevenueCat, Sentry, App Store, and GitHub are core sources.
- Issue and PR-oriented handoffs.
Common questions
Quick answers before you connect product data to an agent.
Which mobile metric should this optimize first?
Activation or purchase conversion early; retention once repeat usage is measurable.
Does this require React Native?
No—any app with explicit events and connected summaries qualifies.
Should reviews be included?
Yes—reviews explain frustration analytics only hints at.