TechCrunch UX Teardown: The Reading Mode That Drops the Date

Above TechCrunch's Startups feed sits a small switch labelled HEADLINES ONLY. Flip it and the page rebuilds itself: thumbnails gone, cards collapsed into rows, a line of topic tags appearing under every headline. Most publications decide how dense their feed should be and ship that decision to everybody. TechCrunch hands it to the reader. The choice follows you into the next section. That is a rarer move than it sounds, and the mode it produces quietly removes two of the things a returning reader is scanning for.

This teardown follows six public, signed-out states captured on 7 September 2026 at 1440×900, in English, from Brazil: the Startups feed, the switch, a story, the end of that story, the AI feed, and a site search.

One switch, two readers

The default Startups feed is image-led. Each story gets a thumbnail, a green eyebrow, a headline and a byline with a relative date: Anthony Ha - 1 day ago. It reads like a magazine, a layout tuned for the visitor who arrived from a link and needs to be told what matters.

Flip the switch and the same feed becomes a queue.

Each story is now three lines: an eyebrow, the headline, and a row of topic tags, with the author pushed out to the right margin. The rows are roughly a quarter shorter, so a little more fits on screen. The bigger change is that nothing competes with the words. Seven tags under the lead story (AI · Startups · Transportation · atoms · In Brief · Travis Kalanick · Uber) put the subject matter where the thumbnail used to be, which is a better trade for a reader who already knows the beat.

Then move from Startups to AI through the header, and the switch is still on. The preference survives the navigation, the toggle stays green, and the AI feed arrives already compact. That is Nielsen's flexibility-and-efficiency heuristic built properly: an accelerator for the experienced reader, sitting in plain sight for everyone else (NN/g).

What the accelerator takes with it

Compare one story across both modes and two things have changed that nobody announced.

The date is gone. In the default view the lead story reads Anthony Ha - 1 day ago. In compact mode it reads Anthony Ha, and that is all. There is no timestamp in the row at any position. In the AI feed, six consecutive stories carry a byline and no date between them.

The content type has been demoted. In the default feed that story is labelled IN BRIEF — TechCrunch's own tag for a short post — and carries a small green badge beside the headline. In compact mode the eyebrow reads ARTICLE, and In Brief reappears fifth in the tag row, set in the same weight, size and colour as Uber and Travis Kalanick. The story below it makes the same move: ROBOTICS in the default view, ARTICLE in compact, with Robotics third among its tags.

So the accelerator built for the frequent reader removes recency and flattens format: the two fields a frequent reader uses to decide what to skip. The type at least survives as a tag, ranked fifth and styled like Uber. The date is just gone.

The default eyebrow has its own inconsistency worth naming. One row says IN BRIEF, which is a format; the next says ROBOTICS, which is a subject. The same slot carries two different kinds of label depending on the story. That ambiguity is what compact mode collapses into a constant.

The newsletter block, and one crimson border

Read to the bottom of the piece and the tags come back as links: a Topics: row repeating the same seven, then a Newsletters block with four options.

The ask is well built. Four newsletters — Daily News, Mobility, Startups Weekly, StrictlyVC — each with one line of description and a + control, so choosing is a click and not a form. Beside them sits No newsletters selected., and under that a greyed-out Subscribe. That sentence is doing real work: it is a disabled control explaining its own condition, which is the part most disabled buttons skip. The consent line sits under the button rather than in a footer, and no field is required before a choice is made.

Then there is the colour. The email input's only styling is a crimson border, on an untouched field, with nothing typed and nothing wrong. Every other element in the block is black, grey or TechCrunch green; the one thing wearing an alert colour is the field that has not yet been used. Nielsen's error-message guidance reserves red for a specific job, and this field isn't doing it. A capture can't tell us whether that's a deliberate brand accent or a validation style leaking into the default state.

The archive still shows dates

Search the archive for robotaxi and the results page does several things right. The query is echoed as a heading, Robotaxi. Under it, Found 1,305 results. Under that, the search field with the term still in it, so refining means editing rather than retyping.

And the dates are back. Which is where it gets odd. Three consecutive results read Kirsten Korosec - Jun 17, 2026, Sean O'Kane - Jul 23, 2026, and Kirsten Korosec - 4 days ago. Two absolute dates and one relative one in the same list, so a reader comparing recency has to switch units mid-scan and do the arithmetic themselves (NN/g on consistency and standards).

The HEADLINES ONLY switch is also absent here. Density is a property of the category template, not of the reader. The preference that followed you from Startups into AI stops at the archive, and search returns you to thumbnails whether you wanted them or not.

What this means for your product

Steal the move. Let the reader set the density, then remember the choice across the session. A mode control that persists is worth more than a better default, because it stops you having to guess which of your two audiences is on the page. TechCrunch's is one switch, visible, in the content column, on by choice.

Then audit the deletions field by field. A compact mode is a set of decisions about what to remove, and those decisions deserve to be made one at a time rather than by dropping whatever the tighter row can't fit. Write down what the default row shows — type, headline, author, date — and ask of each one whether the reader who chose the faster view needs it more or less than before.

Two smaller things generalise past publishing. A disabled control should say what would enable it, the way this newsletter form does. And TechCrunch spends red on an empty field, which leaves it nothing to spend when a real validation error arrives.

Take it further

The lens behind this teardown — can a reader see what a control does, and what the interface stopped telling them once they used it — is the UX Clarity framework, the same one we apply in a Full UX Audit. For how that scoring turns into prioritized fixes, read what a real UX audit looks like.

Scope and limits: a signed-out capture of public pages only, at one viewport, on 7 September 2026. No login, registration, newsletter submission or purchase was attempted, and no advertisement was clicked. Headlines, result counts, relative dates and advertising reflect that moment and the Brazil region, and will have moved since. The homepage landing was outside this capture's scope.

Sources: NN/g — Visibility of System Status · NN/g — Flexibility and Efficiency of Use · NN/g — Error Message Guidelines · NN/g — Consistency and Standards.

Ready to find out what your interface stops telling people the moment they speed it up? Apply for a Full UX Audit →