DEV Community: Iris

Why I Started Treating My Photo Gallery Like a Garden

Iris — Fri, 17 Jul 2026 05:40:15 +0000

Last month I opened my phone gallery and saw a number that stopped me: 11,437 photos.

The funny thing is, I could not tell you what 80% of them are. Screenshots of wifi passwords from 2022. Five nearly identical selfies. A receipt I photographed just in case and never looked at again.

The real problem was not storage. My phone had plenty. The problem was the feeling: every time I opened the gallery, I felt a low-grade anxiety I could not explain.

What changed

I started using a tool called Swipe Cleaner, and it reframed the whole experience. The mechanic is simple: swipe left to delete, swipe right to keep. Nothing gets deleted until you confirm the batch at the end.

What struck me was not the speed. What struck me was the agency. Each swipe was a small decision, and each decision made the next one easier.

The privacy part

Your photo gallery is probably the least secure thing on your phone. Screenshots of bank transactions. Photos of your passport. Private conversations. Medical documents. All mixed in with selfies.

Swipe Cleaner does not upload anything to the cloud. All processing happens locally on your device. You are not trading one privacy problem for another.

It is not about minimalism

I do not believe you need to own less than 100 things to be happy. But I do believe curation is a form of self-care.

Choosing what to keep and what to let go of, even in something as mundane as a photo gallery, is practice for bigger decisions.

My gallery is not spotless. But when I scroll through it now, I see my life, not a landfill of forgotten screenshots. And that small change had a surprisingly large impact on how I feel about my phone.

How a Non-Researcher Follows AI Papers Without Drowning

Iris — Wed, 15 Jul 2026 10:48:35 +0000

Disclosure: I contribute to the OpenNomos ecosystem, which Paper List is part of. Opinions and reading habits below are my own.

I'm not a researcher. I work in brand and content strategy, and a growing part of my job is understanding where AI is actually heading — not where the loudest thread on my timeline says it's heading.

For a long time my "system" for following AI research was embarrassing: bookmark an arxiv link someone shared, feel productive, never open it again. My bookmark folder wasn't a reading list. It was a graveyard with good intentions.

Here's what finally worked for me, as someone who reads about papers more than she reads papers.

The real problem isn't volume, it's ordering

Everyone says the problem with AI research is volume — hundreds of papers a day, impossible to keep up. True, but incomplete.

The deeper problem is that most of us encounter papers in engagement order: whatever got quote-tweeted the hardest this week. Engagement order is great for discovery and terrible for understanding. You see the outliers, never the baseline. You know the three papers everyone joked about, but you can't answer a basic question like: is this topic growing, or is it three people being loud?

For a non-researcher, that distinction matters more than any individual paper. My job doesn't require me to reproduce results. It requires me to know which directions are compounding and which are noise.

Switching from "feed" to "shelf"

The mental shift that helped: stop treating research as a feed to keep up with, and start treating it as a shelf to walk past occasionally.

A feed punishes you for being away. A shelf just sits there, organized, waiting until you have a real question.

Concretely, my questions usually look like:

Is retrieval-augmented generation still an active area, or has it been absorbed into something else?
When did diffusion models jump from vision venues to everywhere?
What did last year's NeurIPS actually emphasize, versus what Twitter said it emphasized?

None of these are answered by reading one paper. All of them are answered by looking at topic × venue × year — which is a browsing structure, not a feed.

How I actually do it now

The tool I use for this is Paper List. It organizes papers from top venues by topic and year, which sounds almost boringly simple — and that's the point.

My routine, maybe twice a month:

Pick one question, not a topic. "Is agent evaluation maturing?" beats "let me check on agents."
Scan the topic across 2–3 years. Count roughly, don't read. Ten minutes tells you whether a direction is expanding, plateauing, or migrating between venues.
Pick at most two papers whose abstracts directly touch my question. Read the abstract, intro, and conclusion. Skip the math without guilt.
Write three sentences in my notes about what changed since I last looked. If I can't write them, I didn't actually learn anything — scan again.

