In this video· click a step to jump to it
Test recording
OurCouple — public + tools walkthrough
49,843 ms · 20,806 pixels changed
We built this regression test for ourcouple.app — it's yours to keep, free.
Take this test with you
This is a real Playwright test, recorded against ourcouple.app. Claim it into your own workspace and re-run it on every deploy — free.
export async function test(page, baseUrl, screenshotPath, stepLogger) {
const STAMP = Date.now().toString(36);
const findings = [];
async function shot(n, slug) {
await page.waitForLoadState('domcontentloaded').catch(() => {});
await page.waitForLoadState('networkidle', { timeout: 5000 }).catch(() => {});
const file = screenshotPath.replace(/\.png$/i, `-${String(n).padStart(2, '0')}-${slug}.png`);
await page.screenshot({ path: file, fullPage: true });
stepLogger.log(`shot ${n}: ${slug} (stamp=${STAMP})`);
}
Checks run
Notes from the demo run
AI-generatedOurCouple is iOS-only for the main app, but Vincent built a polished freemium web surface: eight interactive tools (anniversary calculator, love-language quiz, 36 questions, would-you-rather, truth-or-dare, couple quiz, date-night generator, bucket list) plus four audience landings (long-distance, new, busy, married) — a strong SEO-and-lead funnel that drives visitors to the App Store.
- Tools-as-lead-magnet patternThe /tools/* pages aren't an afterthought — they're the entire web product, deliberately scoped to single-session interactions that demonstrate value before pitching the iOS download. Anniversary calculator and Love Language quiz both work without an account.
- Audience-specific landings/for/long-distance-couples, /for/new-couples, /for/busy-couples, /for/married-couples — four parallel funnels rather than one generic landing. Clear who the founder is targeting at each step.
- Clean privacy + delete-account links in footerBoth surfaced in the global nav: signals a founder who's thought about the trust gradient an emotionally-intimate app needs to earn.
- No way to preview the app on webThe .app TLD primes a 'web app' expectation but every CTA routes to the App Store. Visitors on Android, desktop, or unfamiliar iPhone friends-of-couples cannot evaluate the actual product without commitment.
- Marketing routes 404 instead of redirect/signup, /login, /pricing, /features, /about, /contact, /support all 404 — common discovery paths from SERPs, blog posts, or memory. /#features works but only via in-page anchor. A simple Next.config redirect would catch these.
- Hash anchor navigation breaks Playwright recorder mid-flowNavigating to /#features ended the first test run with an EB-network-unhealthy error after a posthog request abort. Likely a benign interaction with anti-bot heuristics, but worth knowing — replaced with in-page scroll in the working test.
- /dashboard·404 — no web app exists
- /signup·404 — iOS download is the only signup path
3 visual changes
Share this run
Proof your app is not AI slop
This test was built for ourcouple.app — claim it free
One click copies the test and baseline screenshots into your own Lastest workspace. Re-run on every deploy and catch regressions before your users do — free, no card required.