Personal project: You on my mind


I helped to build a social messaging app with a unique twist.




Over the course of two years a friend of mine and I lifted it off the ground and released it on two platforms. Aside from designing user journey and interactions I was busy managing many things: branding, front-end for two platforms, website, and product. The app failed to gain traction, and was shut down.

My role

  • Founding
  • Product design
  • Interaction design
  • Usability testing
  • Website design

What I've learned

To not keep the idea secret, to not try to release the app natively on two platforms simultaneously, to not debate endlessly about features and to let things go. The core idea should be validated through a mock prototype, the feature scope kept really small, and audience built incrementally out in the open. It was a journey with ups and downs and I'm proud of what we were able to achieve.


Sometimes you just want to let someone know that you're thinking about them. Without words, sounds, emojis, or heartbeats.

Imagine receiving a phone call, on mute. There is a catch: the call is as long as the caller keeps his finger on the screen. The called person can also join this call session by tapping the screen performing a digital moment we called "touching fingers".

User journey

As development progressed, I tested the flows of screens, interactions, and the core yomm session mechanic with friends and acquaintances starting from the very first builds refining the UI from build to build.

The following screens featured here roughly showcase the a progression of a complete user journey:

1 Login
2 Friend discovery
3 Main app screen
4 Receiving a yomm
5 Session statistics
6 Anonymous yomm
7 Diary
8 Settings

User flow

The contact list starts out empty and it takes two to yomm. Friend discovery was solved by adding contacts directly or through the address book.

The core flow was kept simple: a scrolling list of friends allowed to pick a recipient, then a session was initiated with a tap. I created a diagram to map out all the screens we needed for the core functionality.

During a session one can join/leave at will. To understand how this affects the two journeys I demonstrated complex cases using the following diagram:

Additional credit: illustrations by Dávid Kozma