Circles: Find relevant people. Start a discussion. Build a Circle.

Aviu

Explore

Home

Projects

Contact

Elsewhere

01 Circles: Find relevant people. Start a discussion. Build a Circle.

Project overview

01 Circled

Project overview

01 Project overview

Circles: Find relevant people. Start a discussion. Build a Circle.
Circles: Find relevant people. Start a discussion. Build a Circle.

Whensomeonelivingabroadneedshelpwitha localquestion,a usefulansweris onlythe firststep.Circledexploreswhethera relevantdiscussioncangrowintoan ongoing,host‑ledCirclewherepeoplecontinuehelpingoneanother.

Circles is a mobile community platform for people living abroad, connecting them through local questions, language practice, and shared interests.

A Circle is a host-led space that grows from an active discussion into an ongoing community.

Timeline

April 2026 – July 2026

Company

Wikilook

Role

Product designer

Team

Product Manager: Daria K.
Developer: Toby

Founder and product owner: Daria K.
Engineering: Toby

Scope

MVP definition, UX/UI, reusable UI foundation, developer handoff

Links

Working MVP

Product direction

Circles began as a product‑design consulting engagement. Daria, a product manager, brought early screens and a broad product vision that needed to become a buildable MVP.

Define the MVP

Close a broad concept into a shared, buildable scope.

Define the MVP

Close a broad concept into a shared, buildable scope.

Establish the foundation

Clarify the first core flows and create a reusable visual and interaction system around them.

Establish the foundation

Clarify the first core flows and create a reusable visual and interaction system around them.

Deliver flow‑by‑flow

Move each priority flow from Figma into sprint delivery while keeping the product coherent.

Deliver flow‑by‑flow

Move each priority flow from Figma into sprint delivery while keeping the product coherent.

Product direction

Circled began as a product‑design consulting engagement. Daria, a product manager, brought early screens and a broad product vision that needed to become a buildable MVP.

Define the MVP

Close a broad concept into a shared, buildable scope.

Establish the foundation

Clarify the first core flows and create a reusable visual and interaction system around them.

Deliver flow‑by‑flow

Move each priority flow from Figma into sprint delivery while keeping the product coherent.

02 Circles: Find relevant people. Start a discussion. Build a Circle.

Core product flows

02 Circled

Core product flows

02 Core product flows

The MVP moves from a person’s first need to an intentional community: set the context, find what already exists, participate in a discussion, then give a committed host a way to create a Circle.

Start with personal context

Goals, languages, and location shape a person’s first feed.

Screens of the onboarding flow

Browse the feed

Interaction with feed. Filter chips are minimised, and then hidden on scroll down. On scroll up minimised version appears and stay minimised until the time user will back on top of the feed.

Search before asking

Search gives an existing conversation a chance to help before a new question begins.

Make participation visible

Clear states make it easy to read, contribute, and return to a conversation.

A Circle begins with commitment

Activity signals interest. A Circle begins only when someone chooses to host it.

05 Circles: Find relevant people. Start a discussion. Build a Circle.

Reflection and next steps

05 Circled

Reflection and next steps

05 Reflection and next steps

The design made the Circle lifecycle concrete enough to build. The next question is whether a qualifying discussion can become an active Circle with a committed host and participants who return.

Working MVP

What would make this successful?

Not simply creating more Circles, but seeing people return to contribute after a Circle begins.

Media 01: Conversion path diagram.
Caption: Qualifying discussion → host application → approved Circle → active Circle.

Media 02: Measurement card or small dashboard.
Caption: Track host-flow completion, invitation acceptance, first meaningful activity, repeat participation, and 7‑ and 28‑day retention. Watch for empty Circles, failed submissions, reports, technical errors, and moderation time.

Media 03: A small before/after comparison.
Caption: From fragmented source material to a buildable product and design system. Definitions, baseline, and review cadence still need product-team agreement before launch.