Problem
The project currently defines the high-level goals and architecture direction for the GovTech learning app, but a standardized scalable frontend structure for the React Native application has not yet been proposed.
Since the application is expected to support:
LMS integration
offline-first sync systems
AI Tutor WebSocket flows
white-label deployments
modular partner integrations
having a clean and scalable mobile app foundation early will help future contributors work more efficiently and maintain consistency across modules.
Proposed Solution
I would like to contribute by creating an initial scalable React Native app foundation including:
modular folder structure
environment configuration setup
API configuration layer
reusable constants and utilities structure
TypeScript path aliases
centralized configuration management
starter architecture documentation
Example structure:
src/
├── api/
├── components/
├── config/
├── constants/
├── hooks/
├── navigation/
├── screens/
├── services/
├── store/
├── theme/
├── utils/
Expected Benefits
improves maintainability for future contributors
creates a cleaner onboarding experience
supports scalable feature development
reduces architecture inconsistencies
prepares the codebase for offline sync and modular deployments
I would love to work on this issue under mentor guidance.
Thank you!
— Rishabh Mishra
Problem
The project currently defines the high-level goals and architecture direction for the GovTech learning app, but a standardized scalable frontend structure for the React Native application has not yet been proposed.
Since the application is expected to support:
LMS integration
offline-first sync systems
AI Tutor WebSocket flows
white-label deployments
modular partner integrations
having a clean and scalable mobile app foundation early will help future contributors work more efficiently and maintain consistency across modules.
Proposed Solution
I would like to contribute by creating an initial scalable React Native app foundation including:
modular folder structure
environment configuration setup
API configuration layer
reusable constants and utilities structure
TypeScript path aliases
centralized configuration management
starter architecture documentation
Example structure:
src/
├── api/
├── components/
├── config/
├── constants/
├── hooks/
├── navigation/
├── screens/
├── services/
├── store/
├── theme/
├── utils/
Expected Benefits
improves maintainability for future contributors
creates a cleaner onboarding experience
supports scalable feature development
reduces architecture inconsistencies
prepares the codebase for offline sync and modular deployments
I would love to work on this issue under mentor guidance.
Thank you!
— Rishabh Mishra