Note - Planning needed before implementation
Reason
The current project structure is inconsistent and loosely organized, which creates several challenges:
- Difficult navigation: Developers often rely on search to locate related components.
- Related classes (UI, models, services, utils) are scattered across different packages.
- New contributors struggle to understand where to place or find code.
- As features grow, the structure becomes harder to maintain and extend.
Suggested structure
Instead of grouping code by type (e.g., all models, all utils), we can organize the project by feature.
Each feature will contain its own:
- UI components
- Models
- Services
- Utilities
Note - Planning needed before implementation
Reason
The current project structure is inconsistent and loosely organized, which creates several challenges:
Suggested structure
Instead of grouping code by type (e.g., all models, all utils), we can organize the project by feature.
Each feature will contain its own: