Prefetch the list, not the letter
A mailbox that prefetches the headers in view and waits until the click to load the body, then keeps that body for the return visit.
- Category
- Developer tools
- Who it is for
- A team whose inbox prefetch is already the slow part.
- Possible model
- Open source
- Difficulty
- Medium
- Inspired by
- Stamp · Aurora Scharff
- Original launch
- Watch the launch · Oct 7, 2026
Difficulty is an editorial estimate of technical and operational complexity, not a score.
Startup idea analysis by Startup Ideas. Last reviewed Oct 7, 2026. How we read a launch.
The startup idea
Aurora Scharff, who works on Next.js docs, says she built Stamp, a Gmail-style inbox, to explore the navigation() API. The reply links a live demo at next16-mail.vercel.app and the repo aurorascharff/next16-mail. The post says visible links prefetch each thread's header, and the message bodies wait until the click, then get reused on the way back. The post says Next.js 16.4. The repo description says 16.5. The readme calls it a demo, MIT, not a mail company. This page did not sign in. The demo page this review opened only showed a compose control.
The opportunity is the wait, not another inbox. People skim. They open two threads. Prefetching every body is the cost. A smaller product is one list, headers first, bodies after the click, and a sentence that says this build is a demo of the API. If you cannot say which version of the framework you tested, quote both numbers the way the post and the readme disagree.
Do not sell Stamp as email hosting. She did not. Do not pick 16.4 or 16.5 and drop the other. Do not treat the names in the film as customers.
The problem
Opening the inbox downloads every message, including the ones nobody opens.
Who would pay for this?
- Primary
- A team whose inbox prefetch is already the slow part.
- Secondary
- A developer who wants the pattern, and will read the demo before copying it.
- Early adopter
- One list you already have, headers in the prefetch, one body after the click.
How could it make money?
Possible models. Nothing here is a claim about what Aurora Scharff charges.
- Stamp does not charge. The repo says it is a demo. Do not invent a price.
- The cost worth naming is the prefetch the customer already pays their host for.
- MIT means they can read it. It does not mean you host their mail.
What would the MVP look like?
- One list.
- Headers in the prefetch.
- Bodies after the click, kept for the return.
- A line that names the framework version you actually ran.
- A line that this is a demo, if it is a demo.
How to validate the idea
- Time one inbox with bodies in the prefetch and one without.
- If the return visit is not faster, the cache is the part you do not have yet.
- Do not add a second account type until one list is honest about what it prefetched.
How to differentiate
- The body waits.
- The header does not.
- Say demo when it is a demo.
- Do not become a Gmail client. The pattern is the product.
Why this could be interesting now
The post shows a mailbox that refuses to prefetch the letter. The opening is that wait, on one list, with the version written down.
Original product launch
This launch is inspiration and evidence that someone shipped, not a partnership. The idea above is our reading of the broader opportunity. Aurora Scharff did not write it.
- Product
- Stamp
- Source
- Aurora Scharff
- Film
- Stamp, a mailbox that waits for the click
- Posted
- Oct 7, 2026 · 0:20
Product that inspired this idea
Aurora Scharff says she built Stamp, a Gmail-style inbox, to try the navigation() API. The repo calls it a demo, MIT. The post says the bodies stay out of the prefetch and load after the click. The post says Next.js 16.4. The readme says 16.5.
Posted by @aurorascharff. Watch the original launch. No separate product site is listed unless the post itself is the source.
- nextjs
- demo
Related startup ideas
- A browser inside the coding agent’s terminal
Open a real browser from the agent session so the agent can see the page it just changed.
- A coding agent that runs a small model in the browser
A coding assistant that runs locally in the browser on a small model, for people who will not send the repo out.
- A desktop for making games with the model you already pay for
A local app that turns a Claude or ChatGPT subscription, or a local model, into a game-making bench.
- A drive that files the document and cites the page
Upload a pile of files, have them land in a folder a person would recognize, and answer a question with the page it came from.
- A record of whether the setup actually worked
Show a trader how often a setup played out, with the sample size next to the number, on data they already have.
- A rich-text editor you can install in one command
Ship a styled editor that matches the rest of a component library, instead of theming a blank one for a week.
Looking for more ideas?
The full list is startup ideas for 2026, each one tied to a launch you can watch.
Browse startup ideas for 2026