🔶 Show HN: Rejourney – Open-source revenue leak prediction for web and mobile apps

⬆️ 7 pts | 💬 0 comments | by mrr7337

中文全文翻译正在补齐，可先查看下方英文原文。

Find and fix conversion issues before they cost you users.

Website · Silly Demo (With Cats)

Rejourney is an open-source platform for finding problems in web and mobile user journeys before they become larger conversion, retention, or revenue problems. It combines session replay, the business events you define, and technical context such as request failures, crashes, and ANRs to surface patterns worth investigating.

SUPPORTED PLATFORMS

1. Install a Rejourney SDK in your web, Swift, or React Native app.
2. Track the few product events that matter most to your business, such as a completed signup, subscription purchase, or successful checkout. These are your critical conversion events.
3. Rejourney records the surrounding user journey and interaction data, then connects it with the events and technical signals from that session.
4. Similar sessions are grouped into cohorts. When a cohort shows a worrying trend around a critical conversion event, Rejourney brings the replays and evidence forward for analysis.
5. The result is an issue report with the relevant context and a suggested fix that your team can review and use in its development workflow. Connecting a GitHub repository can add code context and a proposed code change.

Rejourney relates the outcome you care about to what happened before it. The SDKs collect session, route or screen, interaction, and event context. That includes touches, scrolls, pans, repeated or rage taps, and the sequence of the user journey. When available, it also adds the technical evidence that makes an issue easier to diagnose: API response times and status codes, errors, crash traces, and ANRs.

Replays, journeys, and interaction patterns

Session replay shows the actual path a person took through a flow. Journey maps and heatmaps make it easier to compare paths, spot loops, and see where people try to interact with an unresponsive or confusing part of the interface.

API, crashes, and stability context

Replay alone does not explain every problem. Endpoint views show latency, errors, and status-code breakdowns. Crash and ANR detail adds the app version, device, and runtime context around a failure, helping connect a broken flow to the technical condition behind it.

Device and geographic cohorts

Filter a cohort by app version, operating system, device, geography, and other context to distinguish a broad regression from a problem limited to a release, device family, region, or network path.

Analytics and revenue context

The replay and issue views sit alongside project-level analytics: version adoption, engagement, stability, retention, cohorts, custom events, and—when a revenue source is connected—transactions, refunds, subscribers, and trends. Open an image for the full-resolution capture.

Version adoption, engagement, stability, retention, and cohorts. |
Custom events and the users behind them.
---|---

Revenue, refunds, subscribers, and the revenue trend for a connected source.

Track critical conversion events

Track stable, domain-level events for the actions that establish intent and a successful outcome. For example, a checkout flow might use checkout_started and purchase_completed:

Rejourney.logEvent('checkout_started', {
  orderId: 'order_123',
  amount: 49,
  currency: 'USD',
});

Rejourney.logEvent('purchase_completed', {
  orderId: 'order_123',
  transactionId: 'txn_456',
  amount: 49,
  currency: 'USD',
});

Rejourney uses these events to compare journeys and outcomes across similar sessions. A reported pattern is a starting point for investigation, not proof of causality: review the representative replays and your authoritative product or payment state before shipping a fix.

npm install @rejourneyco/browser


import { Rejourney } from '@rejourneyco/browser';

await Rejourney.init('pk_live_your_public_key');
await Rejourney.start();

Call start() after consent when your site requires it. Add the application domain to Allowed Domains in Project Settings; web recording does not start until it is allowed. See web getting started for framework-specific entry points, route naming, identity, and privacy settings.

npm install @rejourneyco/react-native


import { Rejourney } from '@rejourneyco/react-native';

Rejourney.init('pk_live_your_public_key');
Rejourney.start();

React Native requires native code and does not run in Expo Go. See React Native getting started for navigation tracking, session controls, event naming, and privacy settings.

In Xcode, choose File → Add Package Dependencies and add:

https://github.com/rejourneyco/rejourney

Rejourney requires iOS 15.1 or later.

import SwiftUI
import Rejourney

@main
struct MyApp: App {
    @MainActor
    init() {
        Rejourney.configure(publicKey: "rj_your_public_key")
        Task { await Rejourney.start() }
    }

    var body: some Scene {
        WindowGroup { ContentView() }
    }
}

See iOS getting started for screen tracking, identity, event capture, and recording controls.

Privacy and data handling

Privacy is a core consideration when recording user sessions. Configure consent, capture controls, sampling, allowed domains, and masking for your product. Do not send PII, credentials, payment data, secrets, or sensitive application payloads in events or logs.

Rejourney is designed for short recording retention periods—commonly seven days. After the retention window, recordings are quantized, fingerprints are anonymized, and the retained data is aggregated into general dashboard analytics. Make sure your configuration and policies meet the privacy and GDPR requirements that apply to your users.

The checked-in web benchmark compares the Rejourney browser SDK with PostHog on the same scripted flow in local Next.js, SvelteKit, and Nuxt fixtures. It measures SDK capture overhead, not issue-detection accuracy or a latency SLA.

The published run used Chromium at 1365×768, three iterations per framework/mode, and a shared flow that included navigation, form edits, events, requests, errors, scrolling, and a controlled long task. Rerun it before applying these results to a different application.

The mobile comparison records package footprint against Sentry. It measures packages rather than a complete mobile application.

Sources: @rejourneyco/react-native on Bundlephobia and @sentry/react-native on Bundlephobia.

The recorded Rejourney capture measurement used an iPhone 15 Pro on iOS 26, Expo SDK 54, the React Native New Architecture, and a production app with Mapbox Metal and Firebase.

Only UIKit + Metal capture runs on the main thread. These measurements describe the recorded workload; they are not a general mobile-performance comparison.

Development and deployment

For a local development environment, start with local Kubernetes development. For single-node self-hosting, use the self-hosted guide. Architecture and deployment references are in the architecture documentation.

Client-side components (SDKs and CLIs) are licensed under Apache 2.0. Server-side components (backend and dashboard) are licensed under SSPL 1.0. See LICENSE-APACHE and LICENSE-SSPL.