How aryabandhu/chargeq works
Project type and purpose
• This is a cross-platform mobile application built with Expo (React Native).
• The JavaScript “app” directory holds file-based routes (screens): index.jsx, bookings.jsx, profile.jsx, scanqr.jsx, wallet.jsx.
• The “android” folder is the native-code scaffold produced by Expo prebuild (Kotlin/Gradle).
File structure
Top-level:
• package.json, tsconfig.json → Node.js/TypeScript config
• app.json → Expo configuration
• app/ → React Native screens (file-based routing)
• assets/ → fonts & images usage at runtime
• android/ → native Android project (Gradle, Kotlin)
• (No explicit ios/ folder, managed by Expo under the hood)
Key technologies & build steps
• Expo CLI & Metro bundler (JS packaging)
• React Native JS runtime + JavaScriptCore (on device)
• Native modules via the React Native bridge (e.g., Camera, QR scanner)
• Android build: Gradle → APK/AAB; Kotlin code (MainActivity.kt, MainApplication.kt)
Main components
A. Developer Environment
– Node.js/NPM, Expo CLI, Metro Bundler
B. Source Code & Assets
– JS entry point (app/index.jsx)
– File-based router (screens in “app/”)
– Assets (images, fonts)
C. Build & Packaging
– Metro Bundler → JS bundle (.jsbundle)
– Expo native modules packaging
– Android Gradle build pipeline
D. Target Runtimes
– Android device/emulator (JavaScriptCore + Native Modules)
– (Optionally iOS simulator/device via Expo)
E. External Services (placeholder)
– REST/GraphQL backend
– 3rd-party SDKs (e.g., authentication, analytics)
F. Native Modules / Hardware
– Camera & QR Scanner bridge
– Secure storage / AsyncStorage
– Device sensors/APIs
Relationships & Data Flows
– Developer → Expo CLI → Metro Bundler → Produces JS bundle
– JS bundle + Native modules packaged by Gradle → Installed on device
– On device: UI screens ↔(React Native Bridge)↔ Native modules & hardware
– JS screens ↔(fetch/XHR)↔ External backend services
Architectural patterns & principles
– File-based routing organizes screens as individual components
– Separation of concerns:
• Presentation layer (React components in “app/”)
• Asset management (“assets/”)
• Native bridge modules (expo packages, Android code)
– Modularization: group related screens, assets, native code