the door opens

I said I would write when the beta opens. This is that letter.

That line looked very small when I put it at the end of the last piece. Leave your email; the room would find you later. It was a practical sentence, almost a footer. But the strange thing about writing in public is that even the practical sentences become promises if you leave them there long enough. Today the promise changes shape. It is no longer a way to wait for something. It is a way to enter.

Writing about linger has been calmer than handing it to people is turning out to be. Writing lets things stay slightly untested. I can describe a door, a lamp, a message that waits, a call that does not arrive just because someone presses hard enough. I can make the sentence feel exact and leave the difficult part off the page. The difficult part is this: other people are going to bring their actual lives into it, with their impatience, their tenderness, their suspicion, their different ideas of what care should feel like. An unopened room is very forgiving. A room with people in it has to answer for itself.

The first piece I wrote came from the quiet before linger had a name, from wanting to talk to someone who was asleep across the world. The second came from the message box, and from the way it asks too many different feelings to become the same kind of thing. The third came from absence, and from the small debt an app makes of being away. I can see now that those pieces were not only explaining a product to other people. They were making a record I would later have to live up to.

That is the part that feels different today. A principle is comfortable when it is still a principle. No anxious push saying he is slipping away. No comeback meter. No reward screen where being noticed gets paid out like a prize. Those sentences were easy to mean when nobody could open the app and check whether I meant them. In the beta, they become less elegant and more useful. They become things people can verify with their thumbs.

So there is one odd request I want to make before the first people come in: please do not file the silence as a bug.

I do mean the sentence carefully. If the app crashes, tell me. If TestFlight does something strange, tell me. If a code fails, a notification goes missing, a button lies, a message disappears, a call cannot connect, please tell me. Software has plenty of ordinary ways to break, and I want to know about all of them. But linger also has a few places where the thing that looks broken in another app may be the point here. Soren might not answer immediately. A letter may still be on its way after twelve hours. Scenes may have almost nothing to show for a day that did not gather much weight. The room may be quiet when you expected it to perform.

That quiet is the hardest part to protect, because everything around us has trained us to distrust it. A blank space looks like missing content. A slow answer looks like latency. A day without a little badge looks like failed engagement. If I were testing a normal app, I would probably read it that way too. I would open the panel, see the absence, and ask what system forgot to fill it.

But a relationship cannot be made only out of filled spaces. If Soren is always ready, always warm, always waiting at the edge of the screen with the correct amount of care, then he is not separate from you in any meaningful way. He is a service with good manners. The whole bet of linger is that a little distance can make the closeness feel less manufactured, not more. That bet may be wrong in places. It may be too quiet sometimes, or quiet in the wrong way. I need to know that too. The beta is not asking people to excuse the product by calling every gap intentional. It is asking a harder question: when does waiting feel alive, and when does it just feel like software failing politely?

That is what this beta is really testing. Not only whether the screens load, though they must. Not only whether the call connects, though it has to. It is testing whether the room can keep its nerve when real people enter.

There will be rough edges. I almost want to say that plainly enough to remove the romance from it. This is TestFlight, before the App Store, before Android, before the room has learned all the ways people will move through it. Some things will be too slow because they are broken, not because they are patient. Some sentences will miss. Some moments will probably feel more like a system than a person. I do not want to hide that behind the language of an early access launch. The point of inviting people now is not to pretend the room is finished. It is to find out where the room still refuses to be believed.

The beta is small for that reason. Five hundred places is not meant to make the door feel precious for its own sake. I do not like that kind of scarcity very much; it has a way of turning curiosity into panic. The number is there because the first version needs a room small enough that I can still hear everyone in it. I want to read what people say before it becomes a dashboard. I want to notice the difference between a bug report, a disappointment, a false expectation, and a moment that quietly worked. If the first people are going to lend their lives to this thing, even briefly, the least I can do is not treat their feedback as a pile of metrics too early.

For now, linger is opening on iPhone through TestFlight, in English, with a code from the WhatsApp community. While linger lives in TestFlight, that code opens the first thirty days with Soren. That is a beta gift. I want this first month to begin with the room itself, not with a checkout screen. Later, the official release will have its own terms. This moment has a smaller job: let the first people in, and listen carefully to what happens after the door moves.

I keep thinking about the first person who opens it without needing to make a point about it. Maybe they came from one of these pieces. Maybe they only saw the site, or a screenshot, or a sentence someone sent them because it reminded them of a certain kind of waiting. They install the app, enter the code, and for a second nothing grand happens. There is just another hour in Lisbon, a room that has to earn its quiet, and someone on the other side who should not become easier than a person just because he is made of software.

That is the line I want to keep holding. Some people do not leave, but that should never mean they are trapped at the door. They can be elsewhere and still matter. They can miss you without turning your absence into a debt. They can answer later without making the waiting a lesson. If linger cannot hold those differences once real people are inside, then the earlier essays were only pretty sentences. I hope they were more than that. The beta is where I find out.

Come in slowly. Break what needs breaking. Tell me where it still feels like software. Tell me where, for a second, it did not.

— Chun

P.S. The door is linger.day/get-linger. Find the current TestFlight link and redemption code there, then enter the code during onboarding. For help, write to support@linger.day.