Context

• In early 2019, Swiggy decided to extend its popular food delivery to include Swiggy Stores and Swiggy Go (groceries and Pickup Drop service lines)
• While my manager worked on the Swiggy Stores storefront with another designer, I took the responsibility of designing the Swiggy Go flow, along with the post-order flows for both Swiggy Stores and Swiggy Go.
• Swiggy Go aimed to take on Dunzo in the cities it was already serviceable in, with the idea that Swiggy offered much more coverage and flexibility than Dunzo.
• Unlike food and stores with a distance limit of 6 kms, Swiggy Go would cover as far as up to 30 kms anywhere in the city. It would start in Bangalore in phase 1, and be scaled to other metros in phase 2.

Project brief

<aside> 👉 Design the Swiggy Go experience to allow people to get anything delivered from one point to another point in the city. The intent is to allow for as much flexibility as possible with Swiggy Go for customers, and to realize the true potential of someone doing your tasks for you.

</aside>

Roles & responsibilities

I was managing a team of 4 designers who were working on other products and services (food, supply and delivery), so I took up the individual contribution role for Swiggy Go, along with designing the post-order workflows for both Swiggy Stores and Swiggy Go.

In order to keep the tech effort to a minimum, we would make the Stores and Go storefront as a PWA, and the post-order experience for Stores and Go would have the same framework but contextual order status and updates.

Design process

Discover

Having been one of the early adopters of Dunzo, I was very familiar with the end-to-end experience and was frankly looking forward to seeing how i could do one better than Dunzo. Dunzo's key USP was not the pre-order but the post order chat flow with the delivery partner, which meant that the customer's queries could be cleared in the chat itself and the handover was pretty smooth.