System Requirements Document for Gilded-QuickCart

1. Introduction

Gilded-QuickCart is a hyperlocal delivery application designed to streamline the ordering process for customers by integrating grocery and restaurant ordering into a single, efficient platform. The MVP focuses on delivering an end-to-end customer experience, with vendor inventory and delivery logistics simulated using seed data and a state machine.

2. System Overview

2a. Product Interpretation and Delivery Boundary

Domain Descriptors:

• Hyperlocal Delivery: The app focuses on delivering items from nearby stores and restaurants quickly.
• Simulated Operations: Vendor inventory and delivery logistics are simulated to focus on customer experience.

What is being built:

• A customer-facing app that allows users to browse nearby stores/restaurants, order items, and track deliveries.
• Simulated backend processes for vendor and delivery operations.

Excluded Assumptions:

• Real-time rider matching
• Multi-vendor cart splitting

Access:

• Application-owned identity with authentication required for customer and admin roles.

Behavior Contracts:

• Browse and Search Vendors: Customers can search for vendors, resulting in a list of nearby vendors.
• Add Items to Cart: Customers can add selected items to their cart.
• Checkout and Mock Payment: Customers proceed to checkout, select address, and confirm order.
• Track Order Status: Customers can view live order status updates.
• Manage Vendor and Order Data: Admins can update vendor and order data.

2b. Source Content Inventory

No explicit content sources were provided.

2c. Page Content and Component Coverage

Home Page:

• Displays nearby vendors sorted by distance/ETA.
• Includes search functionality and category filters.

Authentication Page:

• Facilitates login via phone/email and OTP.

Vendor Detail Page:

• Displays vendor/store details, menu/catalog, and allows item selection.

Checkout Page:

• Allows review of cart, address selection, and order confirmation.

Order Tracking Page:

• Displays live order status and ETA.

Admin Interface:

• Allows internal admin to seed vendors/products and progress order status.

3. Functional Requirements as Story Points

• As a Customer, I should be able to browse and search for vendors to find nearby stores and restaurants.
• As a Customer, I should be able to add items to my cart to prepare for checkout.
• As a Customer, I should be able to proceed to checkout, select an address, and confirm my order.
• As a Customer, I should be able to track my order status to know the delivery progress.
• As an Admin, I should be able to manage vendor and order data to ensure accurate information.

4. User Personas

• Customer: Primary user interacting with the app for ordering.
• Admin: Manages vendor and order data within the app.

5. Core User Flows

1. Onboarding → Location → Home: User opens app → grants/enters location → sees nearby vendors sorted by distance/ETA.
2. Discovery → Product → Cart: Browse vendor → view items → add to cart → view running cart total.
3. Checkout → Confirmation: Review cart → select address → confirm order.
4. Tracking: Order status auto-progresses with live ETA countdown.
5. Reorder: From order history, reorder previous cart in one tap.

6. Visuals Colors and Theme

• Primary: #FF6F61
• Primary Light: #FF8A80
• Secondary: #4CAF50
• Accent: #FFC107
• Highlight: #FFEB3B
• Background: #FFFFFF
• Surface: #F5F5F5
• Text: #212121
• Text Muted: #757575
• Border: #E0E0E0

7. Signature Design Concept

The Home page will feature a clean and intuitive layout with a focus on ease of navigation and quick access to vendor information. The design will incorporate a responsive header with product identity and navigation, and a compact footer with product context. The use of vibrant colors and clear typography will enhance user engagement and readability.

8. Interaction Model & Motion Direction

The interaction model for the Home page will be animated, featuring moderate scroll-triggered reveals and hover transitions. This will provide a polished experience while maintaining clarity and usability.

9. Non-Functional Requirements

• Performance: Home screen loads in under 2 seconds on 4G.
• Reliability: Cart state persists across app restarts.
• Security: Auth tokens, no plaintext payment data stored.
• Accessibility: Legible font sizes, sufficient tap targets, color contrast for status indicators.

10. Tech Stack

• Frontend: React Native
• Backend/DB: Supabase (Postgres + Realtime + Auth)
• Realtime Tracking: Supabase Realtime channels
• Maps: Google Maps SDK
• Auth: Supabase Auth (phone OTP)
• Hosting: Vercel/Netlify for web

11. Assumptions and Constraints

• The MVP will focus on customer-facing functionalities with simulated vendor and delivery operations.
• Real-time rider matching and multi-vendor cart splitting are not included in the MVP.

12. Glossary

• MVP: Minimum Viable Product
• ETA: Estimated Time of Arrival
• OTP: One-Time Password
• UI: User Interface
• UX: User Experience

This document outlines the system requirements for the Gilded-QuickCart project, focusing on delivering a seamless customer experience for hyperlocal delivery.