Use case 03
Shaping Mashpot from profile to participation
A 0-to-1 mobile product exploration for group discovery, group context, and lightweight participation flows.
Context
Mashpot was a 0-to-1 mobile product exploration centered on group discovery and participation. The most useful part of the work was product definition: treating discovery, joining, and ongoing participation as one connected flow instead of separate features.
Many community products break the experience into disconnected moments. People can browse groups, but they still struggle to understand whether a group fits them, what is happening there, and what changes once they join.
The app also had to hold different kinds of information on a narrow mobile canvas: groups, members, files, chat history, and event activity. The core challenge was sequencing information clearly rather than simply adding features.
Product shape
The strongest version of the concept came from narrowing it around three connected jobs: help people discover groups, help them judge whether a group is worth joining, and help them keep participating after the first decision.
That led to a product shape anchored around profile setup, a browsable group list, richer group details, and a lightweight communication layer. The value was not a polished screen set on its own; it was making the product model concrete enough to critique, sequence, and build on.
Interaction system
The interface language stays deliberately simple. Repeated cards, small status chips, member counts, and grouped sections help the product feel legible. Once people understand one part of the model, the rest becomes easier to predict.
That repetition matters in a mobile product like this. It gives continuity across onboarding, discovery, notifications, and chat without making every screen compete for attention.
What the exploration clarified
The work made it easier to separate what belongs in discovery, what belongs in group context, and what should only appear once someone is already participating. That gave the concept a clearer information architecture and a more defensible product scope.
Instead of treating community features as isolated surfaces, the exploration connected them into a product path that could support real use over time. Even without launch metrics, the work did useful product work: it exposed where context was missing, where interaction weight was too high, and what the product needed to feel coherent on mobile.