What we learned building Tangled

We didn't build Tangled because relationships needed another app.

We built it because the internet is extraordinarily good at helping people meet, and shockingly bad at helping them stay close.

Dating apps can introduce you to a stranger based on geo-proximity and matching algorithms. Messaging platforms let you transmit text and media instantaneously. Cloud storage hoards tens of thousands of uncurated camera roll photos. Shared digital calendars track dentist appointments and flight itineraries.

Yet, where is the digital home built specifically around the intimate reality of a two-person relationship?

For most couples today, their digital intimacy lives entirely inside a single messaging thread on WhatsApp, iMessage, or Telegram. And look at what that thread has to compete with: it is sandwiched between an urgent slack from a manager, a delivery alert from an e-commerce courier, a verification OTP from a bank, and a 50-person family group chat arguing about politics.

A partner's tender observation sent at 2:15 PM is treated with the exact same transactional urgency and visual hierarchy as a reminder that your electricity bill is overdue.

We felt that was broken. So we built **Tangled**—a private space designed strictly for two.

Lesson 1: Relationships Are Not Social Networks

The fundamental architecture of modern consumer software is built on the concept of the *network graph*. Networks optimize for nodes, edges, virality, and audience broadcasting. They thrive on engagement metrics: follower counts, likes, comments, and algorithmic feeds.

When we began designing Tangled, our earliest instincts were contaminated by social network paradigms. We asked ourselves: - *Should there be shared badges?* - *Should we show relationship streaks?* - *Can couples share their favorite moments to an explore feed?*

Every time we tested these concepts, the product felt hollow, performative, and cheap.

A long-term relationship is the antithesis of a social network. It is not an audience-facing performance; it is a dyad. It has exactly two members. There is no audience to impress, no algorithm to game, and no content creator hierarchy. The moment you introduce "streaks" or "milestone gamification" into a relationship, you turn affection into an obligation.

We stripped it all away. Tangled has no likes, no public profiles, no streaks, and no algorithmic recommendations. It is an enclosed digital room with one door and two keys.

Lesson 2: The Sacredness of the Ordinary Tuesday

Ask someone to name the most important days of their relationship, and they will instinctively list the milestones: the first date at the bookstore, the weekend getaway in the mountains, the anniversary dinner, the proposal.

Those events are easy to remember because we deliberately commemorate them. We dress up, take photos, and post them.

But real relationships are not built out of anniversaries. They are built out of thousands of uncelebrated, completely ordinary Tuesdays: - An absurd photo of a dog sitting awkwardly on a park bench. - An inside joke born from a disastrously burnt dinner that only you two understand. - A shared song heard through grocery store speakers. - A spontaneous voice note recorded while walking home in the rain.

Milestones are preserved automatically; it is the fragile, ephemeral everyday moments that quietly slip through the cracks of digital life. In a chaotic messaging thread, those small gems get buried under logistics (*"Can you pick up milk?"*, *"Did you lock the front door?"*) within forty-eight hours.

Tangled was designed around the thesis that **the little things are the relationship**. By providing a dedicated space where couples can drop fragments of daily life—photos, notes, audio whispers, shared memories—without the noise of transactional daily logistics, those ordinary moments become an enduring tapestry.

Lesson 3: The Danger of Real-Time Surveillance

One of the most consequential decisions we made in Tangled was what to leave out.

Modern messaging apps have normalized an invasive culture of real-time presence surveillance: - *"Typing…"* - *"Online"* - *"Last seen 4 minutes ago"* - *Double blue read receipts*

These features were designed by enterprise collaboration engineers to enforce rapid response times in corporate environments. Exported into romantic relationships, they are an engine of quiet anxiety. If your partner reads a message at 10:00 AM during a hectic work meeting and cannot respond until 1:00 PM, the double blue tick transforms normal life into an unspoken tension.

In Tangled, we eliminated read receipts and real-time typing indicators.

When you share something with your partner in Tangled, it is not an urgent dispatch demanding an immediate response. It is a note left on a kitchen counter. They will find it when they arrive home. That deliberate shift from synchronous urgency to asynchronous sanctuary restored a sense of emotional safety that our beta testers immediately noticed.

Building for Intimate Computing

Building Tangled taught us that the next frontier of product design is not "bigger, faster, and more connected." It is smaller, quieter, and deeply intentional.

We call this **Intimate Computing**—software crafted not for the crowd, but for the sacred spaces where humans drop their armor and reveal who they truly are. It requires rejecting the traditional playbook of growth hacking and vanity metrics in favor of emotional resonance, privacy, and reverence for human connection.

Tangled proved to us that when you build software that respects people's most cherished relationships, you don't need tricks to keep them coming back. The connection is already there. The software just needs to hold the door open.