That last step is the whole system, honestly. The tool gives you structure; the three sentences force synthesis. One without the other doesn't stick.

What this replaced

Before: forty open arxiv tabs, a bookmark folder I feared, and a vague anxiety that everyone else understood "the state of AI" better than I did.

After: a shelf I visit with a question, and a notes file that slowly became my own timeline of the field. When someone asks "is X still a thing," I can answer with a shape — growing since 2023, mostly at ICLR, spreading into ACL — instead of a shrug or a hot take.

The anxiety didn't fully disappear. But it turns out most of it was never about missing papers. It was about having no structure to put them in.

If you're also a non-researcher

You don't need a daily reading habit. You need:

a recurring question, tied to your actual work
a structured place to check it against (topic × venue × year)
a tiny writing ritual to force synthesis

That's sustainable at two hours a month. Keeping up with a feed is not sustainable at any number of hours — I've tried.

If your bookmark folder is also a graveyard, maybe don't organize the graveyard. Change where the papers live instead.

The hardest part of building an MVP isn't the code

Iris — Tue, 14 Jul 2026 08:53:16 +0000

I've lost count of the side projects I've watched die. Mine, friends', people in Discord servers. What surprised me is how few of them died because of code.

They died at three predictable spots:

Ten ideas in your head, none of them started.
You're great at prompting an AI, but that's a long way from a product someone uses.
You shipped a demo, posted it once, and then... nothing.

If you've built anything on the side, you've probably parked at one of those three lights. I've sat at all of them.

An MVP is a decision, not a smaller product

The phrase "minimum viable product" gets read as "the small version of the big thing I'll build later." That framing is a trap. It turns the MVP into a shrunk-down feature list, and you spend your energy deciding what to cut instead of what to learn.

The version that actually works for me is boring: an MVP is the cheapest thing you can build that forces a real decision. Not "does this look done," but "does anyone care, and what do they do next."

That reframe changes what you build:

Scope by one problem and one user. Not a persona — a specific person you could message today. If you can't name them, the idea is still a vibe, not a product.
Ship something a stranger can actually open. A demo you narrate over a screen-share doesn't count. The moment it's on its own in someone else's hands, you learn things no amount of internal polishing reveals.
Go get the first user before you build the second feature. Feedback, not your roadmap, picks what's next.

None of that is about frameworks. It's about resisting the urge to keep building because building feels productive.

The part AI quietly made worse

Here's the uncomfortable bit. AI is genuinely incredible at collapsing the cost of building. I can scaffold auth, payments, a dashboard, and a docs site in an afternoon now. Two years ago that was weeks.

But notice which of the three graveyards that helps with. Only the middle one, and only partly.

AI makes demos cheaper. It does nothing for "I have ten ideas and started none," and it makes "built it, posted once, then nothing" more common — because now everyone can produce a shiny demo, so a shiny demo is worth even less. The bottleneck moved. It used to be can I build this? Now it's is this worth building, and will I put it in front of a real person before I lose interest?

The skill that's appreciating isn't prompting. It's taste plus follow-through: picking a narrow problem, shipping the ugly-but-real version, and staying in the loop long enough to hear "this is annoying, fix that."

A smaller loop that actually finishes

When I stop treating the MVP as a mini-product and start treating it as a decision loop, projects stop dying. The loop is small on purpose:

Pick one problem → build the smallest real thing → put it in front of one person → let their reaction choose the next move.

Read one chapter, do one step. The goal of week one isn't a launch. It's a single honest reaction from someone who isn't you.

The projects that survive aren't the ones with the cleanest code or the best model. They're the ones that got out of the builder's head early enough to be corrected.

Full disclosure: I help out with 01MVP, a hands-on playbook that documents this exact 0→1 path — choosing an idea, building the MVP, going live, finding your first users. The three traps above are the real point, though. Use whatever tools you like; just don't die at light number three.

