Project Overview

Quick Tiffins asks users to complete two very different actions: commit to a recurring meal plan and order a one-time meal when needed. The design keeps both experiences accessible without combining them into a confusing menu structure. Subscription management, plan selection, and delivery scheduling are separated from quick ordering, while vendor and delivery partner interfaces were designed to keep every order moving through the same operational pipeline.

My Role & Contributions

• Mapped separate user flows for subscription plans and one-time quick orders.

• Designed plan selection and management experiences for single, weekly, and monthly tiffin options.

• Designed the customer app covering browsing, ordering, tracking, and subscription management.

• Designed the restaurant vendor interface for order intake and preparation status updates.

• Designed the delivery partner interface for pickups, assignments, and order completion.

• Built a shared design system across all three role-based interfaces.

• Delivered wireframes, prototypes, and handoff documentation for the development team.

Design Highlights

• Two clearly separated entry points for subscriptions and quick delivery.

• A plan comparison layout that makes the differences between single, weekly, and monthly options immediately clear.

• Subscription management designed for pausing plans, reviewing details, and managing upcoming deliveries.

• Category-based browsing for quick orders, including South Indian and Chinese sections.

• Order states designed to remain consistent across customer, vendor, and delivery partner views.

• Compact cards and clear pricing structures designed for fast decision-making on mobile screens.

Tools Used

• Figma

• FigJam

Challenges & Solutions

Challenge

Subscriptions and instant orders follow different user behaviours, and combining them into one navigation system risked confusing both new and returning users.

Solution

I created separate entry points and dedicated flows for each service while sharing common cart, checkout, and tracking patterns. This allowed users to learn the app once and apply the same behaviour across both experiences.

Outcome

• One app supporting both recurring meal plans and instant ordering.

• A clear subscription structure across single, weekly, and monthly options.

• Consistent order states shared across customers, vendors, and delivery partners.

• A reusable design system applied across three role-based interfaces.

• Complete user flows and prototypes prepared for development handoff.