End-to-end walkthrough of what a customer sees: discover, create a code, sign up, manage & delete codes, and buy a plan. Live screens from mayqr-next.pages.dev; dashboard screens are the chosen dense design.
Lands on the homepage: drag-to-compare hero, the mini builder, real codes, the analytics teaser, pricing.

Opens the full builder at /create: enters a URL, then styles colors, corners, logo, dot shapes, stroke, AI art. A live scannability meter (Great / Good / Check) reassures them it will scan.

Creates an account to save and track codes.

mayqr/v1/auth/register, which does not exist on the backend yet (decision HND-627: build the auth routes wrapping WP). Until then, sign-up 404s.Returning customer signs in; the WP session cookie flows once the app is same-origin with mayqr.com.

The chosen dense dashboard: live scan totals, scans-over-time, visits-by-code donut, an hour x weekday heatmap, and a searchable per-code table with trends. Fully responsive - on a phone the KPIs go 2-up and the table becomes cards.


Opens a code: rename, edit tags, toggle Basic/Smart, and retarget the destination URL - which instantly changes where the already-printed code points, no reprint. Plus this code's own analytics.


The Danger zone on the manage screen: Delete disables the code and stops the redirect (revivable later). A confirm step prevents accidents.
DELETE /codes/{id} + /codes/{id}/revive - both already exist on the API.Four tiers (Free / Standard $4 / Pro $9 / Max $29). On mobile this is a swipe carousel.

This is the open question (HND-625). Checkout + recurring billing stay on WooCommerce either way. The choice is whether the account screen (profile, password, plan/usage) is native or the old WooCommerce My Account.