A personal product to solve my and other people's problem with emotional and productivity awareness.
I made Reflexio out of my own frustration. Constant notifications, endless calendars, and no clear way to tell whether I was actually stressed or just busy. I found the similar problem in online communities — people tried different productivity, AI apps and mood trackers, but most of them were shallow. No AI assistant that knows your emotional patterns, no patterns visible over time, no control over what you want the tool to remember. I put all of that into one product designed to help people like me to recognize how they feel, before burnout becomes invisible.
Before designing a single screen, I mapped everything I learned from competitor apps, community discussions, and my own pain into a clear user flow which includes onboarding, AI chat or voice interface, how user saves specific conversations and reflections, what data needed for analytics needed. Getting the structure right first meant every interface decision had a reason and also saved time during the design process.
Before showing the main interface, Reflexio asks how user feels, for what reason they came, and what's their peak productivity time. This shapes how the AI assistant communicates and what it surfaces first, of course user always can change this later. Establishing such intent during onboarding means the product feels personal from the first interaction.
The daily check-in needs to be conversational and quick, that's why the AI adapts its responses based on what it has learned, and the user controls exactly what it remembers. This way people can complete a reflection quickly without the clinical feeling of filling out a survey. A voice-first interaction with a grounding prompt turns the check-in into a moment of pause rather than another task.
From observing both users' needs and my own, I wanted to see our focus windows, daily energy rhythm, mood states, breaks taken, and progress over time. Other apps let you log how you feel, but almost none show you what those entries mean. I made sure Reflexio surfaces that rhythm: when energy peaks, how mood shifts across the week, whether this week looks different from the last four.
Reflexio has no production users, so there are no fabricated metrics. Instead, these are the metrics I'd track to validate whether the core idea holds.
Onboarding completion and first reflection completed. If users don’t even finish setup and complete their first check-in, the product never gets a chance to prove its value.
Reflections per week and reminder response rate. A reflection app that users open once and abandon has failed at its core promise.
Reflection is a habit, so retention over weeks is the clearest signal that the product is working.
Completion consistency and analytics engagement. If users log reflections with AI, but never look at their patterns, the core idea isn’t being validated.
Reflexio is a personal product exploration that was designed and prototyped, but not shipped. What it demonstrates is how I approached a product from the beginning: identifying a problem I personally experienced, then researching how others experience it too, distilling that into structure, then designing around that structure and testing.