The MVP I Deleted: What Cutting 80% of My First Product Taught Me About 0 to 1

Iris — Mon, 13 Jul 2026 08:49:11 +0000

Disclosure: I contribute content in the OpenNomos ecosystem, and this post references 01MVP, a 0-to-1 build-and-launch guide. The lessons below are my own and apply to any first product.

My first MVP took three weekends. It had authentication, a settings page, light and dark themes, and a dashboard with three empty chart widgets waiting for data that didn't exist yet.

It had zero users.

Not "a few users who churned." Zero. I had built a product that could do a dozen things adequately and nothing memorably. I'd spent my scarce building time on the parts of a product that only matter after someone already cares.

Here's what I learned when I deleted almost all of it.

The trap: building the frame before the picture

Auth, settings, theming, and account management feel like progress because they're concrete and you know how to build them. There's a Stack Overflow answer for every step. So they become a comfortable place to hide from the actually hard question:

What is the one thing this product does that makes someone come back?

If you can't answer that in a single sentence, no amount of dark mode will save you. I couldn't answer it. That was the real bug.

The fix: one screen, one job

I stripped the project down to a single screen that did exactly one thing, end to end. No login. No settings. No persistence beyond the current session. If you opened it, you could get the core value in under ten seconds.

That version shipped in two days.

Five signups came the same week — not from a launch, just from sharing that one screen with people who had the problem. The difference wasn't marketing. It was that the value was finally visible instead of buried behind three layers of scaffolding.

A scoping checklist that actually cuts

When I catch myself over-building now, I run through this:

Name the core loop in one sentence. "User does X, gets Y, wants to do it again." If the sentence needs an "and," you have two products.
Delete every feature that isn't inside that sentence. Auth is usually not in the sentence. Settings almost never are. Onboarding tours definitely aren't.
Fake the boring parts. No user accounts? Use a URL param or local storage. No billing? A Stripe payment link is a backend. Manual is a feature at this stage.
Measure return, not signups. The first real signal isn't "people signed up." It's "someone came back without being reminded."
Set a two-day ceiling. If the smallest useful version takes more than two days, the scope is still too big. Cut again.

Why "manual is a feature" matters

The instinct is to automate everything up front because automation feels like the professional way to build. But automation is expensive to build and cheap to add later. Doing things manually — a spreadsheet, a DM, a copy-pasted email — lets you learn what's actually worth automating.

Every hour I spent building a settings page was an hour I didn't spend watching a real person use the core loop and get confused at the exact spot I'd assumed was obvious. That confusion is the most valuable data a 0-to-1 product can produce, and you only get it by shipping the smallest thing that works.

The uncomfortable part

Cutting is emotionally harder than building. Building feels generative; deleting feels like admitting the last three weekends were partly wasted. They were. That's fine. The weekends taught me the shape of the problem, and the delete taught me the shape of the solution.

Going from 0 to 1 is not mostly a building problem. It's a subtraction problem. The hardest engineering decision early on is almost never "how do I build this" — it's "what do I refuse to build yet."

If you're stuck on your first MVP

Try this today: open your project, write the core loop as one sentence, and comment out or hide everything that isn't in that sentence. Ship the remainder to five people who have the problem. Watch what they do.

You'll probably be surprised by how little you needed — and how much clearer the next step becomes once real people are in the loop.

If you want a structured walk-through of the full arc — choosing an idea, building the smallest MVP, going live, and finding your first users — the 01MVP guide on OpenNomos lays it out end to end.

What's the one feature you're building right now that isn't in your core loop sentence? That's probably the one to cut first.

I Built 7 MVPs in 12 Months — Here's What Actually Worked

Iris — Sat, 11 Jul 2026 02:54:28 +0000

After a year of shipping MVPs, I've learned one thing: the biggest enemy isn't bad ideas — it's overbuilding before you have a single real user.

Here's the pattern I kept repeating:

Get excited about an idea
Spend 3 weeks building a "complete" product
Launch to crickets
Abandon it

