How yangsaiyan/dsid_mobile_application_reactnative works
Project Type and Purpose
• This is a cross-platform mobile app built on Expo (React Native + TypeScript)
• Uses file-based routing (app folder) and React Navigation (bottom tabs, stack)
• Focused purely on client-side UI/UX, camera/QR features, user profiles, theming
File Structure
Top-level layout:
• app/ – file-based routes, layouts, navigation setup
• components/ – reusable UI components, subdivided by feature (profile, qr, student_verification) and by generic UI
• assets/ – images and fonts
• constants/, utils/ – shared values and config
• scripts/ – dev utilities (e.g. reset-project)
• Config files (app.config.js, tsconfig.json, eas.json) and package manifests
README
• Confirms Expo CLI workflow, file-based routing
• No back end in repo (pure-client)
• Encourages using Expo Go, emulators, dev builds
Main System Components
A. App Shell & Routing
• Entry point → _layout.tsx + AppNavigator.tsx → BottomTabNavigator.tsx
B. Screens (Features)
• HomeScreen, LoginScreen, ProfileScreen, QRScreen
C. UI Component Library
• Generic components (Collapsible, ThemedText, ParallaxScrollView, etc.)
• Feature-specific components (ProfileCard, QRGenerator, QRScanner, StudentVerification)
D. Cross-cutting Utilities
• Theme hooks (useColorScheme, useThemeColor)
E. Assets Layer
• Fonts, images (static resources)
F. External / Native Services
• Expo modules (Camera, SecureStore, Linking, Haptics)
• QR code library APIs (Scanner / Generator)
• Optional network API endpoints (if your app will call a server)
Relationships & Data Flows
• User taps tab → Navigation layer routes to Screen component
• Screen invokes feature components → UI components
• UI components call hooks/utilities for theming and config
• Feature components (e.g. QRScanner) invoke native Expo APIs (Camera)
• Any network call flows: Screen → utils/config → fetch → remote API
Architectural Patterns
• Feature-based modular structure
• Unidirectional data flow: navigator → screen → component → service
• Separation of concerns between Presentation (components), Routing (navigation), and Utilities
Essential Details to Capture
• Entry point → layout → navigator → screen hierarchy
• Reusable vs. feature components
• Theming and configuration layer
• Native device & Expo services