Walk through any tech blog and read the product posts. You'll notice a pattern: they all talk about the hero feature. The new thing. The launch. The big swing.
What you almost never read about: the thing a user actually touches every single day.
The empty state
Pick any product you use. What's the first thing you saw when you signed up and it was empty? Probably a box with a plus sign and some grey text.
That screen got 15 minutes of thought from somebody, maybe. But you saw it on day one, and it was the first impression your brain formed about whether this thing was for you.
Good products take the empty state seriously. Great products make the empty state the second-best screen in the app, on purpose. You're asking someone to believe before there's any evidence. That's a real emotional ask.
The 3-day-old account
Another one nobody writes about: what your app looks like when the user has used it for three days and hasn't really committed yet.
- They've created a few things.
- The novelty is wearing off.
- The next open could easily be the last.
What happens on that open? Is there anything pulling them deeper? Or does it just look like the empty state, but with a few items?
Most products fall off a cliff here. The onboarding team shipped and moved on. The retention team isn't looking at day 3, they're looking at day 30.
Write about the middle
If you want to write about product and say something useful, skip the launch posts. Write about:
- The empty state.
- The moment after the novelty wears off.
- The error message when the user did something wrong.
- The part where they have to wait.
- The thing they touch 50 times a day and stopped noticing.
These are the parts of the product where craft actually shows. Everyone can ship a hero feature. Almost nobody makes the hundredth interaction feel good.
The great products are the ones where somebody cared about number 100.