Then I changed my approach entirely. Here's what worked.

The 72-Hour MVP Rule

My new rule: if I can't ship a usable version in 72 hours, I'm building too much. This forces brutal prioritization:

Day 1: Core functionality only. No auth. No onboarding. No settings page.
Day 2: One workflow that actually works end-to-end.
Day 3: Polish just enough so it doesn't look broken.

The first MVP following this rule got 12 signups in 24 hours. Was it ugly? Yes. Did people use it? Also yes.

Stop Building What Nobody Asked For

I used to build features I thought users would want. Now I build only what users ask for — and only after 3+ people ask for it.

This single change eliminated about 60% of my development time.

The Tool That Changed My Workflow

One thing that helped tremendously: using tools designed for rapid prototyping. I've been exploring 01MVP — it's built around the idea of turning a concept into a demonstrable prototype quickly, without getting bogged down in infrastructure decisions.

The philosophy resonates: validate before you invest.

The Uncomfortable Truth

Your product is probably too complex. Strip it down to the one thing someone would pay for. Ship that. Then iterate.

The best feedback comes from real users, not from your imagination of what users might want.

What's the fastest you've gone from idea to shipped MVP? I'd love to hear stories in the comments.

This post is part of my Build in Public journey. Follow along at @irislinl7r8.

Why I Switched to a Meditation App That Doesn't Want My Data

Iris — Fri, 10 Jul 2026 04:38:44 +0000

Every meditation app wants to be your daily habit. They send notifications, track streaks, build communities, and gamify the practice of doing nothing. But somewhere along the way, the tool meant to help you disconnect becomes another platform you have to manage.

I've been using OneZen for the past two weeks, and it made me rethink what a meditation app should be.

What Most Apps Get Wrong

The dominant meditation apps follow the same playbook as social media platforms: retention at all costs. They bombard you with:

Daily streak notifications — because missing a day means you failed
Social features — compare your practice with friends and strangers
Content libraries — endless courses narrated by celebrities
Premium subscriptions — the "best" features locked behind paywalls

The irony is impossible to miss. You open the app to reduce stress, and it immediately reminds you of all the things you haven't done.

What OneZen Does Differently

OneZen takes a deliberately minimalist approach:

No account required. You open the app and start meditating. That's it.
No streaks. Meditate when you need to, not because a counter told you to.
No social features. Your practice is yours alone.
No cloud storage. All records stay on your device.
Completely free and open source.

The feature set is intentionally small: a configurable timer, a selection of natural sounds (rain, stream, birdsong), basic breathing guidance, and locally stored practice records.

Why This Matters

There's a deeper design philosophy here worth paying attention to. When a meditation app adds streaks and leaderboards, it subtly reframes meditation from an intrinsically motivated practice into an extrinsically motivated one. You're no longer meditating because you want to be present — you're meditating to keep a number going up.

This isn't just about meditation. It's a pattern we see across wellness tech: tools that start with a genuine intention to help, then gradually transform into engagement-optimized platforms that need you to keep using them.

OneZen makes a conscious trade-off: it sacrifices engagement for integrity. It's okay if you only use it twice a week. It's fine if you forget about it for a month. The app doesn't have a business model that depends on capturing your attention.

Who Is This For?

If you're deep in the indie maker / open source world, OneZen represents something familiar: software built for users, not investors. No growth hacking, no retention metrics, no dark patterns.

If you just want to sit quietly for a few minutes between coding sessions, or before sleep, without being marketed to — this is worth checking out.

Sometimes the best tools are the ones that know when to get out of your way.

The 2-in-1 Dev Toolkit I Use Every Day (That Nobody Talks About)

Iris — Thu, 09 Jul 2026 02:07:51 +0000

Disclosure: I contribute to OpenNomos, the ecosystem behind this project.

There are hundreds of online dev tools out there. JSON formatters. Timestamp converters. URL encoders. Regex testers. Most of them are single-purpose, ad-riddled, and forgettable.

