How sonic-sabers/jet-set-go works
Main Components
• Mobile UI Layer (React Native):
• Screens and Components: Represent each of the main UI components described (Splash Screen, Home Screen, Flight Filter Screen, Modal Filter, Flight Details, Flight Seating, Cost Breakup).
• Assets: Include the Screen-ui folder that holds images and other UI resources.
• Navigation & State Management (if in use): Although not explicitly mentioned, you might add a module for managing navigation (using libraries like React Navigation) and any state management (Redux or Context API) if present.
• JavaScript Core & Bundler:
• Metro Bundler: Illustrate it as the process that bundles and serves the JavaScript code to the mobile environments.
• Main Files: Mention key entry points such as App.tsx, index.js, and babel.config.js.
• Native Platforms:
• Android:
• Android Project Structure: Highlight the “android” folder, Gradle build files (build.gradle, gradle.properties, settings.gradle), and the generated build outputs. This shows how the JavaScript bundle and native code (e.g., MainActivity.java, MainApplication.java) integrate.
• iOS:
• iOS Project Structure: Show the “ios” folder including the Xcode project, AppDelegate, main.m, and resource files like Info.plist and launch storyboards.
• Development & Tooling:
• Testing: Reference the __tests__ folder that contains test files for components.
• Code Quality: Include configuration files such as .eslintrc.js and .prettierrc.js.
• Environment & Build Scripts: Note files such as .env, app.json, and others that support environment configuration and building.
Relationships and Data Flow
• That the Mobile UI layer (React components) communicates with the Metro Bundler for code updates and hot reloads.
• Connections between the assets (in Screen-ui) and the display components in the UI layer.
• Optionally, if there is any asynchronous data fetching (for live flight information) or local storage handling, indicate these interactions as separate services or modules.
Architectural Patterns and Design Principles
• Separation of Concerns: Emphasize the separation between the presentation layer (React components) and native build layers (Android/iOS).
• Cross-Platform Code Reuse: Note that the majority of the application logic is developed in JavaScript using React Native, while each platform contains a native “shell” to host the JavaScript bundle.
• Build and Deployment Pipeline: Optionally, include a small segment that shows the build commands (npm run android / ios) feeding the metro bundler and then into the respective native build tools (Gradle for Android and Xcode for iOS).
Relevant Technologies, Frameworks, and Libraries
• React Native – for the core UI and app logic.
• Metro Bundler – for JavaScript bundling.
• Gradle and Xcode – for building native binaries on Android and iOS respectively.
• Node.js and npm/Yarn – for dependency and script management.
• Optional Testing Frameworks – Jest (indicated by jest.config.js) and React Native testing libraries.