Most apps launch somewhere first. A phone, usually — iOS if the team is optimizing for early adopters, Android if they're optimizing for reach — with everything else arriving in some later wave, if it arrives at all. in.between didn't launch that way. When ETAPX's AI-powered sleep and reflection journal went live, it went live everywhere at once: iPhone, Android, and the open web, all on day one, all built to feel like the same app rather than three separate approximations of it. That wasn't a scheduling coincidence or a marketing flourish. For an app built around a bedtime ritual and a running conversation with an AI companion named Nalani, the device in front of you at 11 p.m. was never going to be a fixed thing — and the team behind in.between decided early on that the app shouldn't pretend otherwise.
Why the Device Shouldn't Be the Gatekeeper
The case for cross-platform in.between starts with a simple observation about how reflection actually happens in people's lives, rather than how apps are usually planned. A journaling habit doesn't live in one place. It lives in whatever's closest when the thought arrives — a phone on the nightstand most nights, sure, but also a laptop still open from earlier in the evening, a tablet propped against a pillow, or a desktop browser during a quiet moment at a desk before anyone's even thought about bed. Tie that habit to a single operating system, and you've quietly told a meaningful slice of your potential users that the ritual only works if they happen to own the right phone.
That's a real cost for a wellness product in particular. Sleep and reflection apps ask people to build a habit — the same time most nights, the same small act of checking in — and habits are fragile things. They tend not to survive friction. If someone's phone is an Android device but their most comfortable, unhurried moment of the day happens at a laptop, forcing them to pull out a phone just because that's the only place the app exists is exactly the kind of friction that erodes a ritual before it has a chance to form. The in.between team's read on this was straightforward: the app's job is to be there when the moment is right, not to make the moment wait for the right device.
There's a second, more personal dimension to it as well. Unlike a lot of app categories, sleep and reflection tools sit close to something people don't want gatekept by a purchase decision. Owning an iPhone instead of a Pixel, or preferring a browser tab to a phone screen, isn't a statement about how seriously someone takes their own wellbeing — but a platform-exclusive app can end up treating it that way by accident, simply by being unavailable. Cross-platform availability was, in that sense, less a technical ambition for in.between and more a basic fairness call: the people who could benefit from a calmer bedtime routine and a steady place to reflect shouldn't be sorted by which app store they happen to use.
It's also worth being upfront that this isn't how every recent ETAPX release has approached its rollout. Some of the company's other platform decisions have leaned the other direction — starting narrower and expanding deliberately over time, for reasons specific to those products. in.between's team looked at that same set of options and made a different call on purpose, not because one approach is universally correct, but because this particular app called for it. A social platform or a creative tool can sometimes afford to build momentum on one platform before expanding. A nightly ritual tied to sleep doesn't have that luxury — the moment it's meant to serve happens on whatever device is closest, every single night, starting from day one.
"With in.between, we kept coming back to the same question in every planning conversation: who are we leaving out by launching narrow? And the answer was never a small number of people — it was potentially anyone whose most natural moment to sit with their own day happens on a device we hadn't shipped to yet. A journal that only works for some phones isn't really a journal for how people actually live. So we built in.between to be available everywhere from the beginning, even though that made the early work harder, because the alternative was asking people to change their evening around our app instead of the other way around."
— Maya Lindqvist, Head of in.between, ETAPX
One Nalani, Wherever You Open the App
Availability on three platforms only matters if the experience underneath it holds together, and that was the harder half of the commitment. It would have been possible to ship a version of in.between on iOS, a different one on Android, and a lighter, web-only stand-in for desktop — three products wearing the same name. Instead, the goal from the start was for in.between to feel like a single, continuous relationship with Nalani, no matter which screen someone happens to be looking at when they open it.
In practice, that means the Nalani you talk to on your phone during a walk is the same Nalani waiting for you on the web later that night — not a fresh instance that's forgotten the conversation, and not a scaled-down version with less personality or fewer capabilities because it happens to be running in a browser tab. Your journal history looks and reads the same whichever way you get to it. An entry you wrote on your phone on a Tuesday is just there, in full, if you open in.between on a laptop the following weekend — nothing to re-sync manually, nothing to export or import, nothing that feels like moving data between two different tools. From the user's side, it reads as one journal you can open several different ways, not several journals that happen to share a name.
That consistency extends to tone as much as to data. Nalani's voice, pacing, and the way it reflects things back to you were built to feel identical across platforms — the calm, unhurried presence people come to rely on for a nightly check-in shouldn't shift depending on whether they're tapping a phone screen or typing at a keyboard. A few interface details naturally adapt to each platform's own conventions, because a well-built app should feel native to wherever it lives rather than like a copy-pasted layout — but the actual experience of reflecting with Nalani, and the sense that you're picking up an ongoing conversation rather than starting a new one, was treated as non-negotiable across every version of the app.
- Same companion, every platform: Nalani's personality, memory of your history, and conversational style don't change depending on whether you're on iOS, Android, or the web — you're always talking to the same companion, not a lighter or heavier version of it.
- Journal history that just shows up: Entries written on one device are simply there the next time you open in.between anywhere else, in full, without any manual step to move them over.
- No feature left behind on one platform: The core journaling and reflection experience was built to be equally complete on phone and on the web, rather than treating one platform as the "real" app and the others as stripped-down companions.
- Interfaces that feel native, not identical: Layout and navigation adapt sensibly to each platform's own conventions — a phone screen and a browser window aren't meant to look pixel-for-pixel alike — while the actual experience underneath stays the same.
- Pick up right where you left off: Switching devices mid-week, or mid-evening, doesn't mean starting over or catching Nalani up. The continuity of the relationship is meant to be invisible, in the sense that you shouldn't have to think about it at all.
The real test of a cross-platform product isn't the first login on each platform — it's the tenth time someone moves between them without noticing they've done it. That's the bar the in.between team set for itself. Someone might start a journal entry on their phone on the walk home, decide to finish it later at a laptop, and pick up mid-thought without needing to remember where they left off or manually carry anything over. Someone else might journal on Android all week and then borrow a friend's iPad on a trip, signing in and finding their full history waiting exactly as they left it. None of that requires a conscious decision about which version of the app is the "main" one, because there isn't supposed to be a main one — every platform is a full front door into the same ongoing relationship with Nalani.
That kind of invisible continuity is easy to undervalue until it's missing. Plenty of apps technically exist on multiple platforms while quietly treating one as primary — the place where new features land first, where the experience feels most finished, where switching to another platform means noticing what got left behind. in.between was built to avoid that hierarchy altogether. Every platform was expected to carry the same weight from the start, which is part of why all three launched together rather than staggered over separate release windows.
Getting Started on iOS
On iPhone, in.between is available through the App Store as a standard download — search "in.between," install it, and sign in or create an account to get started. The onboarding walks through a short introduction to Nalani and a few preferences around notifications, since most people set up a reminder around their usual bedtime as part of getting the habit going. Once that's done, the app is ready for a first entry, whether that's a full check-in about the day or just a few lines to get a feel for how Nalani responds. iOS notifications are also where a lot of people set their gentle nightly nudge — a quiet reminder rather than an insistent one, timed to whenever you tell it your evening usually winds down. Voice entries work the same way they do on the rest of the app, so someone who'd rather talk through their day out loud than type it out has that option from the very first session, not as a feature added later once they're already settled in.
Getting Started on Android
The Android experience mirrors iOS closely by design, available through the Google Play Store with the same search-install-sign-in flow. That parity is intentional rather than incidental — Android users get the same onboarding, the same first conversation with Nalani, and the same access to journal history and reminders as iOS users, without a lagging feature set or a noticeably different look and feel. Anyone moving from an iPhone to an Android device, or vice versa, shouldn't need to relearn the app or worry about what they'll lose in the switch, because there isn't anything to lose — everything, including full journal history, travels with the account rather than the device. That was treated as a baseline requirement rather than a stretch goal during development, which is part of why both mobile apps shipped together instead of one trailing the other by a few months while the team caught the second platform up.
Getting Started on Web and Desktop
For anyone who'd rather reflect at a keyboard than a keypad, in.between is available directly through a browser, with no separate download required to get going. That makes it a natural fit for a laptop still open from earlier in the evening, or a desktop at the end of a workday before the rest of the night has really started. Signing in on the web uses the same account as the mobile apps, which means someone can create their account on a phone and then do most of their actual journaling on a computer, or the reverse, without any extra setup. The web experience carries the full journaling flow and the same conversation with Nalani — it isn't a limited preview meant to nudge people toward downloading a phone app, but a complete way to use in.between in its own right.
For people who split their evenings between a laptop and a phone without thinking much about it, the web app tends to become the default surprisingly fast. There's no install step to talk yourself into, no app icon to hunt for on a crowded home screen — just a browser tab, already open more often than not, that happens to also hold a complete version of the journal.
"I honestly didn't expect to use in.between on my laptop as much as I do. I first tried it on my phone, but most nights I'm already sitting at my desk finishing something up, and it felt silly to switch devices just to journal. Now I mostly do it right there in the browser, and then a couple times a week I'll add a quick voice entry on my phone from bed. It's the same Nalani either way, which honestly surprised me — I expected the web version to feel like an afterthought, and it just doesn't."
— Daniel Achebe, in.between user
A Companion on Every Platform, and What Comes Next
None of the flexibility around devices changes what in.between fundamentally is, and it's worth restating plainly here: Nalani is a wellness companion designed to support a nightly habit of reflection, not a licensed therapist, not a diagnostic or medical tool, and not a substitute for professional mental health care. That's true whether someone is talking to Nalani on a phone in bed, typing to it on a laptop, or opening it in a browser tab at a desk. Cross-platform availability was about removing friction and unfairness around who gets to use the app — it was never meant to suggest that in.between is equipped to handle clinical needs just because it's easier to reach. Anyone dealing with something serious, or in crisis, should turn to a licensed professional or a crisis line rather than any app, however available it is.
Shipping on iOS, Android, and web simultaneously was the starting commitment, not the finish line. The team has described the ongoing work as making sure that parity holds as the app grows — that a new feature landing on one platform doesn't quietly become the new thing the other two are missing, and that the sense of one continuous journal, reachable from wherever you happen to be, stays true as in.between adds to what it does. For a product built around a habit that has to survive real, imperfect evenings — the ones where the phone is dead, or the laptop is already open, or someone's borrowing a tablet from a partner — that kind of consistency isn't a nice-to-have feature. It's close to the whole point.
Frequently Asked Questions
Do I need to buy the app separately on each platform?
No. Your in.between account works across iOS, Android, and the web with a single sign-in — there's no separate purchase or subscription tied to a specific platform. Create an account once, on whichever platform you start with, and it carries over everywhere else.
Will my journal entries and conversations with Nalani show up the same way on every device?
Yes. Your journal history and your ongoing relationship with Nalani are the same no matter which platform you open in.between on. An entry written on your phone is simply there if you open the app on the web later, in full, without any manual step to move it over.
Is the web version a limited version of the app?
No. The web experience carries the full journaling flow and the same Nalani as the iOS and Android apps. Some interface details adapt naturally to a browser versus a phone screen, but the core experience — talking with Nalani, reviewing past entries, building a nightly habit — is complete on every platform.
Can I switch from iPhone to Android, or start on my phone and move to a laptop, without losing anything?
Yes. Because your account, not your device, is what in.between is built around, moving between platforms doesn't mean starting over. Sign in on the new device and your journal history and ongoing conversation with Nalani are there waiting.
Is Nalani a therapist or a medical tool?
No. Nalani is a wellness companion designed to support reflection and a nightly journaling habit — it is not a licensed therapist, not a diagnostic or medical device, and not a substitute for professional mental health care. That's true on every platform. Anyone dealing with something serious or urgent should reach out to a licensed professional or a crisis line rather than relying on an app.
in.between was built on the idea that a bedtime ritual shouldn't have to negotiate with your hardware — that whatever screen is closest when you're ready to reflect should simply work, with the same Nalani and the same journal waiting on the other side of it.
