top of page

for positive impact

Introducing a Schedule feature for Swiggy: A UX/UI case study



This was an assignment given by Design Sundays as a screening test for their UX Design internship program.


A lot of people depend on food delivery services for their meals. During open-ended research, it was revealed that a lot of regular users feel that while there are a lot of options for them to order from, they don’t tend to have time on their hands when they actually want to order food.

The product team wants to solve this disconnect by building a feature to schedule orders and extend it to create weekly and monthly subscriptions.


As a UX Designer, I was tasked with building an experience for a user to be able to schedule & subscribe to the food of their choice.


  • Design a solution for Android or iOS, honoring their guidelines.

  • Decide between Swiggy or Zomato & follow their design ideology and Ul patterns.

  • Ensure that the feature finds a logical place within the information architecture.

I decided to go with Swiggy because of its simple user interface, which will be easier to replicate. I followed material design guidelines for android.


I only had 5 days to finish this assignment. So I started doing user research right away to figure out how this feature would work for my target audience. I began the Ideation process after studying the data from the research phase. After that, I created high-fidelity mockups.

swiggy process.png


  • I believe people who order food on a daily basis are mostly working professionals who don’t have much time to order food.


First, I conducted some desk research by reading some articles online and looking at competitor apps to see if they have this type of feature available on their app. (they didn’t)

Then I went on to conduct primary research on working professionals, who were my target audience. I conducted a telephone interview with four people who regularly order food from online platforms. We talked for about 15–20 minutes about their work and environment, eating habits, and food preferences, among other things.

Key things I wanted to learn.

  • Understanding how the scheduling/subscription feature would help them.

  • Discover any pain points in the current food ordering process.

  • Key factors while selecting a particular food item.

Pain points discovered from the research

  • There is a time gap between when customers actually want their food and when they get it delivered.

  • Users dislike having to go through the same food ordering process everyday.

  • Having too many options to choose from makes the food ordering process time-consuming.

  • Some people often skip their breakfast or lunch sessions because they are preoccupied with their work.


Who will benefit from this feature? To get a basic understanding of this, I created a user persona of my target audience.

swiggy persona.png

Use Cases

I wrote two use cases of how a user will interact with the feature based on the people I spoke with during the research phase.

Case 1: As a working professional with a tight schedule who does not want to miss a meal session due to delayed food delivery, they schedule their meals ahead of time to reduce the risk of missing a meal.

Case 2: As a student with set lunch break times, scheduling their food ahead of time ensures that the food is delivered according to their break times.

User Flow

Next, I created a user flow as part of the ideation process to create a visual representation of the steps a user would take to reach their end goal.

swiggy user flow.png

Paper Sketches

Here are a few iterations of the rough paper sketches I came up with.


Hi-Fidelity wireframes

I then proceeded to create high-fidelity screens in Figma.

swiggy attention.png
Swiggy schedule screen.png
swiggy notification.png


Wow! I can’t believe I managed to complete this assignment in 5 days. These project really pushed me to my absolute limits and I am grateful for that.

If time had not been an issue, I would have designed a few more screens and held a user testing session to validate my prototypes and reiterate them further if needed.

bottom of page