-
Notifications
You must be signed in to change notification settings - Fork 37
Open
Description
Overview
The mobile application currently exists as a separate project and needs to be integrated into the existing monorepo structure to improve development workflow, code sharing, and maintainability.
Motivation
Integrating the mobile app into the monorepo will provide several benefits:
- Unified Dependency Management: Share common dependencies and ensure version consistency across web and mobile platforms
- Code Sharing: Enable sharing of TypeScript types, utilities, and business logic between the mobile app and other packages
- Simplified Development: Streamline the development process with a single repository for all platform implementations
- Consistent Tooling: Use shared build tools, linting, and testing configurations across the entire codebase
- Atomic Changes: Make cross-platform changes in a single PR, ensuring consistency across web and mobile
Proposed Structure
The mobile app should be added under the apps/ directory alongside the existing API and web applications:
apps/
├── api/
├── web/
└── mobile/ # New mobile app directory
Implementation Considerations
- Preserve mobile app git history during migration
- Update CI/CD pipelines to include mobile builds
- Configure workspace dependencies for shared packages
- Update documentation to reflect the new structure
- Ensure mobile-specific tooling (React Native, Metro bundler) integrates smoothly with the monorepo setup
Next Steps
- Plan the migration strategy
- Set up the mobile app directory structure
- Configure build and development scripts
- Update CI/CD workflows
- Document the mobile development setup for contributors
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels