Home / Articles / A browser for one / Versions / v1.1.0
A browser for one: what changed in v1.1.0
From v1.0.0 (2026-10-18, 7954fc4ea) to v1.1.0 (2026-10-18, this release), paragraph by paragraph.
0 paragraphs added, 0 removed, 5 changed in place, 46 unchanged. About 4 words added and 0 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
1 unchanged paragraph
Summary: The browsers on my iPhone have frustrated me to the point where I wantwould like to build one. Not a general browser: an app that only opens my newsroom, where I left it, knows what I have read, opens my vault, keeps my tabs, works offline, never reloads a page on its own, lets me build my own reading workflows, and receives what my agents send me. A year ago I would have put up with it. Now I can do something about it, and that changes how much bad interface I am willing to tolerate. This is the brief. The facts decide most of it. In the UK an iPhone app that browses the web must use WebKit; Firefox and Chrome on iOS are WebKit too. Passkeys inside an app and push notifications both need Apple's paid developer membership, and the app has to be built on a Mac, so not by a cloud session like the one that writes this site. The one real unknown is whether the passkey extension the vault depends on works inside an app's web view, so that is the first thing to test. And there is a second point, which matters more than the app. Once it works, it will be part of my day, and I will not want to maintain it. Not because I cannot; because it is not my focus. Being able to compile a Linux kernel does not mean I want to. Even power users will pay someone to keep the thing they built working, and this app is the first example I will live with.
3 unchanged paragraphs, under In short {#in-short}
• So Ithe wantidea is a browser for one. An app that only reads my newsroom, and knows what I have read.
27 unchanged paragraphs, under Why now {#why}, What it does {#does}, Which engine {#engine}…
The vault opens with a passkey and an extension called PRF, which turns the passkey into a key. Safari supports it for iCloud Keychain passkeys from iOS 18. No source I could find confirms that it works inside a web view in a third-party app. So the first thing the agent builds is the smallest app that tries the site's own unlock. If PRF does not come back, the app does the passkey ceremony natively and hands the result to the page. Either way, Iit wantis better to know on day one, not after the tabs are built.
1 unchanged paragraph, under Even power users want someone to maintain it {#maintain}
This is the part that matters beyond my phone. When this app works, it will be part of my workflow every day. And I will not want to maintain it. Not because I cannot; I could easily take the time. Because it is not my focus. I wantwould torather do something else. Being able to compile a Linux kernel does not mean I want to compile Linux kernels, and being able to code does not mean I want to spend my evenings keeping my own browser up to date with every iOS release.
That is the argument of software vendors as villagers, and now I am the customer. The explorer, me, builds exactly the app I want, which is a better brief than any document. Then I wantwould like to hand it to someone, a person or a company, and pay a couple of pounds a month for them to keep it working: rebuild it when iOS changes, fix what breaks, keep the behaviour policy current. Who will fix your mess asked who does that for companies; this is the same question for one person.
14 unchanged paragraphs, under The brief {#brief}, What this does not claim {#limits}, Where this comes from {#sources}