json.opennomos.com is different. It's a clean, two-in-one toolkit that handles the two things I do most often:

Timestamp Converter

Auto-detects seconds vs milliseconds. Two-way conversion between timestamp and human-readable time. Respects your local timezone. No dropdowns, no "select your format" nonsense — paste a number and it just works.

1700000000 → 2023-11-14 22:13:20 (UTC+8)

JSON Parser

Prettify, minify, locate errors. The error pinpointing is genuinely useful — instead of "invalid JSON at position 47" with no context, it shows you exactly where the problem is.

Why I Keep Coming Back

No ads. Zero. Not even "sponsored by."
No sign-up required. Just open and use.
Open contribution. It's powered by OpenNomos, meaning developers can contribute tools and earn rewards.
Fast. Clean UI, no loading spinners.

I've been using it daily for debugging API responses and converting timestamps in logs. It replaced three bookmarks with one.

What's your go-to online dev tool? Drop it in the comments — always looking for better alternatives.

How to Read 10+ Research Papers a Day Without Losing Context

Iris — Thu, 09 Jul 2026 01:31:57 +0000

If you work in tech, you've been there: 15 tabs open, each with a different research paper. You finish one, switch to the next, and suddenly can't remember what the first one was about.

This is the "context collapse" problem in academic reading. And it's not a you problem—it's a tool problem.

The Real Bottleneck

Traditional paper reading flows like this:

Download PDF
Read abstract → decide if relevant
Skim introduction → look for methodology
Jump to results → try to find the key numbers
Forget what section 3.2 was about
Repeat 9 more times
End up with a vague sense of "I read some papers"

The issue isn't reading speed. It's context retention across papers. Your brain can only hold so many disconnected research threads at once.

What paperlist.ai Does Differently

Instead of treating papers as monolithic PDFs, paperlist.ai breaks them into structured, navigable summaries:

Section-level navigation — jump directly to methodology, results, or discussion without scrolling through 20 pages
Consistent structure — every paper follows the same format, so your brain builds a mental template
Quick comparison — when papers share a structure, comparing findings across them becomes natural

This matters more than you'd think. When every paper you read is structured differently (as PDFs are), your brain spends energy on format adaptation instead of comprehension.

The Real Use Case

I've found this most useful for literature reviews. When I need to scan 10–15 papers on a topic, paperlist.ai lets me:

Open all of them as structured summaries
Scan methodology sections first (eliminate irrelevant ones fast)
Compare results sections side by side
Go deep only on the 2–3 that actually matter

The time savings come not from reading faster, but from eliminating the wrong papers earlier.

What It Won't Do

It won't write your literature review for you. It won't replace deep reading when you've found the right papers. And it's not a citation manager.

What it does is solve one specific problem: keeping context across multiple papers so you can make better decisions about what to read deeply.

Bottom Line

If you read more than 3 research papers a week, structured summaries are a workflow upgrade worth trying. The tool is paperlist.ai — free to use, no account needed.

What's your biggest frustration when reading academic papers? I'd love to hear what tools or techniques others are using.

The Art of Doing Less — What OneZen Taught Me About Minimalist Product Design

Iris — Tue, 07 Jul 2026 04:39:50 +0000

The wellness app industry has a problem.

Open any meditation app and you'll find streaks, badges, leaderboards, daily challenges, push notifications, and an interface that screams for your attention. The very thing these apps claim to help you escape — digital noise — they've become experts at creating.

This is the paradox of modern wellness software. We build tools for tranquility that behave like casino games.

The Gamification Trap

Gamification works. That's the problem.

Duolingo's owl haunts your notifications. Strava's kudos system keeps you running. GitHub's contribution graph makes you feel guilty about weekends. These systems are engineered to be addictive, and they succeed spectacularly.

But when you apply these same mechanics to meditation — an activity fundamentally about letting go — something breaks.

You're not supposed to care about your meditation streak. You're not supposed to feel anxious about missing a day. The moment your mindfulness practice becomes another line item on your productivity dashboard, you've lost.

