Website performance monitoring & testing (roadmap)

This page tracks roadmap intent only. We have not researched or chosen tools for either area. Do not treat names elsewhere in the docs (for example a casual “e.g., Sentry” in deployment notes) as a stack decision.

Today we already have:

  • Vercel and Convex dashboards (ops visibility, not a full APM/error product)

  • First-party map tile latency reporting in Convex (see Map performance and failover)

  • Local/dev test pages in the Next.js app (not a website-testing SaaS)

None of that replaces dedicated website performance monitoring or website testing for production.

Website performance monitoring (planned)

Goal: Catch production errors, slow pages, and regressions before users report them.

Status: On the roadmap. No research into options yet (Sentry, Datadog, Vercel Observability, OpenTelemetry, etc. are examples of the category — not shortlisted).

When research starts, consider at least:

  • Browser and server error tracking

  • Web Vitals / performance budgets for key routes (/, /browse, /search, maps)

  • Privacy/CMP impact (what PII or cookies a vendor would introduce — update Termly / privacy policy if we share data)

  • Overlap with Vercel Analytics / Speed Insights if we enable those later

Website testing (planned)

Goal: Reduce regressions across marketing, auth, maps, and manage flows without relying only on manual clicks.

Status: On the roadmap. No research into options yet (Playwright, Cypress, visual regression, BrowserStack, Percy, TestFlight-style mobile, etc. are category examples — not shortlisted).

When research starts, consider at least:

  • Smoke / E2E for critical paths (sign-in, Square connect, browse/search, event publish)

  • Where tests run (local, CI on GitHub Actions, scheduled against preview/prod)

  • Visual vs functional coverage

  • Cost and maintenance burden for a small team

Out of scope for this page

  • Map-provider failover and tile latency (already documented in Map performance)

  • Choosing a CMP or analytics product (separate privacy / product decisions)

  • Mobile-app store QA (lives with ftn-app / Adapty release process)

Next steps

  1. Research and shortlist performance-monitoring options; document choice here and on Environment variables when secrets exist.

  2. Research and shortlist website-testing options; wire into CI only after a deliberate pick.

  3. Update privacy third-party disclosures if a chosen vendor receives personal data.

  4. Replace the generic “e.g., Sentry” hint on Deployment once a real choice is made.