Seeker Kitchen
Restaurant
A restaurant site built for the ninety seconds someone spends deciding where to eat tonight, on a phone, with the answer usually being hours and the menu.
This business is invented. It’s a concept build made to show how a site for this kind of business should work — not a real client, and not a real company.
The problem
Almost every restaurant website answers the wrong questions. Someone lands on it hungry, standing on a sidewalk or sitting in a car, and needs four things: are you open, where are you, what do you have, and is it any good. Instead they get a full-screen video, a story about the chef's grandmother, and a menu locked in a PDF that opens sideways on a phone. The decision takes seconds and the site spends them on itself.
What I built
- Open-or-closed answered at the top of the page as a state, not a table of hours someone has to read and compare against their watch.
- The full menu as real text on the page — searchable, linkable, readable at arm's length, and never a PDF.
- Dietary marks on every item, because the person with the restriction is usually the one choosing for the group.
- The one dish they are actually known for given its own place, rather than being the fourth item in a list of twenty.
- Address, parking, and a phone number for the things a website cannot answer.
What it does now
Someone can decide in under a minute whether to walk in, and arrives knowing what they want. The kitchen fields fewer calls asking whether they're open and what's on the menu.
What this shows
- Designing for a specific moment and a specific device rather than for a desktop screenshot.
- Treating content structure — a real menu, real hours — as the design problem, which on this kind of site it is.
- Knowing what to leave out. There is no video and no origin story above the fold.