Apprvd.app
Join the waitlist

Know what each release did — not what it felt like.

Mark a release and Apprvd.app compares the fourteen days before it with the fourteen after, across the metrics you choose, with release markers on every chart in the app.

At a glance
Window14 days before · 14 after
MetricsUsers, revenue, D1/D7, events
RetentionRates, never zero-filled
MarkersOn every chart
The challenge

Why it's hard today

1
Every release is judged by anecdote
A few loud reviews or one good day decide whether a release "worked".
2
Charts without context
A dip on Tuesday means nothing until someone remembers that 2.4.0 went out on Monday.
3
Misleading edges
Day-7 retention for a release that shipped three days ago can't be known yet. Tools that plot it as zero draw a cliff that isn't there.
The Apprvd.app approach

How Apprvd.app handles it

Before and after, equal windows

Fourteen days either side, per metric, so the comparison is like for like.

Your metrics

Pick the metrics each release is judged on. Change them and the result recomputes — they're part of the cache key.

Honest retention

Retention days that haven't happened yet stay empty and are left out of the summary.

Context everywhere

Releases appear as markers on dashboard charts, so every dip and spike has a date beside it.

How it works

From connection to decision

Step 1
Mark
Record a release with its version and date — or the day a Remote Config change went live.
Step 2
Measure
Apprvd.app fills the before and after windows as the days arrive.
Step 3
Review
Read the lift per metric and share the result with the team.
Related

Keep exploring

FAQ

Questions, answered

Take the first reading.
Connect a Firebase project and the board fills itself — dashboards, funnels, experiments and push, from data you already have. Apprvd.app opens to the waitlist first.