-
GreenStash
Simple FOSS android app to help you plan and manage your savings goals easily and establish the habit of saving money.
I'm currently using SharedPrefs but there's problem with data types, for example someone who's not familiar with codebase may not know which keys store which type of data (strings, int, or boolean) without looking somewhere where that key is already used, i think overtime it'll become troublesome, that's why I'm planning to use something else which supports strong typing and can enforce static data types for keys when writing code instead of crashing in runtime like SharedPrefs
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
I have considered a few variants around this route. One easy way out would be just to launch a ComponentActivity with a PreferenceFragment like what Chris Banes does in TiVi ... but if you go with PreferenceFragment(Compat) it seems you are kinda stuck with SharedPreferences. If one attempts to supply DataStore wrapped in PreferenceDataStore, it seems types get messed up (TextPreference will store as a String, even if the InputType is number, etc).
-
Flixplorer
Jetpack Compose project showcasing Android MVVM guideline published on https://developer.android.com/topic/architecture#recommended-app-arch
If you're interested, you can check out my implementation on GitHub. Here's the GitHub repo link https://github.com/TheSomeshKumar/Flickophile/../ui/screens/settings/SettingsScren.kt
-
Build your own views/screens. Abandon (pre-made) fragments as soon as you can and you will be a happier developer. Follow the Compose+ViewModel+DataStore+Repository pattern like https://github.com/android/nowinandroid/tree/main/feature/settings/src/main/java/com/google/samples/apps/nowinandroid/feature/settings
