Current Stage
Early MVP Development
The core architecture and base CRUD functionality are already implemented. We are now working towards completing the MVP feature set.
Completed Features
Core Architecture
- Clean Architecture structure
- Domain / Application / Infrastructure / Presentation separation
- Type-safe entities and interfaces
Database
- SQLite local database
- Table:
records
- UUID-based identifiers
- Soft delete support
Records Module
- ✓ Create record
- ✓ Edit record
- ✓ Soft delete record
- ✓ List records
Validation
- ✓ Title normalization
- ✓ Duplicate prevention
- ✓ Minimum length validation (3 characters)
- ✓ Maximum length validation (50 characters)
User Experience
- ✓ Global Toast Notification System
- ✓ Toast animations
- ✓ Basic mobile-first UI
MVP Features Remaining
Records UX
UI Improvements
Data Management
Architecture
Persistence Safety
The MVP focuses on making the core Records module feature-complete before adding new modules.
Post-MVP Features (Future)
These features will be developed after the MVP is complete:
New Modules
- Appointments system
- Services system
Integrations
- Calendar integration
- Local notifications
Sync & Storage
- Offline synchronization
- Cloud sync option
- Multi-device support
Authentication
- User authentication (future optional backend)
Post-MVP features are not scheduled yet. Focus remains on completing the MVP first.
Long Term Vision
Simple Manager aims to be a lightweight offline-first management tool for small businesses and freelancers.
Core Principles
The application should remain:
- Simple - Easy to use without a learning curve
- Fast - Instant response with local-first architecture
- Private - Data stays on the device by default
- Offline-first - Works without internet connection
Every feature should align with these principles. If a feature compromises simplicity or privacy, it should be optional.
Technical Debt
No significant technical debt at this stage. The architecture is clean and maintainable.
Contributing
When working on features:
- Check this roadmap to understand priorities
- Follow the Development Rules
- Apply Best Practices
- Update this roadmap when completing features
Timeline
No fixed timeline. Features are developed as resources allow.
- Fully tested
- Well documented
- Properly integrated
- Following architecture rules