Show HN: Rejourney – Open-source revenue leak prediction for web and mobile apps
Hello there (General Kenobi's favorite way to start the conversation), I’m Rashid, a sophomore at UT Austin. I built Rejourney.co ( https://rejourney.co/ ) to predict issues with your apps and websites before they happen, based on real user session recordings. Here is a silly video (with cats) on how it works: https://www.youtube.com/watch?v=Z95MDxBXMjk It’s open source, and the post link is the github repo, but here it is again: https://github.com/rejourneyco/rejourney I originally built this b
Hello there (General Kenobi's favorite way to start the conversation), I’m Rashid, a sophomore at UT Austin. I built Rejourney.co ( https://rejourney.co/ ) to predict issues with your apps and websites before they happen, based on real user session recordings. Here is a silly video (with cats) on how it works: https://www.youtube.com/watch?v=Z95MDxBXMjk It’s open source, and the post link is the github repo, but here it is again: https://github.com/rejourneyco/rejourney I originally built this because I had a campus freebie finder app that grew quickly, and I had a lot of users dm me on instagram about issues with the app’s onboarding and UX confusion. I initially lost about 340 users out of my 5,000ish users because of these issues, and I had to recover some by nudging them with notifications. It was a big pain, and I felt bad that I lost this many users to small and easy fixes. So I built Rejourney to predict that before it happens. Here is how it works: First, the SDK is installed on Web JS, Swift, or React Native apps. You then help the SDK a little with a few lines of tracking important events -- such as a subscription bought, a signup completed, etc -- before you ship the app. We called these “critical conversion events”. From here, Rejourney records the user session along with the meta data you set up, and relates it to the sequence of the user journey, each touch/scroll/pan interaction, and rage taps. If deemed an issue, it bundles in API response times and codes, ANRS, and crash traces into the context. A heuristic then bundles all the user recordings into similarity cohorts for processing, and finds similar user journeys and outcomes in relation to the critical conversion actions that matter to you. If a trend is found that is possibly worrying, it admits the user recordings into segmentation and processing by an LLM on our back (in this case Gemini for cost and speed, but it has been tested on GPT 5.5 if you decide to self-host and set this up on your sid
本文内容来源于互联网,版权归原作者所有
查看原文