RalphRalph.aiAuto-generated journey graph
Drop in the snippet (web) or the hook (React Native) and Ralph crawls outward from your entry point, discovering screens and paths as real users take them. The graph builds itself and stays current on every deploy.
User analytics so simple, even Ralph gets it.
RalphRalph.ai maps every user journey from your entry point into one visual graph, overlays the numbers on real screenshots, and explains in plain words why each step in your critical flow dropped or lifted after a change.
One snippet for web · one hook for React Native · no event naming required
Named after Ralph, a real frenchie who, with love, is not a smart boy. If he couldn’t get it, we didn’t ship it.
Ralph, Chief Simplicity OfficerHas never read a dashboard manual. Never will.
Works withAny websiteReact Native5-minute installSession data stays yours
Your whole funnel, drawn for you on real screenshots.
Point Ralph at your entry point. It walks your app the way users do, builds the journey graph automatically, and pins conversion between every screen. You never write an event taxonomy or sit through a tracking plan meeting.
▲ +4.2%61% continue
▲ +1.1%44% continue
▼ −18.3%29% continue
▲ +0.4%78% convert
Ralph’s read on this flowShipping → Payment dropped 18.3% after Tuesday’s release. The new required phone-number field was added above the fold; 62% of abandoning users left within 8 seconds of focusing it, mostly on mobile. Making the field optional again, or moving it to Payment, is the biggest win available in this flow.
Three things, done properly.
No 40-widget dashboard. Ralph does the analysis; you get the answer.
Numbers on real screenshots
Ralph pins conversion, drop-off, and rage-taps directly onto screenshots of your actual UI, not onto abstract event names like btn_click_v2_final. You see the screen your users saw.
AI that explains the why
When a step in your critical flow moves, Ralph correlates it with what changed (a release, a copy edit, a new field) and writes the diagnosis in one paragraph a golden-retriever-brained founder can act on.
Compare what changed and what it cost you.
Every deploy gets a before/after on your critical flow. Ralph diffs the screens, diffs the numbers, and links the two, so “the funnel dropped” comes with a suspect attached.
v2.13 · beforeMon · sample data
Shipping form fields6
Phone numberoptional
Shipping → Payment47.3%
Median time on step0:41
v2.14 · afterTue · sample data
Shipping form fields7 (+1 required)
Phone numberrequired
Shipping → Payment29.0% (−18.3)
Median time on step1:22 (+0:41)
Root causeNew required field introduced in v2.14 is the only screen-level change on this step. Ralph estimates it accounts for the full drop, with mobile users affected 2.4× more than desktop.
Stop guessing why the funnel dropped.
We’re onboarding a small batch of web and React Native teams each week. Leave your email and Ralph will sniff you out.
No spam. One email when your workspace is ready.