Launched this week
Revyl
The mobile source of truth
120 followers
The mobile source of truth
120 followers
Revyl gives mobile teams full observability into how their app actually behaves on live cloud devices. Step-level execution traces, performance data (CPU, memory, FPS), a complete network waterfall, and state and file-system diffing across every run. Atlas auto-maps every screen and flow in your app, and revyl dev brings hot reload and device control into your dev loop.
Free Options
Launch Team / Built With
Revyl
Hey Product Hunt👋,
Revyl is the mobile source of truth.
There are 3 main parts of revyl:
- The platform captures the full run so you see why something failed
- CLI allows you (or your coding agent) to drive cloud device from terminal
- Atlas auto-maps every screen and flow in your app, a live source of truth instead of a stale diagram
Would love your feedback from anyone shipping mobile.
'the mobile source of truth' is a positioning that can mean a few different things. is the source of truth about app state in production, about which build is live across cohorts, or about user behavior aggregated across platforms? curious where you've landed and whether mobile teams are buying this as observability or as control plane.
Revyl
Closest to your first framing. The source of truth is what a given build actually does, verified by exercising it rather than inferred from analytics. We drive your app on cloud devices, Atlas turns those runs into a living map of every screen and path per build, and the platform is where teams see and gate on it.
On your observability vs control plane question: it's both, and that's the point. You get the observability surface (step traces, network, state diffs) from runs you trigger pre-release instead of waiting for a user to hit the bug, then gate on what you see. "Which build is live across cohorts" and cross-platform diffs fall out of running per-build across the device matrix.
The report is what makes this interesting to me. For mobile E2E, I care less about a bare pass/fail and more about seeing why a run failed. When writing natural-language steps, how specific should they be to avoid brittleness across small UI changes?
Revyl
@edan_tusi Counterintuitively, vaguer is more robust. "Tap checkout" survives a redesign that "tap the green button at the bottom" won't, because the agent resolves intent against what's actually on screen.
Driving real cloud devices from the CLI is the part that stands out to me. It feels especially useful for mobile teams trying to bring testing closer to the dev loop. How does it fit into CI today?
Revyl
@farrukh_butt1 Thanks for the question!
For CI, most teams use our GitHub Action: upload the build, run the test against it. It streams results live, drops a
report link in the run, and exits 0 or 1 so it gates a merge or deploy cleanly.
Expo/EAS works too. If you're not on GitHub Actions, the raw CLI does the same thing.
Have used Revyl to help me vibecode some iOS apps for fun, super fast and just makes testing so easy, the new maps feature highkey really helps for all the onboarding pages we have to build now.
Revyl
@rishabluthra Thank you for the kind comment!
Glad to hear Revyl is helping you out
the file-system diffing across runs is the bit i haven't seen anywhere else - catching state that quietly accumulates between sessions is genuinely hard to debug otherwise. combining that with the full network waterfall on cloud devices is a strong combo for the 'only happens in prod' class of mobile bugs
Revyl
@galdayan Thank you!
I literally use Revyl everyday to test regressions in our app as I'm adding new features everyday with Codex. It's such a good tool for peace of mind. Congrats on the launch :)
Revyl
@aravs appreciate it man, glad it's been useful for you 🙏