compose-navigation-reimagined
tivi
compose-navigation-reimagined | tivi | |
---|---|---|
17 | 28 | |
526 | 6,435 | |
- | - | |
7.4 | 9.7 | |
4 months ago | about 13 hours ago | |
Kotlin | Kotlin | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
compose-navigation-reimagined
-
Are Fragments in Android going to be deprecated in favor of Jetpack Compose?
Navigation Reimagined https://github.com/olshevski/compose-navigation-reimagined
- What do you use for compose navigation?
-
Compose Navigation Reimagined 1.4.0 released
Look at how deeplinks are converted into destinations/backstack here: https://github.com/olshevski/compose-navigation-reimagined/blob/main/sample/src/main/kotlin/dev/olshevski/navigation/reimagined/sample/ui/MainScreen.kt. It is all manual in comparison to the official Navigation Component, but I feel it gives developers much more control on the deeplink handling.
-
ViewModel: for UI business, not UI operations 😮
Compose navigation reimagined
-
4 reasons Jetpack Compose is better than XML
Using any of the 5 prominent community alternatives is a better approach (even though most people hoping to use the docs as if it was like, written for stable code, will muck around with their apps crashing if the user inputs a & symbol). I have this thing but I'd consider taking a look at https://github.com/adrielcafe/voyager or maybe https://github.com/olshevski/compose-navigation-reimagined
- Will Jetpack Compose Take Over XML?
-
Why using Navigation-Compose in your Jetpack Compose app is a bad idea
Also, I'll just leave it here: https://github.com/olshevski/compose-navigation-reimagined
- Show HN: Compose Navigation Reimagined – open-source library for Android
- Compose Navigation Reimagined
tivi
-
Do you have an open source (base) project using latest tech?
Look no more: https://github.com/chrisbanes/tivi
- What are some open source android projects that you can go to see Best practices or how they implemented stuff
-
What do you use for compose navigation?
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.
-
What's modern approach to handling Preferences (UI & Storage) in Compose?
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).
-
Modern ways to expose Retrofit network progress and errors to a ViewModel?
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
-
"outdated senior" needs your advice
I would read and study nowinandroid and tivi apps.
-
Compose Navigation with multiple graphs
Check out the approach from tivi https://github.com/chrisbanes/tivi/blob/main/app/src/main/java/app/tivi/AppNavigation.kt as an idea.
- Any Clean Architecture app courses that make use of Flows completely without LiveData?
- What resources would you recommend for learning how to build Multi-Module android apps?
-
Anyone here who has bought Philipp Lackner's course for developing multi-module apps?
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.
What are some alternatives?
voyager - 🛸 A pragmatic navigation library for Jetpack Compose
compose-samples - Official Jetpack Compose samples.
Appyx - Model-driven navigation + UI components with gesture control for Compose Multiplatform
android-mvvm-dagger-rxjava-retrofit - A sample project which demostrate use of MVVM and Dagger 2 with RxJava2 along with Retrofit
Cicerone - 🚦 Cicerone is a lightweight library that makes the navigation in an Android app easy.
gamedge - An Android application for browsing video games and checking the latest gaming news from around the world.
Alligator - Alligator is Android navigation library that will help to organize your navigation code in clean and testable way.
architecture-components-samples - Samples for Android Architecture Components.
Bubble Navigation - 🎉 [Android Library] A light-weight library to easily make beautiful Navigation Bar with ton of 🎨 customization option.
android-showcase - 💎 Android application following best practices: Kotlin, Coroutines, JetPack, Clean Architecture, Feature Modules, Tests, MVVM, DI, Static Analysis...
Fragula - 🧛 Fragula is a swipe-to-dismiss extension for navigation component library for Android
fdroidclient - Android client application.