Role: Solo Product Designer
Sprint: 1.5-Hour Rapid Feature Design Sprint (End-to-End UX & Wireframing)
Platform: Swiggy Mobile App (iOS / Android)
Tools: Figma, Notion
1. Context & Problem Statement
When ordering food for groups, the host pays the full bill upfront and faces friction afterward: manually calculating individual shares, switching to external UPI apps (GPay/PhonePe), and chasing friends for reimbursement.
This 1.5-hour design sprint focuses on integrating a native post-order bill-splitting feature directly into Swiggy to streamline group expenses without compromising order fulfillment.
2. Core Architectural UX Decision
Why Post-Order vs. Pre-Checkout?
- Funnel Protection: Placing the split option after order confirmation ensures Swiggy's core checkout funnel remains frictionless. Orders are never delayed or abandoned while waiting for group members to approve payment.
- 100% Payment Security: The host pays the total amount upfront via digital methods (UPI / Debit / Credit Cards / Net Banking), guaranteeing 100% order payment to Swiggy.
- Seamless Reimbursement: Collected shares are automatically credited back to the host's Swiggy Money Wallet or their original payment method as friends settle up.
3. Screen-by-Screen Breakdown
Screen 1: Order Confirmation (Feature Entry Point)
- Goal: Introduce the feature immediately after order placement without obscuring tracking.

Screen 2: Contact Selection
- Goal: Allow quick, low-effort selection of group members.

Screen 3: Bill Distribution & Settlement
- Goal: Provide flexible splitting (Equal vs. Custom) with transparent calculations.

4. Edge Cases & UX Guardrails