clementwzk/OpenCalc

Using database instead of preferences

Open

#500 opened on Dec 6, 2024

View on GitHub
 (5 comments) (1 reaction) (1 assignee)Kotlin (182 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (1,480 stars)
PR merge metrics
 (PR metrics pending)

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

Research direction
Study the existing SharedPreferences implementation for storing calculation history. Then implement Room database with entities, DAO, and repository pattern. Connect to ViewModel using Kotlin Flows for reactive updates. Ensure background thread handling with coroutines.
Tech stack
kotlinandroid
Domain
mobile
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
KotlinAndroid
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55