The in.between App Launch, and Why We Waited to Say Its Name

The in.between app launch is the answer to a question we left open on purpose. In late August we told you ETAPX was building a new AI app and declined to give you its name, its date or a finished feature list. That app is in.between, an AI-powered sleep and reflection journal built around a companion called Nalani, and it is here now. This piece isn't the feature tour. It's the story of the weeks between the teaser and today: why we held the name back when we already had it, what we changed while nobody outside the company was watching, and what that history should tell you about the product you're about to open.

If you've followed ETAPX for a while, you've seen us do some version of this before. We describe a direction, we go quiet, and then something real shows up with a name attached. People find that pattern either reassuring or maddening, sometimes both in the same Discord thread. We'd like to explain it properly, using in.between as the clearest example we've had yet.

What the in.between app launch actually is

Plainly: in.between is a nightly journal you talk or type to before bed. Nalani, the AI companion inside it, guides the conversation, remembers what you've shared over time and occasionally reflects a pattern back to you, like a theme that keeps resurfacing or a particular shape your weeks tend to take. It does that without diagnosing you or telling you what any of it means in a clinical sense.

It's a standalone product with its own team and its own place in the ETAPX lineup. It is not a Whistlr feature, and it doesn't live inside any of our other apps. It's also not therapy, and we'll keep saying that in every piece we write about it. If something in your life needs professional care, a licensed provider is where that care belongs. in.between is a journal with memory, built for winding down and noticing yourself.

That's a deliberately short description. The full walkthrough of what's inside the app lives in our getting-started guide. Here we want to talk about how the product got from "the new app" to a name you can actually search for.

Why didn't ETAPX name the app in August?

Here's the part that surprises people: the name already existed. "in.between" was a working title well before the teaser went out, and Nalani existed in an early form too. So the silence wasn't about not knowing. It was about not being ready to put our name behind what we knew.

A name is a promise. The moment we say "in.between is an AI sleep journal," you start picturing it, and you start wanting specific things from it before it has earned that. If we'd said it in August and then spent the following weeks discovering that parts of it didn't work the way we hoped, we'd have been publicly walking things back instead of privately fixing them. That did happen with pieces of the product, which is exactly why we're glad we kept quiet.

There's a second, less obvious reason that came from the engineering side of the company. Once a name is public, changing direction on the thing behind it carries a psychological cost. People inside a team start defending decisions instead of questioning them, because reversing course now feels like backing down in front of everyone. We wanted the team to keep the freedom to throw things out during the exact weeks when they were throwing out the most. Holding the name back bought that freedom for a little longer.

And there's the simplest reason of all. If we tell you a name, we owe you the product reasonably soon after. We weren't willing to hand you "in.between" and then disappear for a month while we figured out whether it held up. Not naming it felt more honest than naming it and leaving you waiting.

What changed between the teaser and the in.between app launch

The core idea didn't change. By every account inside the company, the concept of a nightly journal guided by a companion had been stable for a while before August. What filled the weeks afterward was something less dramatic and more useful: the ETAPX team kept using its own working version of the app, every night, and kept adjusting it based on what people actually reached for.

There's a moment with a product like this when it flips from "I'm testing this because I'm supposed to" to "I'd be annoyed if this disappeared tonight." That flip didn't happen in August. It happened gradually over the following weeks, one night at a time, across a growing number of people in the building. By the time we were ready to talk about it publicly, in.between wasn't a hypothesis anymore. It was simply how a lot of us were ending our days.

That became the bar for saying the name. Not "is it technically finished," because nothing ever really is. The bar was whether the people who built it would be upset if it went away. Once that was true for enough of us, keeping the name to ourselves stopped making sense.

The approach we threw away

One concrete example of what those weeks were for: an entire earlier approach to how Nalani surfaced patterns didn't survive real nightly use. It looked reasonable on paper. In practice, it didn't hold up across weeks of people journaling at the end of real days, so it went. If the name had been public at that point, cutting it would have felt like a public retreat. Because it wasn't, it was just Tuesday.

How did internal use shape Nalani before launch?

The biggest single shift was in Nalani's temperament. Early versions were more eager than they needed to be. Nalani wanted to say something insightful every time you journaled, and most nights, nobody needs that. If you've had an ordinary day and you want five quiet minutes before sleep, a companion that insists on finding meaning in it gets tiring fast.

So a lot of the work between the teaser and today went into making Nalani comfortable saying less. It now reflects a pattern back only when there actually is one, and otherwise it stays present while you talk. That's harder to build than a new feature, because you can't add restraint the way you add a button. You have to teach the product when not to speak, then check, night after night, that it's still getting that judgment right.

Nalani also had to learn to tell the difference between two very different kinds of user on any given night: someone who wants to talk through their whole day, and someone who just wants a few quiet minutes before sleep. Getting that distinction right shaped the version you can open today more than any single feature did.

We stopped asking whether Nalani had said something clever and started asking whether it had needed to say anything at all. That one question rewrote more of the product than any feature we added.

— The in.between team

What stayed true from the teaser to today

Put the August announcement next to the launch and the most notable thing isn't how much moved. It's how much held. The direction we described before we could name anything turned out to be accurate almost line for line.

• It's personal, not industry-facing. The teaser said the new app would sit closer to your actual day than to any dashboard or professional workflow. A nightly journal guided by an AI companion is about as personal as software gets.
• It's separate from Whistlr. We said it wasn't a Whistlr feature in disguise, and it isn't. in.between is its own product with its own team.
• It came out of the same culture as everything else. The team built it with the same review and iteration habits we use across the company, the ones that also shaped GLSRM and Influxx.
• Your fingerprints are on it. The patterns in what people kept asking for across Discord and PX News comments shaped real decisions in those weeks, including some of the restraint built into how Nalani responds.
• The team kept discarding things. We said in August that a team which never throws anything out early on probably isn't being honest with itself. That kept happening right up to launch.

