Launching today
Rheo
Ship and test app funnels without App Store reviews
47 followers
Ship and test app funnels without App Store reviews
47 followers
Growing a mobile app comes down to distribution and funnel optimization. Most teams nail the first and stall on the second, because every screen change waits on an App Store release. Rheo fixes that. Integrate the SDK once, then your team owns the journey from the dashboard: design funnels on a canvas, publish changes instantly, run experiments and measure what converts without waiting for an app store review cycles.
Hey Hunters 👋
I'm Stefano, founder of Rheo.
I built Rheo because I kept running into the same wall while growing mobile apps.
I'd pour time and money into distribution — getting lots of people to install my apps — without realizing my funnel had massive leaks. When I had a clear hypothesis for what to change, there was no quick way to test it. I was forced to wait: for a new app build, and for App Store review. Days turned into weeks, and iteration stalled.
The frustrating part wasn't a lack of ideas. It was that improving the journey moved at a completely different speed than acquiring users. I could tweak ad creative in an afternoon. I couldn't tweak the screen right after install without a full release cycle. Those small conversion lifts kept dying in the backlog.
I wished something like Rheo existed back then: integrate once, then own the in-app journey from a dashboard. Design flows on a canvas. Change copy, structure, and branches without a store submission. Publish over the air. Run experiments. See exactly where users drop off, step by step.
That's what I've built.
Rheo is for anyone who's felt that gap — when you're getting users in the door but can't iterate on what happens after install at the same pace you run growth experiments.
What Rheo can do:
- Visual flow builder: onboarding, paywalls, win-backs, feedback flows, and more
- OTA publishing: no App Store review for flow changes
- Analytics: step-level funnel analytics, drop-off analysis, cohort analysis
- Experiments: A/B or multivariate testing
- External Integrations: RevenueCat for paywalls and AppsFlyer for attribution
- SDK support: React Native (live), SwiftUI (coming soon), Flutter (coming soon)
I'd genuinely love feedback from the PH community, especially from anyone building and growing mobile apps.
Try it: https://getrheo.io/?source=produ...
Docs: https://docs.getrheo.io
Clean landing page and solid launch! Would love to see Flutter live soon. we’re literally trying to build an in-house version of this right now for our win-back flows. Any rough timeline on the Flutter SDK? Would love to jump on a beta if you're looking for early testers.
Thanks @vishalmehta8340 - currently in the final stage of testing and refining the implementation to ensure it provides the same exact experience as the RN SDK. 🔜
Congrats on the launch, Stefano. Having RN support live out of the gate is huge for us. Quick question on the implementation side: how does this work with Expo EAS updates? If we're already using EAS Updates, does Rheo conflict with that at all, or does it run entirely on its own layer?
Hi @abhiranjan_mehta, Rheo is fully compatible with EAS update as it runs on its own layer. 👍
This looks incredibly clean. My only hesitation with OTA flow builders is always Apple and Google stance on changing app behavior without a review. How does Rheo handle this under the hood to make sure we don't risk getting flagged?
hey @suyash_kr , great question - we rely on the same rules that allows product like EAS Updates or RevenueCat.
Apple Developer Program License Agreement (DPLA) 3.3.2
"Interpreted code may be downloaded to an Application but only so long as such code:
(a) does not change the primary purpose of the Application by providing features or functionality that are inconsistent with the intended and advertised purpose of the Application as submitted to the App Store,
(b) does not create a store or storefront for other code or applications, and
(c) does not bypass signing, sandbox, or other security features of the OS."
Rheo is narrow scoped via the set of components you can add on a screen (no arbitrary code) which makes it compliant with the guidelines above. It's however user responsibility to not use Rheo to circumvent any other guidelines.
how does this actually play with apple’s strict review rules for remote functionality, do i risk getting flagged for changing ui flows without a release
hey @nisaxvhd, great question - we rely on the same rules that allows product like EAS Updates or RevenueCat.
Apple Developer Program License Agreement (DPLA) 3.3.2
"Interpreted code may be downloaded to an Application but only so long as such code:
(a) does not change the primary purpose of the Application by providing features or functionality that are inconsistent with the intended and advertised purpose of the Application as submitted to the App Store,
(b) does not create a store or storefront for other code or applications, and
(c) does not bypass signing, sandbox, or other security features of the OS."
Rheo is narrow scoped via the set of components you can add on a screen (no arbitrary code) which makes it compliant with the guidelines above. It's however user responsibility to not use Rheo to circumvent any other guidelines.
This hits so close to home. The friction between marketing wanting to test a new onboarding hook and engineering having to squeeze an App Store release into the sprint is a constant battle. Absolutely love that you’re solving this, Stefano. Upvoted and sharing this with our mobile team today
🙏🙏🙏