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 y…

Rejourney finds product failures that may be costing revenue. You define the business transition to protect: activation, checkout, purchase validation, entitlement, or renewal. Rejourney compares the current cohort with a healthy baseline and groups the evidence around the change. Session replay is central to the workflow. A conversion drop identifies a transition worth checking; the recording shows the path to that transition, what the user tried, whether the UI acknowledged it, and the errors or slow requests in the same session. Reviewers can compare affected sessions with successful sessions from the same release, device, route, or campaign. The result is a candidate leak with a cohort, a baseline, supporting signals, and sessions to inspect. It becomes a confirmed product or revenue problem only after the relevant application and business state have been checked. The issue feed points to a cohort. These views are used to narrow down what changed and where to look next. Journey maps show the routes through a flow. Heatmaps expose the interaction pattern on the screen: repeated taps, missed targets, or controls that receive little attention. Use both when the failure is visible in the interface but the cause is not yet clear. Endpoint views break down request volume, errors, latency, and status codes. Crash and ANR detail adds the app version, device, and thread context around a failure. This is where a problematic UI transition can be connected to a backend or runtime condition. Device views make version, operating-system, and hardware concentrations visible. Geographic views help separate a global regression from an issue tied to a region or network path. The replay and investigation views sit alongside the project-level context that helps decide whether a change is isolated or broad. The overview combines version adoption, engagement mix, stability, time in product, retention, and cohorts. The events view shows the business events behind a flow and the users who generated them. When a revenue source is connected, the revenue view keeps transactions, refunds, subscribers, and the revenue trend in the same review.