clementwzk / clementwzk/OpenCalc
Using database instead of preferences
Open
enhancement
good first issue
- Dominant language
- Kotlin
- Stars
- 1.5k
- Forks
- 186
- PR merge metrics
- No merged PRs in 30d
Description
Large History Storage
1) Store 100+ calculations
2) Persist across app restarts
3) Efficient querying of past calculations
Performance Benefits
1) Faster than SharedPreferences for multiple entries
2) Better memory management
3) Background thread support for data operations
Common source of data. Using Viewmodel and Flows for reactive programming.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.