Skip to content

Using database instead of preferences #500

@OmniCoder7

Description

@OmniCoder7

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.

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions