Settings and Notifications in in.between: No Streaks, No Guilt
Settings and notifications in in.between follow a different contract than most apps on your phone. There are no streaks to protect, no guilt notifications designed to pull you back, and no pressure to perform insight for a scoreboard. This article explains the product stance: how in.between thinks about alerts, what it refuses to notify you about, and how any notice that does relate to your notes should stay honest — without inventing a full settings control panel that the Journey product story does not describe as a feature tour.
The Stance Before the Switches
Companion means respecting your time and history. That line from the Journey journal is the settings philosophy in one sentence. Many products treat notification preferences as a long checklist of engagement channels: daily reminders, streak warnings, “you haven’t opened us in three days,” social digests, and challenge nudges. in.between was built as a private room for the hours between waking and rest, with Nalani as companion — not as a habit game. So the first answer to “how do I configure notifications?” is product design, not a maze of toggles: the room should not shame you for absence, and it should not turn a night into a chart you must maintain.
Mental health and rest were priorities in how in.between was shaped. No shame mechanics. A night is not a streak and not a chart. Stay — in the Catch, Talk, Keep, Stay rhythm — means no streaks, no guilt, private to you, delete anytime. Those promises are stronger than any single preference row. If an app can guilt you into opening it, the preference screen is already negotiating with a broken premise. in.between refuses that premise so you do not have to hunt for an “off” switch for cruelty that was never shipped.
No streaks. No guilt notifications. No pressure to perform. Notifications, when they exist, should stay honest to your notes — not invent a debt you never agreed to.
What You Will Not Be Nudged About
Expect the product not to send messages that imply you failed journaling by sleeping in, skipping a week, or opening the room only at 2am. You will not get a broken-flame metaphor for consecutive nights. You will not get a countdown that your “progress” is about to expire. You will not get a performance review of how insightful last night’s entry was. Nalani is hopeless at scoring your sleep or turning a night into content; notifications inherit that hopelessness on purpose. Absence is not a defect in the companion relationship.
- No streak alerts: Consecutive nights are not a score the product threatens to take away.
- No guilt pings: Silence from you does not trigger shame-shaped copy to reopen the app.
- No perform-insight reminders: The room does not ask you to produce polished interpretations on a schedule.
- No sleep scoreboard pushes: Rest is not ranked; dreams are not graded for the notification tray.
- No feed FOMO: There is no public dream feed to “catch up on,” so there is nothing to spam about missed posts.
- Respect for late hours: Midnight to 4am is a core use case — not an afterthought that needs daytime nagging to “complete”.
Honest to Notes — Not Invented Engagement
When people ask for “settings,” they often mean two different things: (1) system permission to show banners on the device, and (2) product choices about which stories deserve a ping. For in.between, any product-level notice should stay honest to notes — grounded in something that actually happened in your private room — rather than inventing social urgency. An honest notice is about continuity of your own material: a quiet acknowledgment tied to journaling work you began, not a manufactured crisis because the calendar says you are “behind.” This Help article does not invent a full settings UI with labeled panes, nested toggles, or marketing names for every switch. Journey copy leads with stance: companion respect, no guilt, private delete anytime. Treat that stance as the durable guide while device OS permission sheets remain under your control on web, iOS, and desktop.
Device permission dialogs are separate from product guilt. Your phone or computer may ask whether in.between can present alerts at the operating-system level. Declining system permission is always a valid choice for a private journal. Granting permission does not license the product to run shame mechanics; the product still owes you the no-streak, no-guilt contract. If you allow alerts, hold the product to honesty: notes and presence, not performance theater. If you deny alerts, the room still works — Catch, Talk, Keep, and Stay do not require a notification tray to be real.
How to Think About Quiet Hours and Other Apps
Dreams often vanish under the first wave of unrelated notifications. Protecting the catch window — write or speak while the night is still close — often means silencing other apps more than configuring in.between. Companion Mode was designed for keeping things personal at any hour, including leftover feeling with no neat plot. You do not need a daily push from in.between to “start your ritual.” You need a room that is still there when you open it, without a lecture about the gap. Use Focus modes, Do Not Disturb, or OS quiet hours for the rest of the phone; use in.between for the fragment itself.
- Protect Catch, not a streak: Quiet the noisy apps that erase dreams; do not expect in.between to harass you into logging.
- Open when the night is close: Morning or 2am — both are valid; neither needs a calendar reminder to be legitimate.
- Cross-platform without multiplied nagging: Web, iOS, and desktop share one private room — continuity should not mean three devices guilt-tripping you.
- Notes over theater: If something notifies you, it should relate to your journal work, not to an invented challenge.
- Leave without debt: Closing the app or taking a week away does not create a backlog grade.
Pressure to Perform Is a Settings Failure
Some products hide pressure inside “helpful” defaults: morning check-ins, weekly insight emails, social proof that friends journaled more than you. in.between’s Journey story rejects that pattern. AI is good at answers; nights need questions. Nalani asks one honest question at a time instead of dumping interpretation on contact. Notifications must not undo that pace by demanding daily output. Settings, in the broad sense of product posture, include the decision not to ship engagement loops that look like wellness and feel like surveillance. You are not behind. There is no curriculum. Chat, Imagine, Markers, Index, Case File, and Brainstorm are pieces people live in — optional depth, not homework with due dates.
A night is a room and a companion who stays — not a notification strategy dressed up as self-care.
If you are looking for a step-by-step map of every preference row, this article will not invent one. What the product states clearly is enough to set expectations: no streaks, no guilt notifications, no pressure to perform; private to you; delete anytime; companion presence without a feed. For the broader wellness rationale, see the Help Center pieces on no streaks and no guilt, mental health and rest, and how the room works. For privacy controls that sit beside notifications — including deletion when you want material gone — see export and delete data, and privacy encryption delete. Use system settings on your device to allow or block banners; use this stance document to know what in.between will not ask those banners to say.
Practical Takeaway
Configure your device for the quiet you need. Do not wait for in.between to become a coach with a whistle. Open the private room when a fragment, leftover feeling, or late hour asks for it. Answer one question if Talk helps. Keep what recurs when Index, Markers, or Case File matter to you. Stay without performing. That is the settings model: fewer demands, clearer honesty, and notifications that never confuse care with coercion.
