That morning, the “App of the Year” list almost pulled me in
Last Wednesday morning, I was in a Hangzhou café when I saw Apple’s annual app list. My first thought was: I need another project. But as I scrolled, every entry was a mature product. What I lack most as a side-project app builder isn’t inspiration; it’s knowing what validation will cost and whether I’ll waste a week. I later realized the lists are useful for spotting trends, not copying answers.
The list’s real value is spotting needs that keep coming back
These lists are public samples of demand. Lin Yue, a design-outsourcing friend of mine in Shanghai, saw a small utility nominated for an Apple App of the Year award. Instead of buying it immediately, she organized the user reviews and found that people were not annoyed by the interface; they hated having to “repeat the same setup every time.”
She turned “one-click organization of frequently used materials” into three mobile screens and gave them to eight target users to try. Real people were already using it, but its value wasn’t in its name. It was in the step it eliminated for users.
Today’s replication cost: money, time, and the first step
If I’m using the list only to choose a direction, it costs 0 yuan and about 30 minutes, with almost no technical barrier. The first step is to open Apple’s annual app page and note five products whose users resemble my existing customers.
To validate my own smaller version, the budget is 0–200 yuan, the time is roughly one to two days, and the technical barrier is simply being able to build a basic screen with an off-the-shelf editor. The first step is to write one sentence—“Help whom avoid what hassle?”—and then create a clickable draft.
I’ve made the mistake of “building first, finding demand later” before. The prettier the tool gets, the harder it is to stop polishing. It’s also fine not to test today; collecting feedback is enough.
Here’s how I’d use the lists at each stage
If I’m just starting out, I’d pick one product from the list and use a spreadsheet to record the problem it solves, user complaints, and pricing model—without rushing into development.
If I already have one or two customers, I’d compare the list with our chat logs, identify tasks they mention repeatedly, and build a two-screen version for them to try.
If I’m scaling, I’d have different team members organize the entertainment and games lists separately, then rank the ideas by “frequency of demand, evidence of willingness to pay, and production cost,” instead of looking at popularity alone.
The lists aren’t ready-made businesses. But they make excellent free demand radars.