compose-destinations
compose-samples
compose-destinations | compose-samples | |
---|---|---|
25 | 101 | |
3,061 | 18,824 | |
- | 1.4% | |
9.0 | 9.7 | |
6 days ago | 3 days ago | |
Kotlin | Kotlin | |
Apache License 2.0 | 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-destinations
- What do you use for compose navigation?
-
jetpack navigation(https://github.com/raamcosta/compose-destinations) with activity
This time is about navigation, when raamcosta ( https://github.com/raamcosta/compose-destinations) in jetpack compose
-
Compose only apps question
The biggest help of all by far was Compose Destinations. It takes away all the boilerplate of maintaining your routes. A simple way to not have to create all those routes yourself with placeholders etc, including deeplink patterns and all. It generates all of that for you in a typesafe way. Just check the basic example on GitHub or the dedicated documentation website.
-
How do you deal with complex nested navigation in Jetpack Compose?
Here is a great solution for navigation in compose. Actually this is what Google should have done in the first place https://github.com/raamcosta/compose-destinations
- New app: xml or compose?
-
Pure Compose Navigation
Compose destinations is another alternative: https://github.com/raamcosta/compose-destinations
-
A Type-safe extension library for the Compose Navigation library
Hey, thanks for sharing here. Do you mind sharing how exactly this library is different from this one https://github.com/raamcosta/compose-destinations and why one would use one over the other?
-
Single Activity Apps: Fragments vs Views in 2022
I don't have much experience with conductor, so I'm curious what your concerns about lifecycle is lacking compared to fragments? But if your team already knows that framework I might just stick with views over fragments. I see there is a compose integration if you do ever plan on picking that up with conductor. Otherwise compose makes fragments obsolete and your team already knows conductor. I do agree the navigation story in compose is not mature especially after jetpack compose navigation. But there are other 3rd party libraries like compose destinations or decompose, but would be nice to see something better 1st party.
-
Which navigation library for compose do you suggest?
I can't recommend the vanilla compose navigation from Google, but the community has built others like compose destinations which is pretty good.
-
ViewModel: for UI business, not UI operations 😮
Compose Destinations
compose-samples
-
Jetpack Compose Mastery Part 2: Advanced Tools and Resources for Mastering Compose UI
The official documentation provides a comprehensive guide on the basics of Jetpack Compose, components, layouts, theming, and more advanced topics.
- Jetpack Compose UI App Development Toolkit
-
How the new Threads app is made
Apparently Jetpack Compose is an Android copy of SwiftUI?
https://developer.android.com/jetpack/compose
Only two HN threads with comments: https://hn.algolia.com/?q=jetpack+compose
-
Adaptive layouts in jetpack compose
If you want to take a look at code, we have the Jetnews sample app that support different screen sizes. And Jetcaster also implements features such as table top mode.
-
Customizable calendar for Jetpack Compose with option to add app specific dates etc.
check this out : https://github.com/android/compose-samples/tree/main/Crane
-
Seeking Guidance: How should I learn Android Dev
So I would say that instead if learning everything from Android SDK, you should just set a goal to create some app. Learn about Activities, their lifecycle, layouts (or Compose if you want to be more up to date). Try to implement your app based on this. Then improve your app using Fragments and their lifecycle. If you truly want to understand Views, which are essentially the building blocks of Android UI then I would recommend implementing your own custom View, which will have completely custom look - it is cool thing to try and you will learn how it all works inside.
-
New App structure/template to follow?
The compose samples by Google are a good reference to look into: https://github.com/android/compose-samples
-
Let's create notification reminder app in Jetpack Compose.
Basic understanding of Jetpack Compose.
-
Architecture Help
The compose-samples repo has a comprehensive list of samples ranging from low to complex projects which might be worth a look.
-
Android development beginner.
For instance, there is a link to this repository, that contains all sorts of samples, that are up to date and ready to use. That's cutting edge, which is a recommended start.
What are some alternatives?
voyager - 🛸 A pragmatic navigation library for Jetpack Compose
MPAndroidChart - A powerful 🚀 Android chart view / graph view library, supporting line- bar- pie- radar- bubble- and candlestick charts as well as scaling, panning and animations.
mapbox-navigation-android - Mapbox Navigation SDK for Android
filament - Filament is a real-time physically based rendering engine for Android, iOS, Windows, Linux, macOS, and WebGL2
Duo Navigation Drawer - A flexible, easy to use, unique drawer library for your Android project.
Flutter - Flutter makes it easy and fast to build beautiful apps for mobile and beyond
Chip Navigation Bar - An android navigation bar widget
MVICore - MVI framework with events, time-travel, and more
SlidingTutorial - Android Library for making animated tutorials inside your app
android-mvvm-dagger-rxjava-retrofit - A sample project which demostrate use of MVVM and Dagger 2 with RxJava2 along with Retrofit
Keyboard Dismisser - Dismiss your keyboard by tapping anywhere outside it.
Decompose - Kotlin Multiplatform lifecycle-aware business logic components (aka BLoCs) with routing (navigation) and pluggable UI (Jetpack Compose, SwiftUI, JS React, etc.)