Speaker A
I went through more than 200 of the highest charting apps on the App Store.
Tim Gabe reveals 4 first principles design patterns from 6 standout apps that defy category norms to build million-dollar successes.
Key Takeaways
- Breaking category design assumptions can create unique, defensible products.
- Designing deeply for niche audiences prevents mass-market competitors from copying.
- Rebuilding interfaces around new technologies leads to category-defining innovations.
- Removing negative emotional triggers like shame can improve user data and retention.
- Incorporating social elements into traditionally solo experiences enhances motivation and engagement.
What the video covers
- Most top-charting apps copy category leaders, but a few break design rules to succeed.
- Tim Gabe identifies four first principles design patterns used by outlier apps.
- Pattern 1: Niche Depth - Teemo redesigned productivity for ADHD users with visual blocks instead of text lists.
- Pattern 2: Technology Rebuild - Cal AI rebuilt calorie tracking around AI vision, making the camera the homepage.
- Pattern 3: No Shame Tracking - MacroFactor removed guilt-based tracking, improving data quality and user trust.
- Pattern 4: Social Synchronization - Ladder converted solo workout motivation into a shared social experience.
- Each pattern challenges hidden assumptions in app categories to create defensible, category-defining products.
- Tim emphasizes rebuilding interfaces from first principles rather than adding features.
- He offers design strategy calls to help founders apply these frameworks.
- The video includes examples from multiple app categories and actionable insights for founders.
Chapters
- 00:00Introduction and Overview
- 00:43Tim Gabe's Background and Approach
- 01:22Pattern 1: Niche Depth with Teemo
- 02:14Teemo's Visual Planner Design
- 03:14Key Takeaway from Niche Depth
- 03:55Pattern 2: Technology Rebuild with Cal AI
- 05:20Cal AI's AI Vision Interface
- 06:12Takeaway: Rebuilding for New Technology
- 07:05Pattern 3: No Shame Tracking with MacroFactor
- 08:02MacroFactor's User-Centered Algorithm
Full Transcript — Download SRT & Markdown
Speaker A
And what I realized is that most are basically just well-marketed copies of the category leader. But then I found four exceptions. [music] These apps built million-dollar revenue by taking the design rules every other app in their category was following and
Speaker A
[music] turning them upside down. Same move in four completely different categories. All of them small teams doing something I call first principles design. In this video, I'll break down all the four patterns, including the exact design move each team made, why
Speaker A
competitors couldn't follow, and the framework you can apply to your own app. By the way, I'm Tim. I've been designing software for the last decade, helping companies like Spotify along the way.
Speaker A
And nowadays, I run my own design agency working with app founders every day. So, this is truly all I think about every day. Now, pattern one, something I call niche depth. The app that proves it is Teemo, a Copenhagen-based productivity
Speaker A
app that won iPhone app of the year in 2025. Every productivity app on your phone makes the same design assumption.
Speaker A
Tasks are text rows in a list. Notion, Apple Reminders, Todoist, Microsoft To Do. Open any of them and you see basically the same shape, a vertical list of strings with checkboxes. And when you compete in that category on the
Speaker A
mass market, you kind of have to compete on more list features, more views, more integrations, more automations. But here's the thing most founders building for niches miss.
Speaker A
A productivity app built for ADHD users does not look like Notion with a different font. It doesn't look like a cleaner to-do list. It should look entirely different. Like colored time blocks on a vertical timeline, pictures instead of words. Block sizes based on
Speaker A
how long the task takes. Again, Teemo proves it. Their initial target audience was neurodivergent users. And here's where the design move happens. Text rows work for the mass market because reading is relatively cheap. But for ADHD users, parsing a vertical list of strings
Speaker A
demands focused attention. And that's exactly the thing they have less of. So, Teemo refused the text row assumption entirely. Every task became a colored, illustrated block on a vertical timeline. Block size weighed by duration. Custom icons from a library of
Speaker A
thousands. The user didn't read their schedule. They saw it. Apple's editor citation called it, quote, "A visual planner and thoughtfully implemented AI." Now, before we look at the key takeaway here, quick thing. If you're building an app and you're trying to
Speaker A
figure out where your category's hidden assumption is, that's exactly what we do at Sips App.
Speaker A
You can check out the link to our free design strategy calls below. Now, the key product design takeaway here. When you design for a niche audience, the conventions of the mass market category are usually a trap. Teemo's blocks over
Speaker A
rows wasn't a niche trick. It was a complete reset of the interface. The win for you as a founder is that mass market apps cannot structurally follow you there. Notion will not ship illustrated time blocks for ADHD users because their
Speaker A
audience is just too broad. You own the niche by going deep on the interface, not by doing more of what the leaders do. So, niche depth is one shape of first principles design. The next shape is a bigger though. It's what happens
Speaker A
when a new technology lands in your category and the leaders try to bolt it on instead of rebuilding around it. The app that proves the pattern is Cal AI.
Speaker A
Now, Cal AI is being talked about by everyone right now because they had a massive breakout and they recently launched a second app in stealth doing over $300,000 in MRR just months after selling Cal AI to MyFitnessPal for an absurd amount of
Speaker A
money. So, what's going on here? These guys didn't win because they added a camera button to a calorie tracking app.
Speaker A
For over a decade, MyFitnessPal, the incumbent everyone copied, and funnily enough, again, the company that acquired Cal AI made the primary action add food, then a search field, then a scroll, then a select, then a confirm. Four to five
Speaker A
steps just to log a single meal. Every other calorie tracker competed on the same shape. More features, bigger databases.
Speaker A
All on the same playbook. Cal AI did it. Cal AI rebuilt calorie tracking from scratch around AI vision. The camera is the home page. The thing you do first is take a photo, not type, not search, just point and shoot. The AI identifies the
Speaker A
food, estimates portion size, and writes the entry for you. Correction is the exception, not the entry path. That's the definition of a first principles rebuild. It's built around one question.
Speaker A
What does AI let us do that we couldn't do before? This principle, however, is older than Cal AI, of course. Picture this launched in 2017 doing the same thing for plant identification. Point your camera at a plant and the app tells
Speaker A
you what it is. Image classification even before the current AI wave. So, here's the takeaway. When a new technology lands, whether that's better AI vision, voice, ambient compute, or whatever's next, breakout founders rebuild the interface primitives around the new tech. They don't bolt the new
Speaker A
tech onto the old UI. Camera as homepage wasn't a calorie tracking trick. It was a full reset of the food logging interface for a new technology era.
Speaker A
Founders who add a feature ship a feature. Founders who reset the primitives ship a category-defining product. Again, if you're looking at your product right now and you're wondering how to make it category-defining, that's exactly the kind of conversations
Speaker A
we care about at Zips App. So, if it sounds interesting at all, check the free design strategy call in the link down below. So, Cal AI rebuilt the interface around technology. The next pattern rebuilds it around the user's
Speaker A
emotional state. Pattern three, no shame tracking. The app is MacroFactor, a bootstrap team out of Stronger by Science. No outside funding. They charge $72 a year with 500,000 users as of this recording. And here's what MacroFactor saw that nobody else did. Every macro
Speaker A
tracker was built on a single assumption. Shame motivates compliance. Red numbers when you go over your target, broken streaks when you skip a day, push notifications that tell you that you missed your goal. The whole category competed on adherence pressure,
Speaker A
making users feel guilty when they slipped. Greg Nuckols, one of MacroFactor's co-founders, said it almost word for word. What if nutrition apps didn't try to guilt people into losing weight? So, they didn't. The MacroFactor algorithm assumed users were
Speaker A
going to miss targets. It expected it. It used actual logging plus a smoothing trend weight averaged over about 3 weeks to back calculate real metabolism. Then it adjusted targets accordingly. Here's the golden takeaway. Every category has an unspoken assumption about the user. In
Speaker A
macro tracking, the assumption was that users need pressure to stay on track. MacroFactor asked the obvious question, what if that assumption is wrong? Then they built the products around the opposite. So, look at what your category assumes about its user. Then ask if that
Speaker A
assumption is actually true. When you build for who your user really is, not who you wish they were, the data you get back is the data you can trust. That's the moat. MacroFactor stripped shame from the interface. The result, cleaner
Speaker A
data than every competitor that was competing on adherence pressure. Power users pay them for an algorithm MyFitnessPal can't replicate because MyFitnessPal's user-submitted database is full of bad data from people gaming their own logs. So, MacroFactor's lesson is partly about what you remove from the
Speaker A
interface. The last pattern is about what you add, and it's arguably the strongest one in this video because it converts something almost every app treats as a solitary into something social without ever asking the user to opt in. Pattern four, synchronize
Speaker A
ritual. The app is Ladder, an app of the year 2025 finalist. Now, here's the design assumption almost every workout app makes. Motivation is a solo experience. You and your phone alone doing the work. Maybe a leaderboard if you want to compare, but the actual
Speaker A
workout is private. Ladder refused that. They pinned every member of a team to the same workout the same day. About 5,000 strangers all doing the same set at the same hour. CEO Greg Stewart said it on the Sub Club podcast. They hit
Speaker A
500% growth. Their marketing funnel was TikTok to Quiz Up, and it converted a lot of users, but that's not what kept the users. The cohort calendar is what made them stay because skipping wasn't just personal failure anymore. It was
Speaker A
social. Your absence was visible to the whole cohort. So, remember this. If possible, try to convert solo interface moments into shared ones. Ladder's cohort calendar isn't motivation theater. It's social pressure baked directly into the workflow itself. Now, if you found this breakdown helpful at
Speaker A
all and you want to talk to us at ZipZap about first principles design, again, for the last time, I promise, check out the link down below. And also, if you're interested in more videos like this one, check out this one here somewhere. And
Speaker A
until the next one, have a great life.
Topics:first principles designapp designproductivity appsAI visioncalorie trackinguser experienceniche designno shame trackingsocial motivationapp founders
