ViewPropertyObjectAnimator
simple-stack-compose-integration
ViewPropertyObjectAnimator | simple-stack-compose-integration | |
---|---|---|
11 | 21 | |
338 | 102 | |
- | - | |
2.5 | 6.3 | |
10 months ago | 9 months ago | |
Java | 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.
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
simple-stack-compose-integration
-
The navigation compose library is the most confusing thing I've tried to learn in a while.
Yup, that's why we're working on https://github.com/Zhuinden/simple-stack-compose-integration/ to make it as simple as backstack.goTo(SomeScreenKey(arg1, arg2)) instead of this navController.navigateTo("some/screen&arg1=${UrlEncoder.encode(arg1.toBase64())} stuff. If you are working on an Android app that will always be on Android-only, why would you inherit limitations from Kotlin Multi-platform?
-
Should I use fragments with Jetpack Compose?
We have https://github.com/Zhuinden/simple-stack-compose-integration/ but the fact that I'd normally prefer to use fragments kinda holds it back
-
Are Fragments in Android going to be deprecated in favor of Jetpack Compose?
Simple-Stack-Compose https://github.com/Zhuinden/simple-stack-compose-integration
-
What do you use for compose navigation?
However, it's worth noting that thanks to a guy named @matejdro we are working on a pure-Compose version, in which setup has been reduced to
-
ViewModel: for UI business, not UI operations 😮
And ,yes, although not being made for Compose, also Simple stack :)
-
What's the Current State of Android Development™?
i'd love to recommend simple-stack-compose-integration but i never wrote this missing link
-
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
-
How to migrate an existing app to compose?
If you're deadset on full compose navigation I'd check out Zhuinden`s simple-stack-compose-integration
-
simple-stack-compose-integration VS compose-navigation-reimagined - a user suggested alternative
2 projects | 4 Feb 2022
-
What is the thing you most struggle with when using Jetpack Compose?
I'm almost tempted to use multiple ComposeViews, but I'm definitely not using 1 ComposeView N composables any time soon, even though technically I have the code to support it.
What are some alternatives?
ArcAnimator - ArcAnimator helps to create arc transition animation: 2.3.+
Decompose - Kotlin Multiplatform lifecycle-aware business logic components (aka BLoCs) with routing (navigation) and pluggable UI (Jetpack Compose, SwiftUI, JS React, etc.)
AnimationEasingFunctions - Android Animation Easing Functions. Let's make animation more real!
voyager - 🛸 A pragmatic navigation library for Jetpack Compose
Lottie for Android, iOS, and React Native - Render After Effects animations natively on Android and iOS, Web, and React Native
navigation-compose-typed - Type-safe arguments for Jetpack Navigation Compose using Kotlinx.Serialization
UltimateAndroidReference - :rocket: Ultimate Android Reference - Your Road to Become a Better Android Developer
Decompose - Kotlin Multiplatform lifecycle-aware business logic components (aka BLoCs) with routing functionality and pluggable UI (Jetpack Compose, SwiftUI, JS React, etc.), inspired by Badoos RIBs fork of the Uber RIBs framework
CircleIndicator - A lightweight indicator like in nexus 5 launcher
compose-destinations - Annotation processing library for type-safe Jetpack Compose navigation with no boilerplate.
AndroidViewAnimations - Cute view animation collection.
simple-stack - [ACTIVE] Simple Stack, a backstack library / navigation framework for simpler navigation and state management (for fragments, views, or whatevers).