top of page

Group Order Feature

- PartyBowl

PartyBowl is an API that could be integrated as a feature with all food delivery platforms to help make the group order process easy and hassle-free. 

Frame 45XX.png
Frame 2cc.png
Frame 45XX.png

PartyBowl is a feature for Skip The Dishes, a food delivery platform to help make the group order process easy and hassle-free. 

The Problem

Our research showed that the number of small gatherings at home and online food orders increased substantially amid the pandemic. And people in a group that decides to order food online, need a way to place the order and split the bill efficiently because passing the mobile device around is unhygienic and splitting bills and settling paybacks for a large order is tedious.

panaFXGFXF.png
Role: UX Designer 
Team: A team of 4 UX Designers
Timeline: 8 weeks
The Solution

The video demonstration below gives an understanding of how our product functions. Hit play to watch the video demo! 

PartyBowl Demo
Features in PartyBowl
Frame 78145C.png

Host can pay for the entire order

Frame 21xs.png
Frame 78146C.png

Split the bill and pay for your own share

Frame 24xs.png
Frame 78147C.png

Set timer and spending limits 

Frame 22xs.png
Frame 78148C.png

Add individual food items from  respective devices.

Frame 20xs.png
Frame 78149C.png

Send reminders and give extra time to add orders.

Frame 23xs.png
The Process
Empathize
01
Frame 78137G1.png
  • Conducted Interviews within the studio

02
Frame 78139G1.png
Define
  • Defined User stories and identified pain points

03
Frame 78140G1.png
Ideate
  • Brainstorming 

  • Made guest and host user flows

  • Created paper wireframes 

04
Frame 78141G1.png
Prototype
  • Made Low-fidelity wireframes for the guest's and the host's flow

05
Frame 78142G1.png
Test
  • Conducted Usability testing of the low-fidelity prototypes

  • Made High-fidelity prototypes

Scroll down

Our research indicated that there are two categories of users in a party or a get-together, the guests and the host, and they have different pain points. In cases of unplanned get-togethers, the host can be considered as the person who volunteers to place online food orders on the behalf of the group.

2 Personas
Group 347.png
Frame 3c.png
The Host
Group 347.png
Frame 4c.png
The Guests
P-PB
Frame 78145C.png

Difficult to keep track of everyone’s preferences

Frame 78146C.png

Difficult to stick to a
 pre-decided budget

Frame 78147C.png

Tedious to split the bills

Frame 78148C.png

Awkward to ask
 someone to pay

Frame 78149C.png

Uncomfortable to
 share device password

Host's Pain Points
Frame 78145C.png

Doesn’t have the freedom to order what he wants

Frame 78146C.png

Uncomfortable to discuss the payment

Frame 78147C.png

Tedious to split the bills

Frame 78148C.png

Uncomfortable to use someone else’s device

Frame 78149C.png

Finds it awkward to ask for the host’s phone 

Guests' Pain Points

From our research, we learned that when people in a get-together or a party place online food orders, either the host of the party decides to pay for the entire online order, or sometimes the people in the party decide to split the bill together. In PartyBowl, the host is not necessarily the person hosting the event, but anyone from the group who starts the group order. The guests get to add their items to the group order.

2 Scenarios
Group 347.png
Frame 10z.png
Host pays
Group 347.png
Frame 11z.png
Group splits the bill
Task Flows

01

Group 347.png
Frame 10z.png
Frame 1311.png
Host pays

02

Group 347.png
Frame 11z.png
Frame 1211d.png
Group splits the bill

For our next step, we made paper wireframes and then transformed our ideas into low-fidelity prototypes and conducted 8 moderated usability testings. We asked the participants to perform various tasks and collected feedbacks from them. Based on this feedback, we assessed our insights and started to notice patterns. This helped us decide what changes needed to be made before we moved to our high-fidelity prototype. The wireflow given below shows the paths a user could take during the usability testings.

8 Usability tests
Frame 16z.png
Deep Dive!
Group 347.png
Frame 10z.png
It's On Me!

This section contains wireframes and prototypes for the flow when the host decides to pay. Once the host starts the PartyBowl group order, guests can add their items, and the host finally pays for all the items before placing the order. 

Low-fidelity Wireframes 

Frame 14aa.png

This section contains wireframes and prototypes for the flow when the host decides to pay.

High-fidelity Mockups

Frame 18z.png

01

02

03

04

05

Start group order

Host pays

Set spending limit

Set timer

Share invite link

Frame 19T.png

Menu

Group order status

Send reminder

PartyBowl Locked

Proceed to Pay

06

07

08

09

10

Group 347.png
Frame 11z.png
Split The Bill

This section contains wireframes and prototypes for the flow when the group decides to split the bill. Once the host starts the PartyBowl group order, guests can pay for their individual shares before adding them to the group order. Once everybody has paid their share, the host places the order.

Low-fidelity Wireframes 

Frame 15dd.png

High-fidelity Mockups

Frame 20cvcv.png

Menu

Share invite link

Set timer

Split the Bill

Start group order

05

04

03

02

01

Frame 21y.png

06

07

08

09

10

Individual carts

Individual payments

Individual items added to the group order

Give extra time

Place group order

Because it matters..

These are some of the changes we made to our high-fidelity prototype based on the usability testing feedbacks...

Frame 17ff.png

Issue 01

Update 01

Issue 03

Update 03

Frame 17ff.png

Issue 02

Update 02

Issue 04

Update 04

Update 01:

Added supporting text to QR code 

Update 02:
Added a supporting text and redesigned the timer for consistency.

Update 03:

Removed ‘Lock PartyBowl’ to avoid confusion

Update 04:
Provided context to “It’s on me” and “Split the bill” to make it easy to follow

Arto
Netflix
bottom of page