SPRINT17 - Mobile App

Localite

Local restaurants, in-house delivery

Problem Statement  

How might we make food delivery affordable for people by providing a platform for restaurants to achieve in house food delivery?

Problem Background  

Ordering food from the comfort of home is not anymore just a convenience but  a luxury. Restaurant owners are hiking the price of the food in order to make up for the high commissions to third-party food delivery services.

There is no effective platform that unites local restaurants who are willing to do in-house delivery to help grow their sales and reduce the cost to their customers. 

Research Insights

User Pain Points

  • Customers are not able to book from local restaurants that provide dine-in only
  • Customers pay more for food delivery services from existing third-party delivery apps 
  • Restaurant owners are paying high commission on third-party delivery services
  • Restaurant owners have reduced sales because customers are ordering less 
  • Third party delivery apps orders are not fulfilled if tips provided by customer is low, thus restaurants are making a loss by wasting food

Supporting Data

According to Paytronix, 63% of restaurant customers have not used a third-party delivery service since early 2020. Four in 10 said it’s because they don’t want to pay delivery fees, and more than a quarter said it’s simply too expensive.

Feedback

While conducting our own user research, 100% of customers interviewed are affected by delivery surcharge. People are not able to order food from restaurants at nominal delivery charge. 75% of customers I interviewed opt to pick up or cook at home because of the high overall cost of the food delivered to home. 100% of people interviewed were not able to order from their favorite restaurant which they are willing to support by paying a nominal fee whereas the restaurants are depending on third party delivery apps like  Uber Eats, Doordash, Skip meals etc. which are costing more for users. 

Landing on the Solution 

Based on our customers and restaurant owner’s pain points, we would like to create a platform Localite which lists local restaurants having their in-house delivery system. In-house delivery systems would be a new norm, as it can reduce the cost to customers thereby increasing restaurant sales and more satisfied customers.

User Flows:  

Future Steps

Possible additional problems to address, 

  • Support accessibility
  • Provide services from in home delivery/catering 
  • One click place order
  • Support chatbots

App Icon

Image 1: App Icon for Localite

Learnings

Product Manager Learnings:

Swathi Rumale Shivarudra

  • I am more empathetic than ever
  • Understood how pain points of people can be simplified and resolved 
  • Mentor feedback was valuable to understand my mistakes which helped me to improve on spec
  • User story helped me to place in different people shoes
  • Co.lab is very engaging and I got to meet some really cool folks

Designer Learnings:

Designer Learnings:

Jo Sturdivant

  1. Adapting to an Established Team: Joining the team in week 6 of 8 was challenging, as I had to quickly adapt to existing workflows, dynamics, and goals. This mirrors real-world situations where you often integrate into teams mid-project, and flexibility is essential.
  2. Work-Blocking for Efficiency: With only two weeks to complete the project, I learned the importance of a structured work-blocking system. This approach allowed me to manage my time effectively and meet deadlines under pressure.
  3. Making Data-Driven Design Decisions: Unlike my past projects, I had to rely on research conducted by others. This was a valuable experience in using pre-existing data to guide design decisions, helping me focus on the core insights without starting from scratch.

Developer Learnings:

Developer Learnings:

Vanady Beard

&

As the back-end developer, I learned how important it is to create efficient and reliable systems that support the entire application. This experience also taught me the importance of optimising the database and ensuring the backend is scalable and easy to maintain.

Developer Learnings:

Stephen Asiedu

&

As a back-end developer, I've come to understand the importance of being familiar with various database systems and modules. This knowledge enables me to build diverse applications and maintain versatility in my work. I've also learned that the responsibility for making the right choices rests on my shoulders, guided by my best judgement.

Developer Learnings:

&

Developer Learnings:

Maurquise Williams

&

  1. Process of Creating an MVP: Developing a Minimum Viable Product (MVP) taught me how to focus on delivering core functionalities balancing between essential features and avoiding scope creep.
  2. Collaboration in a Real-World Tech Setting: This experience taught me how to collaborate efficiently in a fast-paced tech environment, keeping the team aligned and productive, even while working remotely across time zones.
  3. Sharpening Critical Thinking and Problem-Solving Skills: This experience honed my ability to think critically and solve problems efficiently. By tackling challenges and finding quick solutions, I sharpened my decision-making and troubleshooting skills in a dynamic, real-world setting.

Developer Learnings:

Jeremiah Williams

&

All in all this experience was very awesome I learned that in coding with others being transparent is key

Developers Learnings:

Justin Farley

&

I learned how important communication is when working with a team. Communication provides understanding, advice, ideas, and much more. While working with the product team, I’ve found that communication keeps everything flowing smoothly. Working with a team also showed me that every member brings something different to the table and we all have to work together in order to align and meet our end goal.

Full Team Learning