fdroidclient VS tivi

f-droid

Play Store → Aurora Store, Fdroid, Neo Store

Here is my pick: -aurora store download apk of apps from the googleplay store. -fdroid a store for opensource apps. -aria2 to use as an advance feature rich download manager and can use to torrent. -package manager is good for when installing apkm and exporting things. -sd maid to clean unwanted folders and dead files, generally clean the phone's storage. -pdf converter might be the best app to work with pdfs. -open resources read and download books for free, also they have an audio book app too. -mindustrycool game that i like, just recommending. -vlc an ad and hassle free audio-video player. -zee archiver another choice to zarchiver. -data eraser cb phones don't really need tools like this and using without understanding is harmful to the phone. -ocr ad free and opensource ocr app. -multi filerename does what it's name says. -stealth feature rich reddit client, can be found in fdroid. -fritter twitter client. newpipe feature rich no ad youtube client. -droid splitter splits files, can be buggy sometimes but does it's job. -onlyoffice-collabora microsoft office alternative. -binary eye qr code scanner. -video transcoder transcode video. -open link with cool link tool. -touch protecter protect from accidental touches when you don't want them. -fake stand by kinda like the one above but this one saves energy. -proexpense advance miney manager. Welp thats some of my pick and sorry for the lack of upper caped characters.

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.