What would Steve Jobs do?
If Steve Jobs built his own website, it would not be a portal, a dashboard, or a brochure. It would be one thought, presented perfectly, on every screen he shipped it to.
First principles
Jobs treated design as a series of decisions about what matters. A website, to him, would be an exercise in choosing.
The hero is the thing itself. Visitors meet the product and its promise in the first three seconds, not an org chart, a slogan wall, or a history of the firm.
Focus is subtraction. One primary action per screen, one story told in order, and every element that does not serve it gets cut, however good it is on its own.
His most famous design line was that design is not the surface, it is how the thing works. Load time, tap targets, reading order, and what happens after the click are the design.
Apple controlled hardware, software, and the store, end to end. His website would own its whole journey too: the arrival, the scroll, the tap, the share, and the reason to come back.
Typography, spacing, and restraint carry the brand. When the layout is confident, the page does not need badges, banners, or decoration to prove it is good.
Every screen earns its place or gets rebuilt. The standard is not whether the page works. The standard is whether it feels inevitable.
Mobile and desktop
He would never ship a shrunken desktop page and call it mobile. The words, the order, and the one action stay identical. Only the staging changes.
On desktop
On mobile
The deletions
Before adding anything, he would walk the page with a red pen. Most of what modern websites open with would not survive the meeting.
Five messages rotating is zero messages delivered. Pick the one that matters.
Asking for an email before giving anything is a confession that the page has nothing to say.
One primary action. Everything else is a quiet text link, or it is gone.
A navigation that lists everything admits the site does not know what it is for.
Movement should explain something. Decoration that moves is still decoration.
The bottom of the page is a closing line, not a sitemap wearing a disguise.
The build order
The process is the philosophy, in sequence. Each step removes a chance to hide behind complexity.
If the page cannot be described in one sentence, it has no focus yet. Write the sentence first.
The hero carries the whole argument: product, promise, one action. Everything else is support.
The small screen exposes every lie. Fix the order, the words, and the tap targets there first.
Give the same truth more air. Wider staging, larger type, quiet comparisons. No new messages.
Then ship it, watch real humans use it, and refine. Perfection is a direction, not a delay.
Simple is not empty. Simple is everything unnecessary, removed.