A Wellness App Without Streaks: The Rules We Wrote Before Building in.between

in.between is a wellness app without streaks, and that was the first rule we wrote, before a single screen existed. It also has no guilt-trip notifications, no endless feed and no public leaderboard. The reason is simple: in.between is ETAPX's AI sleep and reflection journal, it lives in the last few minutes of your day, and almost every standard engagement trick works directly against rest. So we judged the product on a different question: do you close the app feeling a little better than when you opened it? This piece explains the rules that came out of that question, the tradeoffs they cost us, how we measure success without leaning on time-in-app, and a checklist you can use to judge whether any wellness app is actually on your side.

We're writing this partly to explain ourselves and partly to hold ourselves to it in public. A value that only lives in a slide deck doesn't survive a deadline. Writing it down where you can read it makes it harder to quietly drop.

Why we built a wellness app without streaks

Most consumer apps start from some version of "how do we get people to come back more often?" It's a reasonable question for a lot of products. For a journal that sits beside someone at 11 p.m., tired, sometimes anxious, often alone with their thoughts, we decided it was the wrong one.

Our starting question was different: what does this person actually need from the last twenty minutes of their day, and how do we stay out of the way of it? That sounds like a small shift in wording. In practice it changed almost every decision we made, including what got built, what got left out, and what got refused even when it would have been easy to ship and would almost certainly have lifted our usage numbers.

Late at night is exactly when engagement-optimized design does its most effective work, and its most damaging. A tired mind is easier to pull back into a loop. We saw that leverage as a responsibility, not an opportunity. If we could have made in.between maximally sticky and chose not to, that restraint is the decision worth explaining.

The honest tradeoff: streaks work

It would be convenient to claim that streaks and nudges don't work, so dropping them cost us nothing. That's not true, and we'd rather be straight about it. Streak counters do bring people back. Notifications with a little guilt baked in do lift open rates. Infinite feeds do stretch sessions. These mechanics are everywhere precisely because they move the numbers.

The problem is what they move the numbers with. A streak turns a missed night into a small failure. Picture someone who's been journaling for nineteen nights, then gets the flu. On night twenty they're not resting, they're worrying about losing the count. A sleep app that makes people feel bad about using it imperfectly defeats its own purpose.

So we made a bet. Our bet is that trust and genuine usefulness compound into something more durable than manufactured urgency. A person who opens in.between because they want to, on a night they need it, is worth more to them and eventually to the product than ten people who opened it because a red dot told them to.

Five things in.between refuses to do

Values are easiest to see in what a product won't do. Every item below was technically possible and would likely have increased time in the app. We left each one out on purpose.

1. Punishing streaks. Missed nights don't reset anything or cost you anything. Travel, illness, a hard week or simply not feeling like it are all normal parts of life.
2. Guilt-trip notifications. Nalani may check in, but there are no "we miss you" messages, no manufactured urgency and no red badges counting the days since your last entry.
3. Infinite scroll. There's no endless feed designed to keep your thumb moving. A session has a beginning and an end, and the app is built to actually end.
4. Engagement-bait prompts. Nalani's questions are written to open something honest, not to maximize how long you type. A short, true answer counts as a complete session.
5. A public performance layer. No leaderboards, no badges to show off, no comparing your rest with anyone else's. Reflection performed for an audience stops being reflection.

How we judge whether a wellness app without streaks is working

If you stop optimizing for time in the app, you need something else to steer by. This turned out to be the hardest problem we faced, harder than any interface question. Feelings don't show up neatly on a dashboard the way session counts do.

Our answer was to anchor success to a simpler, more honest signal: did this person feel better, calmer or more settled after using in.between than before? That reframes a lot. A two-minute session that helps someone fall asleep is a success. A forty-minute session that leaves someone more wound up is not, however good it looks in a usage chart.

Because no single number captures that, we look at several imperfect signals together rather than trusting any one of them:

• What people choose to share when they aren't being prompted to.
• Whether sessions taper naturally toward sleep instead of trailing off into something else.
• Whether people come back because they want to, not because a mechanic pushed them.
• What people tell us when we simply ask how using it made them feel.

It's slower and messier than reading a usage dashboard, and it makes our own product reviews harder to run. We think that's an acceptable price for measuring the right thing instead of the easy thing.

What's hard, and what we actually care about, is building the version people use less but trust more, because it left them better off. If someone opens in.between for two minutes and falls asleep peacefully, that's not a failed session. That's the whole point.

— The in.between team

Nalani: an AI companion that lets you leave

Nalani, ETAPX's first purpose-built AI companion model, is who you actually talk to inside in.between. It asks how your day went, notices patterns in what you share over time, and offers a starting question when a blank page feels like too much. Its design brief carried the same values as the rest of the product: be present without being needy, attentive without being intrusive, and never make anyone feel managed.

That ruled out a set of patterns common in AI companions. No scripted attempts to stretch a conversation past its natural end. No persona built to seem lonely so you feel bad about leaving. There was real debate on our team about how warm and chatty Nalani should be, because the tempting version of an AI companion is one engineered to feel irreplaceable. We built away from that. If you go a week without talking to Nalani, nothing about coming back should make you feel you owe it an explanation.