We point this out not to congratulate ourselves on a prediction. We point it out because it's the strongest argument we have for the way we communicate. When we tell you a direction before we're ready to name a product, we're trying to only tell you things that will still be true later. This time, they were.

Why we refused to say "soon"

If you reread the teaser, you'll notice a word that never appears in it. We didn't say "soon" once, and that was deliberate.

'Soon' is a word that creates a countdown whether you mean it to or not. The second I'd said it, every conversation after that article would have been about when, instead of about what we were actually building or why.

— AJ, ETAPX CEO

That discipline went past the public announcement and into how the company talked about the project internally. We didn't put a launch date on a slide until we were genuinely close. A date on a slide has a way of quietly becoming the goal, and once it does, teams start optimizing for hitting the date rather than getting the thing right. We've seen that happen elsewhere, and if we're honest, we've seen earlier versions of our own team do it. Leaving the date off kept that pressure away from in.between for longer than it usually stays away.

For you, this has a practical upside. The version of in.between you're opening wasn't squeezed to meet a date somebody announced months ago. It shipped when the people closest to it believed it was ready to sit in someone's evening.

The cost of staying quiet, and what we heard from you

We won't pretend the silence was free. The ETAPX community has, in AJ's own August description, zero patience for waiting, and every version of "just tell us already" landed in our Discord. We read them. We don't think that impatience was wrong. People don't get impatient about things they don't care about, so honestly it was one of the better signals we had.

It was also tiring from the inside. Every interview, every Discord AMA and every comment thread under the teaser came with the real answer sitting right there, unsaid. Making the right call once is easy. Making it again every day for weeks wears on you. Saying "in.between" out loud to people who'd been asking for months felt less like an announcement and more like finally exhaling.

Some of you spent those weeks building theories. Longtime readers had noticed that GLSRM and Influxx both started as vague directions before becoming named products, and plenty of you guessed at what this one would be. Most guesses missed the specifics. A surprising number got the feeling right: something personal, not another dashboard. That instinct held up.

Inside the company, there was a quieter shift too. For a long time, in.between only existed for people in our building. We'd mention a good night of journaling with Nalani the way you'd mention a good workout, casually, because it had become ordinary for us. Watching people outside the company have that same kind of night, and describe it in the same casual way, is a strange and genuinely moving thing to see. The product stopped being ours in the private sense and started being ours in the shared one.

What the in.between app launch means if you're deciding whether to try it

If you're reading this and wondering whether the backstory matters to you as a potential user, here's the short version of why we think it does. The way a product is announced tends to reflect the way it was built. A product announced early, with a date and a list of promises, often ships under pressure to match the announcement. One that stays quiet until its team trusts it ships under a different kind of pressure: the team's own nightly use.

What we'd suggest is simple. Open it on a night when you have five minutes, say whatever is actually on your mind, and see how it feels to close the app afterward. Don't judge it on the first night alone. A journal with memory gets more useful as it has more to remember, and Nalani was tuned specifically to avoid making a big impression on night one.

A sleep journal has to be right before it exists in someone's life, not after.

— AJ, ETAPX CEO

Will ETAPX tease future products the same way?

We've now followed roughly the same arc three times, with GLSRM, Influxx and in.between: say there's a direction, stay quiet on specifics, name the product when it's ready. Each time it has worked out better than the alternative would have, and we trust the approach a little more every time it holds.

We're not going to promise it as a fixed rule, though. Making that promise would contradict the very instinct behind it, which is not committing publicly to things we aren't sure of yet. What we can tell you is the reasoning we'll keep applying: we'd rather tell you less and have every word hold up than tell you more and quietly correct it later. That applies to how we talk about in.between's future too. We'd rather under-promise on what comes next for the app and over-deliver when it arrives.

So the August teaser ended with the details still ahead. They aren't ahead anymore. The sentence we left unfinished has its second half, and the second half is a journal you can open tonight.

Frequently asked questions

Is in.between the app ETAPX teased in August?

Yes. In late August ETAPX announced it was building a new AI-powered app without sharing a name, a date or a feature list. That app is in.between, an AI-powered sleep and reflection journal guided by an AI companion named Nalani. The name existed internally before the teaser ran, but the company held it back until the team trusted the product enough to put its name behind it.

Why did ETAPX keep the in.between name secret before launch?

A public name works like a promise and makes changing course harder. ETAPX wanted the team free to rework or discard parts of the product during weeks of internal testing without publicly walking anything back. Leadership also didn't want to announce a name and then leave people waiting while it confirmed the product actually held up in real nightly use.

What changed in in.between between the teaser and the launch?

The core concept stayed the same. What changed came from the ETAPX team using the app every night. Nalani became noticeably more restrained, reflecting patterns only when one genuinely exists instead of trying to say something insightful every session. An entire earlier approach to how Nalani surfaced patterns was dropped after it didn't hold up in real nightly use.

Is in.between part of Whistlr?

No. in.between is a standalone ETAPX product with its own team and its own place in the company's lineup. It isn't a Whistlr feature and doesn't live inside any other ETAPX app. It was built with the same review and iteration habits the company uses across its products, but it's designed around one person's evening rather than a network of people.

Is in.between a replacement for therapy?

No. in.between and Nalani are a nightly journaling and reflection tool, not a licensed therapist, a medical device or a substitute for professional mental health care. Nalani doesn't diagnose or treat anything. If something in your life calls for professional support, a licensed provider is the right place to bring it, and in.between is built to sit alongside that care, not replace it.