How vishalkasa23/hellodot works
Project type and purpose
• From the file tree and minimal README, HelloDot is a cross-platform mobile application built with React Native.
• It targets iOS and Android (presence of ios/, android/), uses Metro bundler, and implements React Native’s new architecture (TurboModules, JSI, C++ components).
• The JS code under src/ implements UI screens, navigation (Drawer), form validation, and API calls (src/api/auth-api.js) to remote authentication endpoints.
File structure
• Top-level:
• android/ – Android Studio project, Gradle config, native Java modules, JNI C++ code for TurboModules.
• ios/ – Xcode project, CocoaPods (Podfile), Obj-C/Swift entrypoint, unit tests.
• src/ – Pure JS: components, screens, assets, API layer, helpers, theming, drawer navigation.
• Config files: babel.config.js, metro.config.js, linter/prettier, .buckconfig, Ruby/Gemfile (for iOS CocoaPods).
• Entrypoints: index.js, App.js, package.json – defines scripts & dependencies.
README for additional insights
• The README only gives the project name; no embedded architecture details. All insights come from the file tree.
a. Main components:
• JavaScript Layer (React Native app):
– UI Screens (Login, Register, Dashboard, etc.)
– Navigation Layer (Drawer)
– Business Logic & Validation Helpers
– API Client (auth-api.js)
• Metro Bundler & JS Engine (e.g., Hermes)
• React Native Bridge & JSI Host
• Native Layer:
– Android (Java) & iOS (Obj-C/Swift) App entrypoints
– TurboModules & C++ Components Registry (JNI/CMake)
• External Services:
– Authentication REST API (external server)
• Device OS & Hardware
b. Relationships & Interactions:
1. Developer invokes metro bundler (local machine) → bundles JS.
2. index.js / App.js loads bundle into JS engine (Hermes) on device or emulator.
3. JS code invokes React Native Bridge / JSI to call native modules (e.g., custom C++ TurboModules).
4. UI rendering requests flow from JS to the native UI Manager → platform widgets (Android Views or iOS UIView).
5. JS API client issues HTTP(S) requests over network to external Auth API → processes responses.
6. Native modules (Flipper on debug build) communicate back to debugging tools.
c. Architectural Patterns & Principles:
• Modular JS code: separation between UI, navigation, API, and validation
• React Native New Architecture: JSI + TurboModules for high-performance native integration
• Platform abstraction: a single JS codebase with platform-specific native overrides
• Unidirectional data flow: from JS → native → UI, and from network → JS state
d. Key Technologies, Frameworks & Libraries:
• React Native (CLI-managed)
• Metro bundler
• Hermes JS engine (or V8, dependent on config)
• TurboModules & JSI (C++ & JNI for Android, Obj-C++ for iOS)
• Android Gradle & Xcode build systems
• Babel, ESLint, Prettier
• CocoaPods (iOS)
Critical Details to Capture
• The separation of concerns between JS and native layers.
• The bidirectional nature of the React Native bridge / JSI host.
• The role of TurboModules (native C++ components) under the new architecture.
• The external API dependency and network flow.
• Platform-specific build & debug tooling (Gradle, CocoaPods, Flipper).