Hustle #005 / The City Table

The City Table: eight steps, one build.

A table-planning app with guest rules and seating history. Encrypted sync, account isolation and the signup-code flow have been tested. The privacy policy remains a draft with owner details and legal review still needed.

What we did

01 / Choose one customer

2 October

Plan a dinner without starting the seating from scratch.

  • The founder asked for a table-plan maker. She wanted to upload guests and say who should not sit together.
  • The founder required seating history. The app should remember earlier neighbours so the next plan can avoid repeating them.
  • The founder required flexible tables. The plan needs different table shapes and sizes rather than one fixed layout.
02 / Check the idea and the costs

2-3 October

Check the planner and the storage route.

  • The agent scoped the seating tools. Guest lists, rules, dinner history and table layouts became distinct parts of the prototype.
  • The agent chose account-backed storage on Supabase. The database needed signed-in ownership rules before any real guest data could be accepted.
  • The agent kept hosting costs minimal for the prototype. Cloudflare Pages hosts the app; no pricing or billing has been launched.
03 / Give it a name and a home

3 October

Give the app its own name and home.

  • The founder chose The City Table. The agent prepared the app under that name.
  • The founder approved public hosting. The agent deployed the app on Cloudflare Pages and connected thecitytable.co.uk.
  • The agent kept the public face simple. The app and account route are available without a paid-plan or customer claim.
04 / Make one thing people can buy

3 October

Build and test the planner before charging.

  • The agent built the guest, rule and dinner screens. The planner supports guest tools alongside the visual table layout.
  • The agent added encrypted sync. A signed-in user can save and reload a workspace using a passphrase; the server stores ciphertext.
  • The agent left the paid offer unfinished. There is no live checkout, settled price or claim of sales.
05 / Put it in front of real people

3 October

Put a real app in front of the founder.

  • The agent delivered a private preview first. The founder could review the planner before a public deploy.
  • The agent found the preview's network limit. The hosted preview blocked external calls, so real sign-in testing needed normal web hosting.
  • The agent deployed the public app after approval. The Cloudflare Pages route made real backend testing possible.
06 / Learn from the first response

3 October

Fix the phone layout and prove the boundaries.

  • The founder flagged the mobile layout. She said the app looked better but was not mobile friendly.
  • The agent fixed phone, tablet and desktop layouts. It checked the welcome screen, plan, guests, rules, dinners and account menu without horizontal overflow.
  • The agent tested a fresh-session reload. The encrypted saved data came back unchanged; a wrong passphrase was rejected.
07 / Hand over one repeatable job

3 October

Make saved work safe to repeat.

  • The founder ran the database isolation test. The result confirmed a second user could not read, write or delete the first user's rows.
  • The agent tested two real confirmed accounts. The second account could create its own workspace but could not read or change the first account's workspace or snapshots.
  • The agent erased the test workspaces. Both accounts were left with no saved test guests or snapshots.
08 / Improve it, change it or stop

3 October

Fix signups. Keep the privacy gaps visible.

  • The agent connected Resend to Supabase. The 3 October test confirmed a signup email arrived and its code confirmed the test account. The app no longer relies on a single-use confirmation link.
  • The agent added a vault recovery code. The tested recovery route unlocks the workspace and requires a new passphrase and replacement code.
  • The agent published a draft privacy policy. The live app marks it pending solicitor review. Legal entity, address, contact details, date and inactive-account retention still need to be settled.
  • The agent disabled the domain analytics beacon. On 4 October, it found Cloudflare domain-level Real User Measurements enabled even though Pages Web Analytics was off. It disabled the separate setting and checked the live app; a 5 October read again found no beacon or RUM requests.
5 November 2026

Today's update

  • "Remove my plans from this device" is live for shared computers. It clears this browser's copy and signs the person out on that device, and it does not touch the encrypted cloud copy. It was tested with throwaway accounts on desktop and mobile. A minimum passphrase length is now enforced.
  • One narrow case is checked in code but not proven live: removal at the exact moment a sync is waiting to run. Close other City Table tabs first. On a shared computer, clearing the browser's site data is still the stronger step.
  • Plans are encrypted in the browser before upload, so the stored copy is encrypted.
  • Prepared but not active: an inactivity policy with a warning email before any deletion. Nothing is sent, no accounts are removed, and the privacy notice is unpublished with legal and retention decisions still open. When emails exist, "delivered" will mean the provider accepted it, not that it was read.
The build lesson

Biggest learning

  • A wipe must cancel or ignore any pending sync, and the guard has to be tested on the real served build, not only in source.
The next test

Next step

  • Settle the open privacy and retention decisions before anything automatic is switched on.