A gentle social memory app designed for introverts and socially anxious users — helping them capture someone right after they meet, refresh before they see them again, and stay in touch without the pressure of a CRM.
Context
Rehello started from a very different emotional premise than most networking tools. The problem was not "how do I track leads?" It was "how do I remember someone I just met without turning that person into a record?"
I wanted to explore a product that supports social memory for people who feel shy, overwhelmed, or mentally overloaded after meeting someone new. That meant the product needed to feel more like a quiet notebook than a productivity system.
The goal was to help users feel more human and more prepared in future interactions, not more optimized.
Product Framing
Most existing tools assume a transactional mindset: follow-up cadence, pipeline stages, or generic note fields. That felt wrong for this audience. Rehello needed a different product language, different interaction tone, and different priorities.
No pipelines, no status stages, no pressure loops. The app avoids the feeling that relationships need to be managed like tasks.
The first version stays focused on memory support. It helps users remember what matters and gently prepare, without pretending to teach them how to perform socially.
The visual system, copy, and interactions all aim to reduce anxiety. Every surface is meant to feel calm, lightweight, and forgiving.
I intentionally kept the app local-first and front-end only so I could focus on the product loop before introducing accounts, sync, or backend complexity.
Core Loop
The MVP was shaped around a simple sequence: remember someone, revisit them later, and feel more ready the next time you meet. That loop became the backbone of the product.
A multi-step capture flow breaks memory into gentle prompts instead of one blank note field. Users can record context, details, mood, and a light stay-in-touch reminder.
The recall surface condenses what matters before the next encounter: what this person is like, what you talked about, and what could be worth asking next time.
A chip-based picker turns vague intentions like "I should check in sometime" into a low-pressure reminder. No streaks, no guilt, just gentle prompts.
Key Decisions
Because the target user may already feel socially fatigued, I avoided open-ended forms wherever possible. Each step is one small decision, not a page of fields.
Everything stays on the device. That choice kept the MVP technically simple, but it also reinforced trust: this is personal memory, not social data to be uploaded.
I added a small set of pixel-style avatars to make people easier to distinguish and remember. The goal was not decoration alone, but adding gentle visual hooks for recall.
Instead of turning the app into an event planner, Prep stays lightweight: just enough conversation support to reduce friction before a mixer, class, coffee chat, or work event.
System Thinking
Although the app is small, a lot of product work lived in the system details: how people sort, how reminders surface, how empty states behave, and how the app avoids dead ends when onboarding, replay, import, or sample data are involved.
I spent a surprising amount of time refining flow logic and data consistency so the product would feel calm rather than fragile. The goal was not just to make screens look finished, but to make the app behave coherently across first use, later use, and edge cases.
A product can feel unfinished even with polished visuals if its state logic keeps surprising the user. Much of the real UX work here was making the app feel steady.
What I Built
AI Collaboration
I used AI as a rapid product-building partner across naming, framing, front-end implementation, debugging, and iteration. It accelerated execution, but it did not define the product point of view.
Reflection
Rehello shows how I think about product design beyond screens. The work was not only about styling an interface, but about reframing a category, shaping product language, sequencing interaction, and making a small system feel emotionally coherent.
If I continue the project, the next meaningful step would be testing the memory loop with real users and learning which parts genuinely reduce anxiety before social re-encounters. But even at MVP stage, the product already demonstrates a strong point of view: software can support social life without turning it into performance.