Animated Recycler View is a library that allows you to animate a recycler view in your project like Google does it in its Google Play Store. Only the first visible items are animated there and you will see no animation when the recycler view scrolls up.
Reasons to use it
This library solves several problems:
It works stably fast and without jerks.
It doesn’t need to utilize the adapter to animate items when they appear for the first time.
While working on a project, most of time we need animation similar to the one used in the Google Play Store but didn’t find any appropriate library on Internet/ Github/ StackOverflow that could help us with this task.
There are so many ways to make mobile apps ranging from direct platform specific development (using Java and Kotlin for Android, and ObjC and Swift for iOS), there’s React Native from Facebook, Electrode Native from Walmart, the Ionic framework, Unity for certain types of apps, and the flutter.io framework which was just released by Google.
Ever wondered how these libraries and frameworks affect the size of your app? Let’s analyze some apk files for apps written in some of these ways. The apps are very basic, containing just a title at the top and a text at the center of the screen.
This will show, for a bare minimum app what these frameworks need to package along with the apk for it to be able to run.
For this test I created four different versions of the app, one in each of Java, Kotlin, React Native, and Flutter. (Android API 27)
The apks were then published for release type using Android Studio for Java and Kotlin and using the cli for React Native and Flutter.
Default proguard configuration was used.
The apks were analyzed using the Analyze APK feature in Android Studio.
This article looks at many categories of Java defects that Kotlin prevents in addition to null safety. Kotlin showed a surprising impact on productivity.
This article looks at many categories of Java defects that Kotlin prevents in addition to null safety. My first article (5 cool thing about Kotlin) provided a brief introduction to Kotlin and showed a surprising impact on productivity.
It’s important to realize the difference in value in fixing a defect in one class versus preventing an entire category of Java defects from occurring in any class.
Today, the MVC pattern is used by well-known frameworks such as Ruby on Rails, Apple iOS Development, ASP.NET MVC, etc. While MVP is mostly used for ASP.NET Web Forms applications and MVVM is used by WPF, Caliburn, Silverlight, nRoute, and more. Which development pattern are you currently using in your software projects? Let us know in the comments below.