Mobile & Web Application Requirements

Project-Type Overview

CurryDash is a Flutter cross-platform application targeting iOS, Android, and Web from a single codebase. This approach maximizes code reuse while enabling platform-specific optimizations where needed.

Architecture Pattern: Feature-first clean architecture with GetX state management Codebase: Single Flutter codebase (lib/features/) serving all platforms Base: StackFood Multivendor (commercial solution) with CurryDash customizations

Platform Requirements

Mobile Platforms

Cross-Platform Framework: Flutter 3.4.4+ State Management: GetX with reactive controllers Navigation: GetX named routes (50+ routes defined)

Web Platform

Web Rendering: HTML renderer for broad compatibility PWA Support: Service worker enabled for offline capability Responsive: Mobile-first with desktop breakpoints

Device Permissions & Features

Web Equivalents:

• Geolocation API for address detection
• File upload for photo submission
• Web Push API for notifications (where supported)
• LocalStorage/IndexedDB for offline data

Offline Mode Strategy

Offline Capabilities:

• Browse cached restaurant/menu data
• View order history
• Access saved addresses and payment methods
• Queue orders for submission when online

Sync Strategy:

• Background sync when connectivity restored
• Conflict resolution: Server wins for order state
• Local-first for user preferences

Implementation: Drift database for local persistence, API queue for offline actions

Push Notification Strategy

Implementation: Firebase Cloud Messaging (FCM) Channels: Separate channels for orders vs marketing (Android) Permissions: Request at first order, not app launch

App Store Compliance

iOS App Store

• Apple Sign-In required (implemented)
• In-app purchase compliance for subscriptions
• Privacy nutrition labels configured
• App Tracking Transparency (ATT) for advertising

Google Play Store

• Google Sign-In supported
• Billing library for subscriptions
• Data safety section configured
• Target API level 34 compliance

Common Requirements

• Privacy policy URL
• Terms of service URL
• Age rating: 4+ (no objectionable content)
• Content guidelines compliance

Responsive Design

Breakpoints:

Implementation: ResponsiveHelper class in lib/helper/ Web-specific: Hover states via lib/common/widgets/hover_widgets/

Performance Targets

SEO Strategy (Web)

Focus Areas:

• Restaurant discovery pages (indexable)
• Menu/package pages (rich snippets)
• Location-based landing pages (local SEO)

Technical SEO:

• Server-side rendering for key pages (future)
• Meta tags per route
• Structured data for restaurants/menus
• Sitemap generation

Current: Client-side rendering (CSR) - SEO limited Future: Consider Flutter web SEO improvements or SSR gateway

Accessibility Level

Target: WCAG 2.1 AA compliance

Implementation:

• Semantic labels on all interactive elements
• Sufficient color contrast (4.5:1 minimum)
• Touch targets minimum 48x48dp
• Screen reader support (TalkBack/VoiceOver)
• Keyboard navigation (web)

Implementation Considerations

Platform-Specific Code Patterns:

if (ResponsiveHelper.isWeb()) {
  // Web-specific behavior
}
if (GetPlatform.isAndroid || GetPlatform.isIOS) {
  // Mobile-specific behavior
}

Feature Flags:

• Use conditional compilation for platform-specific features
• Firebase Remote Config for runtime feature toggles

Testing Strategy:

• Widget tests for UI components
• Integration tests per platform
• Playwright for web E2E
• Emulator testing for mobile