Context: a concept for a dating service built around events that people create themselves. Sign-in goes through a state ID platform. A studio project
Role: the only product designer on the project
When: 2026, three months so far
Status: a concept in progress, in review with the client
Client under NDA. Visuals are recreated, and the logo is not shown.
In short
So far there are 18 concept screens and a sign-in flow of 24 screens. I also rebuilt two screens on the host platform’s design system; after calls with the developers we design outside that system. All counts on this page are from the Figma file, October 2026.
01 · The question: use the host platform’s design system or not
The client proposed building the app on the host platform’s design system, with our own base tokens on top. The reason was speed of development.
By then I already had a visual concept of 18 screens.
02 · I built part of the concept on that system
I rebuilt two concept screens, the home page and the public profile, with the host platform’s components. After that we had a series of calls with the development team.
On the calls it turned out that we could not adapt the system: we could only assemble screens from ready-made parts, with no settings of our own, and that would have broken the concept.
For now we design the screens outside that system. The client will confirm how the design system is made.
03 · From a list of events to one card per screen
In the first versions, events came as a list. Now there is one event on the screen, and the photo fills the screen behind the text.
I wanted to add a swipe, as in dating apps: people already know this mechanic. The concept went through three rounds of review, and most comments were about the swipe and the profile cards. Nothing was rejected: the client and I saw some things differently, so we tried several versions.
04 · The profile is a photo and a feed from events
A profile opens with a photo. Below it is a feed of photos and videos from events. I drew four states for this feed: the header collapses on scroll, a double tap adds a like, a long press opens a preview of the event, and a photo opens full screen.
05 · Sign-in: 24 screens from the client’s requirements
The client gave us written requirements for the first sign-in, with the edge cases: an age limit, an error on the host platform’s side, a required update. From them I designed a flow of 24 screens, with a PIN code, Face ID and permission requests.
How I used AI
I used AI to create prototypes and user flows to save time. Claude checked my flows for errors, collected examples from the web into summaries, suggested some improvements, and helped with texts and prototypes.
06 · I now plan five or six rounds of improvement from the start
The concept took three review rounds. I now plan five or six rounds of improvement from the start. The next step is the client’s: he reviews the screens and decides on the design system.