GreenStash VS tivi

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

Myne has pretty aesthetic and unique UI (i guess?), while GreenStash has very nice adobe after effects animations all of the place, check them up, maybe you'll like it :)

GreenStash (version 20): Simple app to help you plan and manage your savings goals easily.

Source Code (GitHub)

Google Play Store | Source Code

greenstash

Green Stash -manage savings

Hello there! I'm an android devloper from India who is interested in working on free and open source android apps. From past few days I've been looking for some app ideas since I'm pretty bored and wanna work on some useful and cool projects to improve my android devlopment skills, gain some experience and contribute towards the FOSS community at the same time. If you got something on your mind feel free to drop it down in comments. For those who are interested you can take a look at my another app which I've posted here a while ago. Cheers 🙌

Look no more: https://github.com/chrisbanes/tivi

It's definitely the most verbose part of our app and one of the weakest parts of the Jetpack library. We used https://github.com/chrisbanes/tivi for some inspiration on how to organize your navigation structures.

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).

Thanks I think what's confusing is that UI events are recommended to be modeled as Flows, which I guess is why Tivi uses Flows for even the simplest actions, but it does a lot of very fancy things. Most repository interactions seem to have an entire class extending an Interactor (e.g.) which catches and emits errors, progress and handles timeouts and does all that crazy queuing stuff with UI "messages" Flow

I would read and study nowinandroid and tivi apps.

Check out the approach from tivi https://github.com/chrisbanes/tivi/blob/main/app/src/main/java/app/tivi/AppNavigation.kt as an idea.

They probably want you to do a module split like in https://github.com/chrisbanes/tivi or https://github.com/igorwojda/android-showcase, but what they probably don't realize is that modularization is a trade-off, namely greatly increased build configuration complexity for... well, having modules.