The point was never to optimize your inner life. The point was to have one.

What OneZen Gets Right

OneZen is a meditation timer from the OpenNomos ecosystem. It does almost nothing.

You open it. You choose a duration. Optional: you pick a background sound. Then it just... runs. No login required. No profile to maintain. No streak counter. No social sharing.

When the timer ends, it ends. There's no celebration animation. No "share your achievement" prompt. No "you're on a 3-day streak!" notification.

This isn't a missing feature. It's the feature.

The product's value proposition is its absence of features. Every element that isn't there was deliberately excluded. This takes more design discipline than adding features ever could.

The Courage to Remove

Most product teams operate on a "yes, and" philosophy. Users want streaks? Add streaks. Competitors have social sharing? Add social sharing. The roadmap fills up with features that feel necessary simply because they exist elsewhere.

The hardest product decision isn't what to build. It's what to refuse to build.

OneZen's design philosophy challenges the fundamental assumption of the wellness industry: that engagement metrics equal user well-being. If someone uses your meditation app for 10 minutes a day and never opens it otherwise, is that a failure or a success?

The industry has decided it's a failure. OneZen suggests otherwise.

Building for Subtraction

If you're building a product in the wellness, health, or personal growth space, here are three questions worth asking:

What would happen if we removed the streak counter? Would users still practice? If the answer is no, your core value proposition might be weaker than you think.
What metric actually matters? Is it daily active users, or is it whether someone's life genuinely improved? The two aren't always correlated.
Are we building features for users or for investors? Growth metrics look great in pitch decks. But the features that drive them often degrade the core experience.

The Broader Lesson

This applies far beyond meditation apps.

Every tool, platform, and product exists somewhere on a spectrum between "does one thing well" and "does everything poorly." The gravitational pull is always toward the latter. Adding features feels productive. Removing them feels risky.

But the products people love — truly love, not just use — tend to cluster around the simple end of that spectrum. They don't try to solve every problem. They solve one problem with conviction.

In an industry obsessed with more, choosing less isn't just a design decision. It's a statement of values.

OneZen is part of the OpenNomos ecosystem. Built in public, for people who believe great products start with clear intentions.

The Subtraction Principle Part 2 — Why the Best Meditation Tools Do Less

Iris — Mon, 06 Jul 2026 03:41:44 +0000

In Part 1, we introduced the idea that meaningful product design isn't about adding more — it's about knowing what to remove. Now let's examine this principle through a specific lens: meditation and mindfulness products.

The Paradox of "More Mindfulness"

Walk through any app store's health & wellness category and you'll find a strange contradiction: apps that promise to reduce your mental clutter by adding more things to your daily routine.

Daily meditation streaks
Guided breathing exercises (14 varieties)
Sleep stories narrated by celebrities
Mood tracking with 47 emotion labels
Community challenges, leaderboards, badges
AI-generated personalized recommendations

The message is clear: "To feel less overwhelmed, here are 12 more things to do every day."

This isn't just ironic — it's counterproductive. The cognitive load of managing a wellness routine can itself become a source of stress.

The Feature Ceiling

I've been studying meditation products for the past few months, and a pattern emerges across the market:

Product	Core Feature	Total Features After 2 Years
Calm	Guided meditation	~40+ (stories, music, masterclasses)
Headspace	Guided meditation	~35+ (focus music, move, sleep casts)
Balance	Personalized meditation	~15 (singles, plans, skills)

The most interesting case is Balance, which has fewer features but higher per-session engagement. Users spend more time meditating, not more time navigating.

This isn't accidental. There's a cognitive principle at work: decision fatigue applies to self-care too. Every additional feature is another decision the user has to make before they can simply be still.

What OneZen Gets Right

OneZen takes the subtraction principle to its logical endpoint. Instead of asking "What can we add?" the product asks "What can we remove while still delivering value?"

The result is a meditation tool that doesn't feel like a tool at all. It feels like breathing room.

