Launchpad

Simple terms

Launchpad is the home screen that tells an operator what to do next for the selected shop.

The daily command center for a shop. It shows readiness, active tests, draft blockers, recent learning, and the next best action.

Routes

• /

Implementation behavior

• Launchpad reads the active shop and aggregates setup state from goals, audiences, store profile, installation, drafts, and running experiments.
• It computes a readiness stage such as setup, launch, active learning, or readback based on what exists and what is blocking progress.
• The next-move card points to the highest-leverage route with a reason and confidence so operators do not hunt through the app.
• Learning proof comes from recent experiment outcomes, store profile findings, and signals that are already persisted.

How to use it

• Start from Launchpad before creating new work.
• Follow the highlighted next move if setup or launch readiness is unclear.
• Open active and draft tests directly from the Launchpad lists.
• Use readiness checks to decide whether to install, add metrics, build variants, QA, or read results.

When not to use it

• Do not use it as the source of truth for detailed experiment math; open the experiment or analytics pages for that.
• Do not treat a next-move suggestion as approval to launch without QA.
• Do not diagnose SDK install issues from Launchpad alone; use Realtime Analytics and installation checks.

Implementation source

• The route is src/app/(dashboard)/page.tsx with supporting dashboard data calls.
• It composes shop setup state from experiments, goals, audiences, installation, analytics summaries, and store profile state.
• Navigation cards link into the same underlying routes documented in the complete catalog.

Data and API

• Reads Shop, Experiment, Variation, Goal, ExperimentGoal, store profile, signal, and installation state.
• Analytics summaries come from dashboard and experiment analytics APIs.
• Navigation connects into /backlog, /tests, /analytics, /store-profile, and /installation.

Failure modes

• Empty Launchpad usually means no shop, no installation, or no foundations yet.
• A next move that looks stale usually points to incomplete setup data rather than a broken recommendation.
• Analytics cards stay thin until SDK events reach the Worker and Tinybird.