quickie
compose-navigation-reimagined
| quickie | compose-navigation-reimagined | |
|---|---|---|
| 5 | 17 | |
| 351 | 526 | |
| - | - | |
| 7.4 | 7.4 | |
| 1 day ago | 3 months ago | |
| Kotlin | Kotlin | |
| MIT License | MIT License |
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.
quickie
-
Learning Android Camera stack
here are some nice resources: https://github.com/G00fY2/quickie
-
QR scanner library
I use latest CameraX with ML Kit for my small QR scanning library: https://github.com/G00fY2/quickie
-
Introducing quickie: QR code scanning library based on CameraX and ML Kit
Currently only QR codes are support. But you can follow this issue: https://github.com/G00fY2/quickie/issues/5
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
What are some alternatives?
AR-Touch - 🔮 Obtain the power of touchless interaction with display screens
voyager - 🛸 A pragmatic navigation library for Jetpack Compose
chucker - 🔎 An HTTP inspector for Android & OkHTTP (like Charles but on device)
Appyx - Model-driven navigation + UI components with gesture control for Compose Multiplatform
Leku - :earth_africa: Map location picker component for Android. Based on Google Maps. An alternative to Google Place Picker.
Cicerone - 🚦 Cicerone is a lightweight library that makes the navigation in an Android app easy.
Alligator - Alligator is Android navigation library that will help to organize your navigation code in clean and testable way.
Bubble Navigation - 🎉 [Android Library] A light-weight library to easily make beautiful Navigation Bar with ton of 🎨 customization option.
Fragula - 🧛 Fragula is a swipe-to-dismiss extension for navigation component library for Android
compose-destinations - Annotation processing library for type-safe Jetpack Compose navigation with no boilerplate.
BubbleTabBar - BubbleTabBar is a bottom navigation bar with customizable bubble-like tabs
Debug-Artist - Debug menu for happy android dev