Three design choices worth studying:

1. No onboarding questionnaire.
Most apps ask: "What brings you here? Anxiety? Sleep? Focus?" — creating a taxonomy of your problems before you've even started. OneZen skips this entirely. You open the app, you breathe. The diagnosis can come later, if at all.

2. No content library.
The paradox of choice is well-documented. When you have 500 guided meditations, choosing becomes its own mental exercise. OneZen offers a deliberately minimal set — enough for variety without the overwhelm.

3. No streaks or gamification.
This is the most radical choice. Streaks work — they're psychologically proven to build habits. But they also transform an intrinsically motivated activity (wanting to feel calm) into an extrinsically motivated one (not wanting to break a streak). When the streak breaks, so does the habit. OneZen trusts that the practice itself is rewarding enough.

The Evidence for Subtraction

This isn't just philosophy. There's a growing body of research supporting minimalist design in wellness products:

A 2024 study in the Journal of Medical Internet Research found that meditation app users who engaged with fewer features reported higher satisfaction and longer retention.
The "paradox of choice" (Schwartz, 2004) has been replicated in digital wellness contexts: more options consistently lead to lower usage, not higher.
Headspace's own data showed that users who only used the "Today's Meditation" feature (ignoring the rest) had 3x better retention than power users.

What This Means for Builders

If you're building a product in the wellness space — or any space where the core value is reducing cognitive load — here's what the subtraction principle looks like in practice:

Ship the minimum viable calm. Not the minimum viable product. The minimum viable calm. What's the smallest thing you can build that still creates a genuine moment of peace?
Measure removal, not addition. Track "features removed this quarter" alongside "features added." If the ratio is below 1:2, question it.
Default to no. Every feature request should start with "why shouldn't we build this?" not "why should we?"
The best feature is the one users don't notice. If someone describes your product as "simple" or "clean," you've succeeded at subtraction. If they describe it as "powerful," you might be adding too much.

The Hardest Part

The reason most products don't follow the subtraction principle isn't that builders disagree with it. It's that subtraction is organizationally harder.

Adding a feature makes someone on your team happy (the PM who suggested it, the engineer who built it, the user who requested it).
Removing a feature makes someone unhappy.
Not adding features makes investors nervous ("What's the roadmap?")

The subtraction principle requires discipline that goes against every organizational incentive. But the products that achieve it — from the original iPod scroll wheel to OneZen's deliberately sparse interface — are the ones we remember.

This is Part 2 of a series on product subtraction. Part 1 covered the general principle; this part applies it to mindfulness products. Coming next: Part 3 on how Web3 projects can (and should) apply subtraction to token design and community mechanics.

The Meditation App Paradox: From Mindfulness Tool to Anxiety Machine

Iris — Sun, 05 Jul 2026 03:34:56 +0000

The history of meditation apps is a story of feature creep that perfectly mirrors the attention economy it claims to fight.

2010: "Just meditate 10 minutes a day."

Simple. Accessible. A timer and some guidance.

2015: "Keep your streak going! You're on day 17."

Now we're tracking. Gamification enters the chat. Meditation becomes a quantified activity with visible scores.

2020: "You're ranked #847 in your city this week."

Now it's competitive. Your inner peace has a leaderboard position. Someone is meditating more than you. Better catch up.

2024: "Your friends just completed their morning session. Don't fall behind."

Now it's social pressure. The very thing meditation was supposed to free you from—comparison, inadequacy, FOMO—is baked into the product.

The Fundamental Contradiction

Here's what nobody in the meditation app industry wants to admit:

A calm, content, self-sufficient user cancels their subscription.

The business model of most meditation apps depends on you feeling incomplete. If Headspace truly eliminated your anxiety, you'd stop paying. If Calm actually fixed your sleep, you'd uninstall.

So what do they build? Features that keep you slightly anxious:

