On shaping Mashpot from
profile to participation
Context
Mashpot was a 0-to-1 mobile product exploration centered on group discovery and participation. The work aimed to make community activity feel more navigable by treating discovery, joining, and staying active as one connected product flow.
A fragmented journey
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.
Mobile-first constraints
The app had to hold different kinds of information on a narrow canvas: groups, members, files, chat history, and event activity. The core design problem was sequencing information clearly rather than simply adding features.
Early product definition
Because the work was exploratory, the screens also helped define the product itself. They were a way to test the information architecture, product tone, and interaction logic before a heavier roadmap or system was fixed.
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 stay involved 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 in how those parts connect, not in any one screen by itself.
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 system, 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
- Discovery → detail → chat
- Group-centered IA
- Clearer product shape
Positive
- Clearer information architecture: the work made it easier to separate what belongs in discovery, what belongs in group context, and what only appears once someone is already participating.
- More coherent mobile flow: instead of treating community features as isolated surfaces, the exploration connected them into a product path that could support real use over time.
- Stronger concept definition: even without launch metrics, the screens did useful product work by making the idea concrete enough to discuss, critique, and build on.
What mattered most
- Product clarity: the concept became easier to evaluate because the screens focused on a few practical jobs rather than broad social-product sprawl.
- Screen-to-screen continuity: the strongest decisions came from treating onboarding, matching, and participation as one system.
- Future direction: the exploration left a clearer backbone for features like event activity, member context, and lightweight group communication.