airader

airader is the renamed product surface from the recent trakkker repository work: a session-replay tool for watching user sessions, understanding customer-journey friction, and exporting session data into analysis workflows.

The project is moving away from a generic tracking shell and toward a more specific product idea: session replay that is useful for humans, agents, and downstream analysis. The value is not just recording clicks. It is making the journey inspectable enough that product teams can understand where users hesitate, break, rage-click, or abandon a flow.

What it does

• Captures session-replay style interaction data for product and UX debugging.
• Provides a clearer landing page around the session-replay and customer-journey angle.
• Supports session pagination so longer lists can be explored instead of only sampling the first page.
• Adds public API documentation and an OpenAPI schema for external access.
• Positions against common analytics/session tools through comparison pages.
• Keeps the door open for analysis workflows beyond a closed dashboard.

Why this project exists

Most analytics tools tell you what happened in aggregate. Session replay helps answer the more painful question: why did that user get stuck? The product direction behind airader is to make those moments easier to inspect and easier to connect to follow-up work.

That matters more as products are increasingly built and modified with AI assistance. Teams need a way to feed real user friction back into the build loop. A replay tool with a usable API can become more than a dashboard; it can become evidence for prioritization, QA, support, and automated analysis.

Recent work from local commits

The recent commits moved it toward a clearer product: landing-page copy, session pagination, login and site-detail flows, public API documentation, OpenAPI schema, and comparison pages for teams looking beyond generic analytics tools.

A rebrand pass changed the public surface from trakkker to airader. Another pass improved the landing page, SEO copy, metrics state, HUD state, and notification-hook state. The comparison work added Hotjar and Lucky Orange alternatives, making the product angle more explicit: session replay, API access, and exportable journey data.

Product story

airader is strongest when it is framed as a bridge between visual replay and operational follow-up. A product person wants to watch what happened. A developer wants enough detail to reproduce or fix it. A support workflow may need a shareable summary. An agent workflow may need structured session data. The project direction is to support those different consumers without making the replay data disappear inside a single UI.

Current direction

The useful next steps are deeper replay inspection, clearer API examples, stronger onboarding for sites/projects, and more concrete analysis loops that turn session evidence into product decisions. The comparison pages are a start, but the product needs to keep proving what it can do that a generic analytics dashboard cannot.

Public boundary

This public page explains product direction and surfaced work. It does not expose private recordings, customer-identifying session data, credentials, or raw operational logs.