web-browser is a general-purpose, everyday web browser built for its single maker-user, Oluwacoded. The product intent is a browser that is fully functional: it must let its user open the application, enter or follow a URL, load and read real web content, and navigate between pages within a session — reliably, every day, without ceremony.
The audience is the requester themself. This is not a multi-tenant product, not a team tool, and not a marketing surface. It is a precision instrument for daily use: the chrome must be legible at a glance, the state of every control unambiguous, and the content — not the application — must be the hero of the surface.
The design authority for the product is a Dieter Rams reading of the browser: less, but better. Warm off-white ground, graphite controls, exactly one signal colour, ruled tabular lists instead of card grids, and motion that is mechanical rather than expressive.
The current delivery is a custom-UI web application with two first-party pages:
Both pages are owned by the application and both are reachable without any account or sign-in. There is no identity establishment, no login, no registration, and no session-ownership requirement anywhere in the accepted scope: the accepted journeys are single-user, local, and continuous within a browsing session. No differentiated permissions, roles, or visibility controls exist, because no authoritative source establishes differentiated control over shared product state.
The single accepted human actor is the Browser User — the person who uses the browser as their everyday tool to reach the web.
Delivery ownership. The browser is delivered as a first-party web application. The Landing page and the Browser workspace are both application-owned custom pages. There is no provider-owned surface, no external destination, and no headless delivery in the accepted scope.
Access ownership. Both pages are anonymous-access surfaces. The user is never asked to create an account, sign in, or verify identity in order to browse. This is a hard, source-backed access fact from the accepted page contract, not a provisional default: the accepted journeys begin at the Landing page and continue directly into the Browser workspace with no identity step between them.
Current boundary. Current scope is: a public entry page that explains the browser, and a browsing workspace that accepts a URL, loads the requested web content, renders it for reading, and supports navigation within the session — including going back, going forward, reloading, and following links from loaded content. The browser must be fully functional for this everyday use.
Future boundary. Nothing in the authoritative thread commits to a future horizon. Features conventionally adjacent to a browser — bookmark management, history management, settings, tab management, extensions, sync, profiles, downloads, developer tools — are not accepted current requirements and are not current pages. Where the creative direction names ruled tabular treatments for bookmarks, history, and settings, that is a visual language for ruled lists and micro-labels, not an accepted capability; no bookmark, history, or settings page or feature is created by this document.
Exclusions. No account system, no authentication, no permissions model, no multi-user state, no provider-owned browsing surface, and no adjacent browser-suite modules are in scope.
ENGINE — Blink, PRIVACY — Local only, STATE — Fully functional.Open the browser — the single primary CTA, graphite with a 2px orange left edge, which hands the user into the Browser workspace.web-browser), the three label/value facts, the line-art browser diagram.Open the browser; 1px graphite border, orange 2px left edge, 1px inset shadow on press.GO label in 12px uppercase Archivo) to load that page.GO label; 2px orange focus ring offset by 2px.FR-1 — Open the browser from a public entry page. (provenance: explicit — "a web browser"; page contract: Landing) As a Browser User, I should land on a public page that explains the browser and offers one clear way in, so that I can start browsing without any setup.
Open the browser CTA.FR-2 — Enter a URL and load that page. (provenance: explicit — "fully functional"; page contract: Browser) As a Browser User, I should type or paste a URL into the URL field and commit it, so that the browser loads that page and shows me its content.
GO label or the Enter key.FR-3 — Follow a link inside loaded content. (provenance: explicit — "fully functional"; page contract: Browser) As a Browser User, I should click a link in the page I am reading, so that the browser loads the linked page in the same workspace.
FR-4 — Go back and forward within the session. (provenance: explicit — "fully functional"; page contract: Browser) As a Browser User, I should move backward and forward through the pages I have visited in this session, so that I can return to something I was reading and come back again.
FR-5 — Reload the current page. (provenance: explicit — "fully functional"; page contract: Browser) As a Browser User, I should reload the page I am on, so that I can recover from a stale, partial, or failed load.
FR-6 — See unambiguous load state at all times. (provenance: explicit — "fully functional"; page contract: Browser) As a Browser User, I should always be able to tell whether a page is loading, loaded, or failed, so that I never have to guess what the browser is doing.
FR-7 — Read the current URL exactly as resolved. (provenance: explicit — "fully functional"; page contract: Browser) As a Browser User, I should see the resolved URL of the page I am on, including scheme, host, port, and path, so that I always know where I am.
FR-8 — Use the browser for general everyday use without setup. (provenance: explicit — "fully functional", "general everyday use by the requester (Oluwacoded)") As a Browser User, I should be able to open the browser and start browsing immediately, every day, without creating an account, signing in, or configuring anything first.
Product context. The Browser User is Oluwacoded — the maker and the sole everyday user of this browser. They are not evaluating the product, not administering it, and not sharing it. They open it many times a day, on the same machine, and they stay inside it for long stretches. The browser is the surface through which they reach everything else on the web, which means the browser itself must be the least interesting thing on screen.
Primary goal. Reach a specific page on the web quickly and read it without friction — and be able to move around the web from there without losing their place.
Distinct accepted responsibilities.
Relevant inputs and decisions. The URL string (including scheme, host, port, and path); whether to commit the typed address or follow a link already on the page; whether a disappointing result means "wrong address" (edit and recommit) or "bad load" (reload); whether to go back or push forward.
Interactions with other accepted participants. None. The Browser User is the only accepted human actor in this product. There is no second participant, no counterparty, no recipient, and no administrator. The only other actors are non-human: the remote web servers the browser requests pages from, and the browser's own loading process.
Observable success. The requested page renders in the viewport, the URL field shows the resolved address, the load indicator has stopped, and the user can read the page and move on from it — with back, forward, and reload all behaving exactly as their state suggests.
What makes this role's work different. This is not a role defined by permissions, collaboration, or workflow handoffs — it is defined by continuous, low-attention tool use. The Browser User's competence is expressed in muscle memory: address, enter, read, back, address, enter. Every requirement in this document exists to keep that loop uninterrupted and to make the browser's state legible without the user having to look for it.
ENGINE — Blink, PRIVACY — Local only, STATE — Fully functional), and the graphite Open the browser button with its orange 2px left edge.Open the browser. The button depresses 1px with an inset shadow.GO label.Muse: Dieter Rams. Headline idea: Less, but better — a browser as a precision instrument. The register is trust, calm, and mechanical reliability: a well-machined tool that disappears behind the content, with controls whose function is legible at a glance and whose state is never ambiguous. Braun-radio energy, not SaaS-dashboard energy.
| Role | Light mode | Use |
|---|---|---|
| Background | #F2F0EC | Warm off-white paper ground; carries the whole app |
| Surface | #FFFFFF | Cards, panels, and the browser viewport itself, so web content reads true |
| Text | #161514 | Near-black body and heading text at 16px+ for AAA contrast |
| Primary | #1C1B1A | Graphite "anodised aluminium": nav, tab bar, primary controls |
| Accent | #E8590C | Braun orange — the single signal colour |
| Muted | #8A867E | Secondary labels, URL scheme text, disabled states |
| Divider | #D9D5CE | 1px hairlines between ruled rows and sections |
Accent discipline. Orange #E8590C is reserved for exactly four things: the active tab underline, the focus ring, the loading progress bar, and the single primary CTA on the Landing page. No second accent. No blue or indigo anywhere — not #2563EB, not #4F46E5, not bootstrap blue, including links, which are graphite with an orange underline.
Ratio. ~70% warm off-white, ~20% graphite, ~8% white surfaces, ~2% orange.
TABS, BOOKMARKS, HISTORY, SETTINGS).Rounded-rectangle controls with small, consistent radii: 4px on buttons and inputs, 6px on cards and panels, 8px on the browser window itself. No pills, no blobs, no organic curves. Every interactive element carries a 1px graphite hairline border and a subtle 1px lighter top-edge highlight suggesting a machined surface. Focus is a 2px orange ring offset by 2px. Pressed buttons take a 1px inset shadow — the click should feel mechanical, not springy.
A strict 12-column grid, 24px gutters, 32px outer margins on the Landing page. The browser chrome uses a dense but ordered modular layout: a 40px tab strip on top, a 44px toolbar (back / forward / reload / URL / bookmark) beneath it, and the viewport filling the rest. Label/value pairs align in ruled rows — bookmarks, history, and settings are tabular lists, never card grids. Section dividers are 1px hairlines in #D9D5CE. Nothing floats; everything sits on the grid.
Diagrammatic and schematic, never photographic. The Landing page uses a single line-art illustration of the browser window in 1px graphite strokes on the warm ground, with the orange accent marking the active tab. Icons are drawn on a 20px grid with 1.5px strokes — geometric, legible at small sizes, a family of honest pictograms (back, forward, reload, star, lock, plus, close) that read like transit signage. No stock people, no 3D renders, no gradient blobs.
The Braun control panel, not a SaaS hero.
The Landing page is a single full-width off-white stage (#F2F0EC) composed on the 12-column grid. A 96px Archivo headline sits flush-left across columns 1–8: "A browser that gets out of the way." To its right, in columns 9–12, sits a precise 1px line-art diagram of the browser window drawn at actual scale, with exactly one orange active-tab underline as the only saturated mark on the page.
Below the headline, a ruled row of three label/value pairs — ENGINE — Blink, PRIVACY — Local only, STATE — Fully functional — separated by 1px hairlines in #D9D5CE, with 12px uppercase Arch

web-browser
Window at actual scale · 1px strokes
Product facts

web-browser
Window at actual scale · 1px strokes
Product facts
No comments yet. Be the first!