muhammadumar55/punjab-electric-bus-routes

Purpose and Runtime

A static React/Vite landing site promoting a Punjab electric-bus-routes Android application. It is a client-only marketing/download experience; the APK is bundled as a public asset. Development runs through Vite (vite.config.ts), with no backend, database, or external service evident.

Application Entry and Composition

src/main.tsx mounts the React application into index.html. src/app/App.tsx is the page-level composition root, assembling the landing-page sections in a single scrolling experience.

Landing-Page Flow

The primary user journey proceeds through content sections:

• Navigation and page anchors: src/app/components/Header.tsx

• Product introduction and primary call to action: src/app/components/Hero.tsx

• Value proposition and usage explanation: src/app/components/Features.tsx, src/app/components/HowItWorks.tsx

• Social/proof and visual product material: src/app/components/Stats.tsx, src/app/components/Screenshots.tsx

• App acquisition and site closure: src/app/components/DownloadSection.tsx, src/app/components/Footer.tsx

Control flow is predominantly presentational: section CTAs and navigation guide users to in-page content or the download asset rather than invoking application APIs.

Download Boundary

The distributable mobile application is served directly from Vite’s public directory at public/assets/punjab_electric_bus_routes.apk. src/app/components/DownloadSection.tsx is the architectural boundary between the web landing experience and installation of the separate Android app.

UI System

The project uses a local reusable component library under src/app/components/ui, including foundational controls such as button.tsx, card.tsx, and accordion.tsx. Page sections consume these primitives rather than implementing all interaction and styling independently. src/app/components/figma/ImageWithFallback.tsx provides resilient image rendering for design-exported imagery.

Styling and Assets

Global visual behavior is layered through src/styles/index.css, src/styles/tailwind.css, and src/styles/theme.css, with font declarations in src/styles/fonts.css. default_shadcn_theme.css indicates a shadcn-oriented design-token baseline. Static deliverables and other browser-served assets belong under public/.

Material Boundaries

The browser hosts all rendered content and client interactions. Vite provides local development/build integration; React and the local UI layer provide rendering. There are no visible server endpoints, authentication flows, persistence layers, analytics integrations, or remote data dependencies in the repository structure.