Loading
← Back to workLianne

UI / WEB DESIGN · 2023

YLanes

Designing a web home for a mobile-first conversation platform — without losing what made it feel alive.

ROLEUI Designer
TEAM2 Designers
SCOPEWeb App
YEAR2023
YLanes

01  The Design Question

A candid-conversation app, already live on iOS and Android, needed to exist on the web.

What is YLanes?A curated, small-group platform for real conversations — structured, moderated rooms for meaningful discussion.
Why web?Mobile shipped first. But hosts and moderators — the people running rooms — needed a bigger canvas to manage them.
My constraintI joined after mobile was locked. No fresh research. The brief: translate a mobile-first product to web without losing its soul.

02  Three Key Decisions

Decision 01 · Architecture

Put the filters in front of the content, not behind it.

Most community products bury filtering in a dropdown and lead with a feed. I gave categories, room types, and time windows their own persistent columns, level with the rooms themselves. On YLanes, what you're willing to talk about is the navigation — someone looking for rooms on grief shouldn't have to dig through the same UI as someone browsing relationship topics.

Trade-off: the page is heavier than a typical feed. That's the right heaviness — it reflects that choosing a room is a real decision, not a simple scroll.

YLanes rooms interface — filters lead, level with the rooms
Decision 02 · Entry

Make people write something before they can register.

The “Your Take” box isn't optional. Before you can join a room, you have to say what you're bringing to it — a question, an experience, a resource, a perspective. Visually, I gave it a yellow outline and the full right column, so it reads as the primary action on the page, not a form field. The Register button sits inside it; you can't get to one without the other.

Friction as a filter: if someone won't write two sentences about why they want in, they're probably not the person the room needs.

YLanes room details — the “Your Take” box gates registration
Decision 03 · Messaging

Show that the conversation is temporary. Don't hide it in settings.

YLanes messages disappear after 24 hours. Most products would treat that as a backend policy and never surface it. I put “Chats visible only for 24hrs” centered at the top of every thread — not as a warning, as a frame. It changes how the UI feels: you're not writing into an archive, you're writing into a moment. The typing indicator, the soft yellow message bubbles, the lack of reactions — all of it reinforces that nothing here is being kept.

The product's disappearing messages was the concept. Surfacing it honestly in the chrome was the design call.

YLanes chat — “Chats visible only for 24hrs” framed at the top

03  Brand & System

Web patterns pull toward dashboards — density, persistence, performance. YLanes needed to feel like a living room instead.

Signal Yellow#FFCB00
Paper#F2F2F2
Ink#242424

04  The Rest of the System

Landing page, profile, connecting with moderators, earning YCoins — the supporting flows that hold the product together.

Supporting flows

05  Reflection

The hardest part wasn't the screens — it was resisting the pull of web conventions.

What it taught meWeb patterns pull toward density and persistence. The real work was keeping YLanes feeling like a living room, not a dashboard.
What I'd do differentlyPush earlier for a shared component library across mobile and web — I retrofitted consistency that could have been designed in from the start.