pocket-casts-android VS tivi

https://github.com/Automattic/pocket-casts-android/releases/tag/7.47-rc-2 their was upnext bug that broke multiselect in 7.46 which is why the app is lagging, it should be fixed in 7.47 it is at least for me 🤔

Hmmmmm don't have a telegram, could you add a comment to this thread 🤔 😉 https://github.com/Automattic/pocket-casts-android/pull/997

Here's the PR: https://github.com/Automattic/pocket-casts-android/pull/997

https://github.com/Automattic/pocket-casts-android/pull/900 should be fixed in the next beta 😉

You can get a slight sneak peak from github 😀

I am not very familiar with GitHub. Would this be the correct place to add the feature request? https://github.com/Automattic/pocket-casts-android/issues

If your on the latest Android alpha it might be their but theirs a chance it's only accessable via development tools currently 🤔🤔 https://github.com/Automattic/pocket-casts-android/issues/825

Yep, been using PocketCasts and it is pretty good.

Recently they made their apps opensource as well.

https://github.com/Automattic/pocket-casts-android

https://github.com/Automattic/pocket-casts-ios

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.