compose-navigation-reimagined
ViewPropertyObjectAnimator
Our great sponsors
compose-navigation-reimagined | ViewPropertyObjectAnimator | |
---|---|---|
17 | 11 | |
524 | 338 | |
- | - | |
7.4 | 2.5 | |
3 months ago | 9 months ago | |
Kotlin | Java | |
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
ViewPropertyObjectAnimator
-
Am i safe by sticking with Java and XML for years ahead ?
I've been using https://github.com/blipinsk/ViewPropertyObjectAnimator and it's amazing
-
intuitive jetpack compose animations
you just use https://github.com/blipinsk/ViewPropertyObjectAnimator for everything, and if you need shared element transtiions you cry (then again, it's not like Compost can do that at all, so)
- Adding animation to recyclerView in an MVVM app requires a lot of boilerplate code
-
Why is Compose better than XML in your expirence? I'm preparing a post looking at TRUE benefits. Input appreciated.
Animations with views were much easier, you just had to use this lib https://github.com/blipinsk/ViewPropertyObjectAnimator and animator sets made it trivial. If you needed fancy crossfades then TransitionManager.beginDelayedTransition(container) and that's it.
-
What is actually the right way to make an android app?
Honestly, they're pretty even in that regard. Whether you use XML or Compose in "simple apps" is up to you. Some things are easier in Compose, and some things are just stupid tricky. Animations in Compose are the worst imo, with ViewPropertyObjectAnimator they used to be trivial for XML layouts.
-
4 reasons Jetpack Compose is better than XML
This is probably just my experience, but with Compose I have to muck around with LaunchedEffects and manual interpolation, while with XML views I could just use https://github.com/blipinsk/ViewPropertyObjectAnimator and AnimatorSet().playTogether().
-
Can someone review my coding assignment for a job? How valid is the feedback from the engineers who reviewed it?
That, and animations with https://github.com/blipinsk/ViewPropertyObjectAnimator were much easier than linear interpolating in a LaunchedEffect, and shadow support is basically non-existent (Modifier.shadow() doesn't work as you expect, even android:elevation was better).
-
Is it okay to set margin values ​to negative?
I like this library https://github.com/blipinsk/ViewPropertyObjectAnimator
-
What are the most underrated third party libraries for Native Android?
I don't know how to write animations without ViewPropertyObjectAnimator https://github.com/blipinsk/ViewPropertyObjectAnimator
-
Compose stable coming in July
Really? I just used https://github.com/blipinsk/ViewPropertyObjectAnimator + AnimatorSet for everything and it always just worked
What are some alternatives?
voyager - 🛸 A pragmatic navigation library for Jetpack Compose
ArcAnimator - ArcAnimator helps to create arc transition animation: 2.3.+
Appyx - Model-driven navigation + UI components with gesture control for Compose Multiplatform
AnimationEasingFunctions - Android Animation Easing Functions. Let's make animation more real!
Cicerone - 🚦 Cicerone is a lightweight library that makes the navigation in an Android app easy.
Lottie for Android, iOS, and React Native - Render After Effects animations natively on Android and iOS, Web, and React Native
Bubble Navigation - 🎉 [Android Library] A light-weight library to easily make beautiful Navigation Bar with ton of 🎨 customization option.
UltimateAndroidReference - :rocket: Ultimate Android Reference - Your Road to Become a Better Android Developer
Alligator - Alligator is Android navigation library that will help to organize your navigation code in clean and testable way.
CircleIndicator - A lightweight indicator like in nexus 5 launcher
Fragula - 🧛 Fragula is a swipe-to-dismiss extension for navigation component library for Android
AndroidViewAnimations - Cute view animation collection.