FlashGrub
Clarifying a concept-dense product through iterative, accessiblity-driven app design.
Role
Product & Operations
Timeline
September 2025 – Present
Team
Solo contributor (report to CEO)
Due to confidentiality agreements, detailed designs and implementation specifics are not shown. I’m happy to discuss my process, decision-making, and learnings in more detail in conversation.
Challenge
FlashGrub is a pre-launch mobile app that connects users to local restaurants and markets that have surplus food. It sells pre-made meals and unsold food at a discount, reducing waste and supporting families in accessing affordable meals.
As both a subscription service and a pay-as-you-go discount app, first-time users struggled with:
- Grasping how the platform worked, what features were available, and what value they gained from buying through the app
- Understanding the subscription model, its logistics and conditions, and its added value
Ultimately, the core challenge was making a choice-complex idea feel like an intuitive process within just a few screens.
How Might We...
- ...communicate a multi-part value proposition without overwhelming users?
- ...introduce a subscription model with multiple tiers while simultaneously preserving our value within a free model?
- ...guide users within the intended flow while still allowing free exploration?
Qualitative Outcomes
- The app became more informative and easier to understand for first-time users
- User testing showed improved comprehension of FlashGrub’s concept
- The subscription offering included greater clarity, user freedom, and appeal
My Role
As a Lead Product and Operations Intern, I work closely with the founder to iterate on the app and prepare it for launch, focusing on helping users understand FlashGrub’s value proposition and navigate a product that blends the functionality of traditional marketplace and subscription apps. I worked independently, contributing in all respects to the end-to-end iteration process while checking in weekly with the founder to review findings and prototypes, challenge assumptions, and align on next steps. My process consists of:
- Conducting competitor and market research
- Prototyping and iterating on app features
- Running external beta testing
- Performing internal quality checks
- Incorporating user feedback into design decisions
- Translating abstract ideas into actionable product choices
Approach: Research, User Testing, Iteration
Designing for Users, Not Assumptions
A key shift in my process was learning to design based on observed user behavior rather than personal intuition. As a product designer, I have improved upon:
- Identifying moments of confusion or uncertainty
- Reducing cognitive load in concept-heavy flows
- Emphasizing clarity over feature density
- Iterating incrementally instead of full redesigns
Reflections & Learnings
One of the biggest lessons I have learned so far has been learning how effective products subtly guide users toward next steps without making those paths feel forced.
Furthermore, continually engaging in feedback loops sharpened my product thinking — decisions were grounded in observed behavior, and iteration became more focused and defensible.