Example AppHole Report

Observed. Tapping Pay on a 390px viewport returns an error before a checkout session opens.

Why it matters. A mobile customer cannot complete a purchase.

Plug. Fix the mobile payment handler and retest checkout on a 390px viewport.

URL. https://example-app.invalid/checkout

• example: Illustrated finding. Not from a live customer app.

Retest: Open /checkout at 390px and tap Pay. Confidence 96%. Category payment.

Observed. A new account reaches /dashboard with no projects, no instruction, and no visible primary action.

Why it matters. A first-time user can register and still fail to experience the product.

Plug. Route empty accounts to the first useful action or give the empty state a strong CTA.

URL. https://example-app.invalid/dashboard

• example: Illustrated finding.

Retest: Create a new account and stop on the first screen after verification. Confidence 90%. Category first run.

Observed. The reset URL returns an expired or 404 page immediately.

Why it matters. If login fails once, recovery is the only path back. Broken reset loses the customer.

Plug. Fix token validation and the reset landing page, then retest the full email link.

URL. https://example-app.invalid/reset

• example: Illustrated finding.

Retest: Request a reset and open the link in a fresh browser. Confidence 91%. Category signup login.

Observed. The product is usable, but nothing asks the user to buy, upgrade, or start a trial.

Why it matters. Building more features will not invent a purchase moment.

Plug. Put one honest paid action in the path. Then talk to buyers before adding plan tiers.

• example: Illustrated finding.

Retest: Walk a new user from value to a visible paywall or upgrade CTA. Confidence 80%. Category purchase moment.

Observed. The landing page says unlimited, while checkout shows a hard monthly cap.

Why it matters. Contradiction creates distrust. Confirm the intended offer before rebuilding billing UI.

Plug. Align landing copy with the actual entitlement, then verify checkout.

• example: Illustrated finding.

Retest: Compare landing, pricing, and checkout side by side. Confidence 77%. Category pricing.

Observed. A privacy link exists, but it is a one-line placeholder.

Why it matters. Real gap. Not a rational reason to postpone the first customer conversation.

Plug. Publish a short accurate privacy page. This is not legal advice.

• example: Illustrated finding.

Retest: Open the footer privacy link. Confidence 70%. Category privacy.

Observed. The primary happy path completed without a crash in this example.

Why it matters. Passes matter. AppHole is not trying to maximize issue count.

Plug. No plug required.

• example: Illustrated finding.

Retest: Repeat the core workflow on desktop and mobile. Confidence 84%. Category core functionality.