## 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 <img width="397" height="508" alt="Image" src="https://github.com/user-attachments/assets/be85878f-5666-4cb7-b5c5-2bd212f84277" />
Activity
alperozturk96 commentedon Apr 24, 2026
1 - #16907