adding shared prefs to save the users name
This commit is contained in:
151
TODO.md
151
TODO.md
@@ -9,11 +9,27 @@
|
||||
- [x] Implement proper state management with LiveData/StateFlow
|
||||
- [x] Add ViewModelFactory if needed
|
||||
|
||||
### 1.2 Dependency Injection with Hilt
|
||||
- [ ] Add Hilt dependencies
|
||||
- [ ] Set up Hilt modules for WifiAwareManager
|
||||
- [ ] Convert singletons to proper DI
|
||||
- [ ] Inject ViewModels using Hilt
|
||||
### 1.2 Dependency Injection with Hilt ✅
|
||||
- [x] Add Hilt dependencies
|
||||
- [x] Set up Hilt modules for WifiAwareManager
|
||||
- [x] Convert singletons to proper DI
|
||||
- [x] Inject ViewModels using Hilt
|
||||
|
||||
### 1.3 Room Database Setup
|
||||
- [ ] Add Room dependencies
|
||||
- [ ] Create Message and User entities
|
||||
- [ ] Implement DAOs for data access
|
||||
- [ ] Create database migrations
|
||||
- [ ] Store messages in Room database
|
||||
- [ ] Load message history on app restart
|
||||
- [ ] Implement message sync logic
|
||||
|
||||
### 1.4 Coroutines & Flow Optimization
|
||||
- [ ] Convert callbacks to coroutines
|
||||
- [ ] Use Flow for reactive data streams
|
||||
- [ ] Implement proper scope management
|
||||
- [ ] Replace GlobalScope with proper lifecycle scopes
|
||||
- [ ] Add proper error handling with coroutines
|
||||
|
||||
## Phase 2: Core UX Improvements
|
||||
|
||||
@@ -29,19 +45,50 @@
|
||||
- [ ] Handle user join/leave events
|
||||
- [ ] Show user count in chat header
|
||||
|
||||
## Phase 3: Data Persistence
|
||||
### 2.3 Enhanced Messaging Features
|
||||
- [ ] Message status indicators (sent/delivered/read)
|
||||
- [ ] User presence indicators (online/offline/typing)
|
||||
- [ ] Message timestamps with proper formatting
|
||||
- [ ] Offline message queue
|
||||
- [ ] Message retry mechanism
|
||||
- [ ] Long press message actions (copy, delete)
|
||||
|
||||
### 3.1 Room Database Setup
|
||||
- [ ] Add Room dependencies
|
||||
- [ ] Create Message and User entities
|
||||
- [ ] Implement DAOs for data access
|
||||
- [ ] Create database migrations
|
||||
### 2.4 File & Media Sharing
|
||||
- [ ] Image sharing support
|
||||
- [ ] File transfer capability
|
||||
- [ ] Image preview in chat
|
||||
- [ ] Progress indicators for transfers
|
||||
- [ ] File size limits and validation
|
||||
|
||||
### 3.2 Message Persistence
|
||||
- [ ] Store messages in Room database
|
||||
- [ ] Load message history on app restart
|
||||
- [ ] Implement message sync logic
|
||||
- [ ] Add message timestamps
|
||||
## Phase 3: UI/UX Improvements
|
||||
|
||||
### 3.1 Material 3 Design Update
|
||||
- [ ] Migrate to Material 3 components
|
||||
- [ ] Implement dynamic color theming
|
||||
- [ ] Update typography and spacing
|
||||
- [ ] Add proper elevation and shadows
|
||||
- [ ] Implement Material You design principles
|
||||
|
||||
### 3.2 Dark Theme & Theming
|
||||
- [ ] Implement dark theme
|
||||
- [ ] Add theme toggle in settings
|
||||
- [ ] System theme detection
|
||||
- [ ] Custom color schemes
|
||||
- [ ] Persist theme preference
|
||||
|
||||
### 3.3 Animations & Polish
|
||||
- [ ] Message send/receive animations
|
||||
- [ ] Screen transition animations
|
||||
- [ ] Loading state animations
|
||||
- [ ] Smooth scrolling improvements
|
||||
- [ ] Haptic feedback
|
||||
|
||||
### 3.4 Better Error Handling UI
|
||||
- [ ] User-friendly error messages
|
||||
- [ ] Retry mechanisms with UI feedback
|
||||
- [ ] Connection lost/restored snackbars
|
||||
- [ ] Empty states for no messages/users
|
||||
- [ ] Inline error states
|
||||
|
||||
## Phase 4: Reliability Improvements
|
||||
|
||||
@@ -56,26 +103,78 @@
|
||||
- [ ] Handle app lifecycle properly
|
||||
- [ ] Save and restore connection state
|
||||
|
||||
## Phase 5: Advanced Features
|
||||
## Phase 5: Security & Privacy
|
||||
|
||||
### 5.1 Background Service
|
||||
### 5.1 Message Encryption
|
||||
- [ ] End-to-end encryption implementation
|
||||
- [ ] Key exchange protocol
|
||||
- [ ] Message integrity verification
|
||||
- [ ] Secure key storage
|
||||
- [ ] Forward secrecy
|
||||
|
||||
### 5.2 Privacy Features
|
||||
- [ ] Optional username anonymization
|
||||
- [ ] Message auto-deletion
|
||||
- [ ] Block/unblock users
|
||||
- [ ] Private rooms with passwords
|
||||
- [ ] Data export/import
|
||||
|
||||
## Phase 6: Advanced Features
|
||||
|
||||
### 6.1 Background Service
|
||||
- [ ] Create foreground service for persistent connection
|
||||
- [ ] Handle Doze mode and battery optimization
|
||||
- [ ] Add notification for active chat
|
||||
- [ ] Implement proper service lifecycle
|
||||
- [ ] Wake lock management
|
||||
|
||||
### 5.2 Additional Features
|
||||
- [ ] Message delivery status
|
||||
- [ ] Typing indicators
|
||||
- [ ] File/image sharing support
|
||||
- [ ] Message encryption improvements
|
||||
### 6.2 Settings & Preferences
|
||||
- [ ] Create settings screen
|
||||
- [ ] Notification preferences
|
||||
- [ ] Sound/vibration settings
|
||||
- [ ] Auto-reconnect toggle
|
||||
- [ ] Message history limits
|
||||
|
||||
## Phase 7: Testing & Quality
|
||||
|
||||
### 7.1 Unit Testing
|
||||
- [ ] Test ViewModels
|
||||
- [ ] Test Repository logic
|
||||
- [ ] Test data transformations
|
||||
- [ ] Test error scenarios
|
||||
- [ ] Mock dependencies with Hilt testing
|
||||
|
||||
### 7.2 Integration Testing
|
||||
- [ ] Test database operations
|
||||
- [ ] Test network layer
|
||||
- [ ] Test complete user flows
|
||||
- [ ] Test state persistence
|
||||
|
||||
### 7.3 UI Testing
|
||||
- [ ] Espresso tests for main flows
|
||||
- [ ] Test navigation
|
||||
- [ ] Test user interactions
|
||||
- [ ] Screenshot testing
|
||||
- [ ] Accessibility testing
|
||||
|
||||
## Current Status
|
||||
- ✅ Phase 1.1 - MVVM Architecture - COMPLETED
|
||||
- ✅ Phase 1.2 - Dependency Injection with Hilt - COMPLETED
|
||||
- ✅ Phase 2.1 - Connection Status Management - COMPLETED
|
||||
- 🚀 Next: Phase 1.2 (Dependency Injection) or Phase 3 (Data Persistence)
|
||||
- 🚀 Next Priority Options:
|
||||
- Phase 1.3 - Room Database (Foundation for persistence)
|
||||
- Phase 2.2 - User List Feature (Core UX)
|
||||
- Phase 2.3 - Enhanced Messaging (Better UX)
|
||||
- Phase 3.1 - Material 3 Update (Modern UI)
|
||||
|
||||
## Completed Work Summary
|
||||
1. **MVVM Architecture**: ViewModels, Repository pattern, proper separation of concerns
|
||||
2. **Connection Status**: Visual indicator with real-time updates, activity-based detection
|
||||
3. **Sleep/Wake Handling**: Auto-recovery when messages resume after device sleep
|
||||
2. **Dependency Injection**: Hilt integration with proper scoping and lifecycle management
|
||||
3. **Connection Status**: Visual indicator with real-time updates, activity-based detection
|
||||
4. **Sleep/Wake Handling**: Auto-recovery when messages resume after device sleep
|
||||
|
||||
## Development Notes
|
||||
- Architecture foundation (Phase 1) should be completed before moving to advanced features
|
||||
- UI/UX improvements (Phase 3) can be done in parallel with feature development
|
||||
- Testing (Phase 7) should be implemented incrementally as features are added
|
||||
- Security features (Phase 5) are important for production readiness
|
||||
Reference in New Issue
Block a user