Projects Dashboard

Dashboard

The private web app I use to run my week, with my plan for the day, the morning briefing, the radio station, a reading list and recipes.

You can’t log in, so the screens on this page are the real app running on sample data.

The Reading queue with saved articles and one saved screenshot of a bundle budget slide, its text transcribed on the card.
Real screen, sample data.

What It Does

The app opens on Today, and a few other screens stay private. There’s also a box I can type anything into. Simple rules handle what they can, and a model sorts the rest into a fixed list of destinations. If the model fails or isn’t confident enough, the item goes to a review queue with the reason attached, and I sort it myself.

The Briefing as it appears in the dashboard, with a Top Story and numbered Takes on a white page against a dark background.
Real screen, sample data.

How It’s Built

Dashboard is a Next.js app that handles sign-in and gets all of its data from a shared API. The website and the API share one set of contracts that define and check every request and response. The iPhone app uses the same API.

Keeping Data Private

The first thing the app serves is a static page with no personal data in it, so it can load from a CDN. Personal data arrives only after sign-in.

After every build, a script reads the HTML that was generated. If it finds an email address or a user ID, the build fails. The same script writes the page’s content security policy, which limits what scripts the browser will run.

When Something Fails

Slow or offline: the page shows its last good copy from the browser right away, then updates when new data arrives. Only a copy from today or yesterday can appear, and only for the person who saved it. Anything else gets deleted.

Expired sign-in: a sign-in token can expire while a laptop sleeps. When the API rejects a request, the app gets a fresh token and tries once more before treating me as signed out.

A broken API route: Today loads from one combined API route. If that route fails, the app builds the page from the older separate requests.