

Competitive Analysis
I started the project with a look into the competitive landscape of apps focused on shopping local and sustainably with some additional secondary research on the industry.
The secondary research and competitive analysis helped better understand the landscape of apps that connect consumers with locally and sustainably grown food. I examined both direct competitors, such as SimplyLocal, Soko, GrownBy, which focus on connecting users with local farmers and markets, and indirect competitors like Farmish, Thrive Market and Market Wagon, which provide convenient online shopping experiences for organic and locally sourced goods.
By analyzing their strengths and weaknesses, I identified key opportunities for improvement, including enhancing product visibility, streamlining the ordering process, and creating a more user-friendly interface. This research provided valuable insights into how my app could differentiate itself by offering a seamless, transparent, and engaging experience for consumers looking to support local food systems and making the shopping experience easier.
POV & HMW
Based on the research findings and steps taken to define the problem, I determined that users who want to support their local food economy would benefit from a platform specifically focused on connecting users with local farmers and events. In parallel, this platform will allow users to plan and organize their shopping in-app.
The goal being that users can use this app through their whole shopping process making the scattered and overwhelming process of shopping local much easier.
Feature Diagram
To prioritize features for the app, I used the MoSCoW method to categorize them into Must Have, Should Have, Could Have, and Won’t Have based on user needs, competitive analysis, and feasibility. The Must Have features focus on core functionalities like a searchable map of local food sources, vendor profiles, and filtering options to help users easily find sustainable food. Should Have and Could Have features enhance the user experience, such as educational content, seasonal food tracking, and CSA subscriptions, while Won’t Have features—like live chat support—were excluded to streamline development and leverage existing tools. This structured approach ensured that the app remains user-friendly, functional, and scalable.
User Flows & Task Flows
After doing the MoSCoW matrix I wanted to get some ideas down for how these features could be laid out with some sketching. View ideation sketches here: Sketches.
In tandem, I worked on User Flows & Task Flows and let the two exercises inform each other. For the flows, I focused on the two main features of the app have the user work through Discovery and Shopping List for these tasks.
View User Flows & Task Flows here: User/Task Flows
Logo & Branding

Wireframing
From my initial sketches and User/Task Flows I had a good sense of what I would design, so moved into a digitizing Mid-Fi frames to get a sense of how the layout would look.
The specific aspects of Gather that I wanted to focus on in the design were the Home Feed, Discover, and Planner (Calendar & Shopping Lists), as seen below or in Figma.
HiFi
Usability Testing
I built an interactive prototype in Figma and performed a mix of moderated/unmoderated tests with 6 participants. I asked participants to freely use the app as they desired and then had them complete 2 tasks: Create a Shopping List and Search for a Farmers Market using the Discover filters.
The feedback was that overall people really liked the design and felt the app functioned as they would have expected. There were 2 critical comments one of which was around the lists section being hard to find and the other around the size of the food icons.
Priority Revisions
Based on the feedback received in the usability tests, I tried making the food icons on the vendor cards a bit larger and agreed it was easier on the eyes than the smaller original size.
I brainstormed how to address the lists comment that came from 1 individual, I didn’t want to change the Planner tab to Lists because this section also includes saved events. In the end, referring back to my POV/HMW statements the app is more focused on the discovery and connection to local food sources and the lists/events features in the Planner tab are more secondary features. Given this comment only came from 1 individual, I opted not to change anything.
Learnings
This project highlighted to me that more meaningful research can be achieved by being more selective with my interviewees and my line of questioning. This gave me a number of routes I could have taken with the product and what solution it provided to the users. Which meant when it came time to do feature sets, I had to be more selective for what would shape the Gather MVP. Good research from the start gave me more freedom to be selective down the road.
Next Steps
I would focus on implementing more vendor-side input within the app so shoppers can see up to date information, such as specific vegetables the vendor will be selling that day.
Communication tools in app where shoppers can connect with their local vendors to ask questions about their products or to just say hello!
Explore potential for online ordering and/or farm box subscriptions with additional user research.