shanmukht9/nike-ecommerce

Purpose and Entry Points

This is a Flutter client for a Nike-style ecommerce flow: introductory landing, product browsing, cart management, and bottom-tab navigation. The Dart application starts at lib/main.dart; platform launchers embed the Flutter runtime on Android, iOS, desktop, and web.

Application Composition

lib/main.dart establishes the widget tree and application-level state wiring. Screen-level flow is separated into:

• Intro/landing: lib/pages/intro_page.dart

• Main shell/home navigation: lib/pages/home_page.dart

• Product catalog: lib/pages/shop_page.dart

• Cart view: lib/pages/cart_page.dart

The likely primary transition is intro → home shell, then tab-driven switching between shop and cart.

Domain State Boundary

The cart is the central mutable domain model in lib/models/cart.dart; products are represented by lib/models/shoe.dart. Product data and cart mutations should remain behind this model boundary rather than be duplicated in page widgets. UI consumes shoe records, adds/removes them through cart state, and renders the resulting collection.

Presentation Components

Reusable widgets isolate repeated ecommerce UI from page orchestration:

• Catalog/product card: lib/components/shoe_tile.dart

• Cart line item: lib/components/cart_item.dart

• Application navigation: lib/components/bottom_nav_bar.dart

Pages compose these components around model data. This creates a clear boundary between route/tab ownership, reusable rendering, and domain state.

Primary Data and Control Flow

1. lib/main.dart launches Flutter and supplies the app/root state.

2. lib/pages/intro_page.dart initiates entry into the shopping experience.

3. lib/pages/home_page.dart owns selected navigation state and chooses the active content page.

4. lib/pages/shop_page.dart reads available Shoe data and requests cart additions.

5. lib/models/cart.dart updates cart contents and notifies dependent UI through the project’s Flutter state-management mechanism.

6. lib/pages/cart_page.dart renders cart state with lib/components/cart_item.dart; navigation remains controlled by the home shell and lib/components/bottom_nav_bar.dart.

Runtime and Platform Infrastructure

Flutter/Dart is the application runtime, declared through pubspec.yaml. Native host projects package the same Dart UI for Android (android/app/src/main/kotlin/com/example/nike_ecommerce/MainActivity.kt), iOS (ios/Runner/AppDelegate.swift), macOS, Linux, Windows, and web (web/index.html). The tree contains no evidence of a backend, payment processor, authentication provider, remote API, or persistence service; catalog and cart behavior appear client-local.

Assets and Delivery Boundaries

Application image assets are expected under lib/images, while platform-specific icons, splash/launch configuration, signing/build behavior, and host lifecycle remain in native project directories. Android Gradle configuration begins at android/app/build.gradle.kts; iOS packaging is represented by ios/Runner.xcodeproj. These hosts should not contain business or presentation logic except platform integration requirements.