Gimme - Mobile, Admin & Merchant Dashboard
Gimme is a product connecting end users with merchants through a mobile-first experience built on the blockchain, supported by operational dashboards for both users and merchants.
The client entered the project with validated research and marketing insights. The core challenge was no longer discovery, but turning that insight into a coherent product structure that could scale across multiple surfaces and survive real-world implementation.
While the value proposition was clear, several product questions required design leadership to resolve
Even with a clear idea, several practical product questions needed to be solved:
How should the experience differ for users and merchants without making the product feel disconnected?
What information and actions needed to stay consistent across mobile and dashboards?
How could we ship an MVP without adding unnecessary complexity early on?
The primary risk was not lack of direction, but overbuilding and misalignment during execution.
I owned end-to-end design across the consumer mobile app, user dashboard, and merchant dashboard.
I was responsible for
Translating research insights into product structure and flows
Defining information architecture and cross-surface consistency
Making scope and priority decisions as constraints emerged
Working directly with engineering throughout implementation to adapt designs to technical realities
This required continuous judgment rather than linear handoff.
The design approach prioritized system coherence before interface detail
Clear separation of user and merchant responsibilities
Core concepts and flow stayed consistent across all surfaces
Features were scoped tightly to ship a usable MVP
This helped the team ship faster without creating unnecessary complexity
Chose clarity over feature volume to reduce setup and usage errors
Simplified early user flows to help users reach their first successful action quickly
Delayed secondary features to keep the product focused and buildable
Adjusted interactions when backend limitations appeared, without changing the core experience
These decisions balanced user needs, development effort, and delivery timelines.
Execution Across Surfaces
Designed to help users quickly understand the product and take their first key action
Designed for operational clarity, making it easy for merchants to manage their setup without confusion.
Designed to help the system manager oversee everything, with detailed information about both users and merchants
I worked ahead of engineering, designing one surface at a time. Once I finished the mobile app, engineers started building it while I moved to the dashboard. Throughout development, I stayed available to resolve questions and adjust designs when technical issues came up.
The product is still in active development. This case study reflects real design decisions made during build, not a polished post-launch story.
If I had more time, I would
Add better tracking to validate early assumptions
Expand merchant tools based on real usage and data collected
Standardize shared components across surfaces
This project highlights my strength in execution: taking validated ideas and translating them into coherent, multi-sided products that teams can actually ship.
Up next
