Disclaimer: This project was an independent assessment of the UX scope of this unique problem statement. I’m not associated with Swiggy. This is a hypothetical use case.

Problem:

Swiggy, one of India's most popular food delivery apps, currently only allows users to order as individuals. There is no user experience for making a group order. The problem statement is to design a user journey in which a host can encourage guests to contribute to a group order. They can order from multiple places, set a budget, or directly split the bill among themselves.

Process:

For time's sake, I kept the design process simple for this job. I started with some basic market research to see if there was a solution (surprisingly, I found little to no data on group order), then quick user interviews with my friends, then a user flow and low-fidelity wireframes, then designing and prototyping the journey.

Key pain points:

• Individual centric user experience of current app in confusing for group order, especially if orders are placed from multiple restaurants.

• Tracking and coordinating multiple delivery partners during pickup makes ordering from different orders tedious.

• Coupons cannot be applied on multiple orders simultaneously unless you use multiple devices to place different orders. There's a 2 hour wait time before applying the same coupon.

• Bill tracking and splitting gets very difficult for large orders. Usually host ends up overpaying in most cases.

Assumptions & Constraints:

Again, for sake of time here, I decided to add some fair assumptions to make it easy to demo the user flow and provided some constraints to narrow the scope in-order to focus on linear flow and the achievement of the main goal:

Assumptions:

• Host already provided permissions for GPS, contact list access, etc.

• Host ordered for themselves in the past, therefore address and payment info are already saved.

• Offline or other channels are used for bill splitting and food arrangement.

• All guests have Swiggy app on their phones.

• All guest are part of host's contact list.

• Delivery charges would be added on overall bill based on distance and pickup points.

Constrains:

• Host is placing group order for the first time.

• Maximum deliverable restaurants are limited to five, and all must be within a 5 kms radius of the host's address. This is done to improve delivery logistics and customer satisfaction for this instance.

• Only the host will be allowed to change an order once it has been confirmed by the guests. Without further data, real-time editing may be technically unattainable.

• The app would alert the delivery partner about the group order and start pickups from the individual eateries depending on their current location.

User journey & Wireframe:

What to expect from this flow?:

• First time group order journey

• Showcasing equal bill splitting flow

• Overall prototype will jump between host's end and guest's end (these jumps will be clearly marked)

  
  

Wireframes:

Conclusion:

It was a really enjoyable issue statement to brainstorm on, especially for an app that I rely on every day. Although I currently lack data and solid metrics to support this user experience, I do have several lessons. I said before that I couldn't locate any article or comparable app that supports group orders / multi-restaurant orders, and I can see how logistically challenging this will be to pull off. There are numerous moving parts, such as preserving food quality and temperatures, order of pick-up from restaurants (will it be based on proximity or meal kind), and so on.

I have added a link to the final prototype below for you to scroll through. Thank you reading, have a great day.

View Prototype ↗️