A companion meant to help you rest has to be willing to disappear once the rest starts.

What using a wellness app without streaks actually feels like

Rules on a page are abstract, so here's how they play out across an ordinary month. Imagine a teacher who opens in.between most weeknights during term. Some nights she talks with Nalani for ten minutes about a difficult class. Some nights she types two sentences and puts the phone down. Both count as complete sessions, and nothing in the app treats the short ones as underperforming.

Then a school trip takes her away for a week and she doesn't open the app once. In a streak-driven product, that week would be waiting for her when she got back: a broken counter, a reset badge, maybe a string of notifications asking where she went. In in.between there's nothing to repair. She opens it the following Monday and Nalani simply picks up the conversation, with the context of what she's shared before still there to draw on. No catch-up, no explanation owed.

That's the experience we're designing for: a habit that bends around your life instead of the other way round. Some people use in.between nearly every night. Others use it a few times a week, or only when a day has been heavy. We don't consider any of those patterns better than the others, as long as the time spent leaves people a little more settled.

Rest as a design constraint, not a feature

Saying you prioritize rest can sound like marketing until you see what it constrains. In in.between, it shapes four concrete areas:

These constraints don't stay settled on their own. A new idea gets pitched, someone points out it would lift engagement, and the team has to decide again whether that's actually a reason to build it. Our habit is to keep the original question visibly attached to those conversations, so a growth question doesn't quietly replace it while borrowing the same vocabulary. It's a small piece of process, and it's the piece that stops a value from eroding one reasonable-sounding exception at a time.

We'll also be candid that this is an ongoing balancing act. ETAPX is a company that needs to grow and sustain itself, and the pressure to drive usage is real here like everywhere. What we try to change is where the argument starts: does this help the person, before does this help the number, and the person-first answer is allowed to actually win.

Why this starts inside ETAPX

Protecting people's rest isn't something we invented for in.between's launch page. It's a value we've talked about internally for a while, and it's supposed to describe how we treat the people who build our products too. A team expected to run itself ragged doesn't tend to ship something that genuinely protects anyone else's rest. The values leak through one way or another.

In that sense in.between is a test of whether that internal value is real. If we can hold a mental-health-first line on a real roadmap, under real deadlines, it's evidence the value means something. If we can't, you'll be able to tell.

How to tell if a wellness app respects your rest

You don't have to take our word for any of this, and these questions are worth asking of any sleep, meditation or journaling app on your phone, ours included:

• Does missing a day cost you anything, like a lost streak, a reset counter or a sad notification?
• Do its notifications create a small jolt of guilt or urgency when you read them?
• Is there a feed or loop inside it that's hard to stop scrolling?
• Does it reward longer sessions or celebrate time spent, rather than how you feel?
• Is there a public or social comparison layer around something that should be private?
• After using it, do you usually feel calmer, or slightly more wound up?

If an app answers yes to most of the first five and leaves you wound up on the sixth, it may be optimized for your attention rather than your rest. That doesn't make it useless, but it's worth knowing which job it was built to do.

What in.between is not

Being honest about what in.between is for means being just as honest about what it isn't. It's a space for daily reflection, for noticing patterns in your sleep and mood over time, and for a gentle wind-down at the end of the day. It is not a mental health treatment and not a crisis service.

That boundary isn't a disclaimer we added at the end. It comes from the same value as everything else on this page. Caring about someone's mental health means being clear about the limits of what a reflection journal can do for them, especially in the moments that matter most.

Frequently asked questions

Why doesn't in.between use streaks?

Streaks work by making a missed day feel like a loss, which creates anxiety about usage. For an app meant to help you rest, that's counterproductive. Life regularly interrupts nightly habits through travel, illness or hard weeks, so in.between is designed so a missed night never comes with a penalty, reset or guilt-inducing reminder attached.

Does in.between send reminder notifications?

Nalani may check in, but in.between doesn't send notifications engineered to make you feel guilty about not opening it. There are no "we miss you" messages, no manufactured urgency and no badges counting days since your last entry. Check-ins are designed to respect the hour rather than interrupt you once you've settled down.

How does ETAPX measure whether in.between is working?

Instead of treating time in the app as the main measure, the team looks at whether people feel better, calmer or more settled after a session. That's judged from several signals together, including whether sessions taper toward sleep and what people say when asked how it made them feel. A short session that helps someone sleep counts as success.

Is Nalani a real person or a therapist?

Neither. Nalani is ETAPX's first purpose-built AI companion model, the presence inside in.between that offers prompts, listens and helps surface patterns over time. It is not a person and not a licensed therapist. It isn't built to diagnose, treat or manage mental health conditions, and it's designed to point toward professional support when that's needed.

What should I do if I need more support than in.between can offer?

Reach out to a licensed mental health professional, your doctor or a crisis resource in your area rather than relying on an app. in.between is built for everyday reflection and rest, not crisis support. The team is explicit that professional help is the right path whenever someone is struggling in a serious way.