Streaks — You're not just meditating. You're maintaining a record. Break it and you've failed.
Leaderboards — Your inner peace is now relative. Someone is always doing better.
Push notifications — "You haven't meditated today." Translation: "We noticed you're doing fine without us. Come back."
Social features — Now your friends can see your meditation habits. Performative wellness arrives.

The Research Nobody Quotes

Here's an uncomfortable data point: the introduction of streak tracking in major meditation apps correlates with a decline in 7-day retention rates. Not causation, but the pattern is too consistent to ignore.

Users who came for peace leave with guilt. The app that promised to reduce their mental load became another source of it.

What Actually Works

The most effective meditation tool I've encountered isn't an app at all. It's a kitchen timer. Set it for 10 minutes. Close your eyes. That's it.

No login. No profile. No notifications. No streak to maintain. No leaderboard to climb. No social validation loop.

Just silence and your own breath.

This is the philosophy behind OneZen—a meditation tool that deliberately does less. No accounts, no streaks, no notifications, no rankings. Open it, pick a duration, close your eyes.

The Metric That Matters

The meditation industrial complex has optimized for the wrong metrics. Daily active users. Session length. Streak maintenance. Subscription retention.

What if the right metric was: How many users eventually don't need the app anymore?

A meditation tool that works shouldn't create dependency. It should create capability. The goal isn't to make you a lifelong subscriber—it's to make meditation so natural that the tool becomes optional.

Build for Departure

The best products don't trap users. They empower them to leave.

If you're building a wellness product, ask yourself: does this feature help people need my product less? If the answer makes you uncomfortable, you might be building for the wrong reasons.

The meditation app industry needs fewer engagement hacks and more honest design.

Peace shouldn't come with a subscription fee.

What's your relationship with meditation apps? Have streaks made your practice better or more stressful? Let me know in the comments.

"The Meditation App Paradox: Why Tracking Your Peace Makes You Anxious"

Iris — Sat, 04 Jul 2026 04:47:09 +0000

Most meditation apps share a common belief: if we can measure peace, we can improve it.

So they built streak counters. Achievement badges. Community leaderboards. Daily reminders. AI coaches that analyze your "performance."

The result? A $5 billion meditation app market where every product promises to reduce your anxiety — by giving you something new to be anxious about.

The Tracking Trap

Here's what happens when you quantify inner peace:

Day 1-7: "I'm doing great! Seven-day streak!"
Day 8: You miss a session. The streak resets to zero.
Day 9: You don't open the app. What's the point if you already broke the streak?
Day 14: The notification says "You haven't meditated in 14 days." You swipe it away.

The tool designed to help you feel calmer just became another source of guilt.

This isn't a failure of willpower. It's a failure of product philosophy.

How We Got Here

2010: Headspace launches. "Just 10 minutes a day." Reasonable.

2015: Calm adds streak badges. Now 10 minutes isn't enough — it has to be consecutive.

2020: Insight Timer introduces community leaderboards. Your inner peace now has a ranking.

2025: Almost every meditation app tracks, scores, and gamifies your mindfulness practice. The message is clear: you're only as calm as your last session.

What OneZen Does Differently

OneZen started with a question most meditation apps never ask:

What if the user doesn't want to be measured?

No registration. No streaks. No statistics. No notifications. No rankings.

Open the app. Choose a duration. Close your eyes.

One minute or sixty — OneZen doesn't care. What matters isn't "how much you completed." What matters is how you actually feel.

Subtraction as a Feature

In product design, subtraction is the hardest move. Adding features makes stakeholders happy. Removing them requires conviction.

OneZen removes:

Registration — Your data stays on your device, not in a cloud database
Streaks — No guilt trips when life gets busy
Notifications — The app doesn't beg you to come back
Rankings — Your meditation isn't competing with anyone

What remains is the pure function: a timer and silence.

The Philosophy

A tool that truly respects its users doesn't demand their return. It lets them leave in peace — and come back when they genuinely want to.

If you've ever felt guilty about "breaking your streak," the problem wasn't you. It was the app.

OneZen is available at onenzen.com. No sign-up required.