What's the difference between commit() and apply() in Shared Preference

-
apply() was added in 2.3, it commits without returning a boolean indicating success or failure.
commit() returns true if the save works, false otherwise.
apply() was added as the Android dev team noticed that almost no one took notice of the return value, so apply is faster as it is asynchronous
commit() writes the data synchronously (blocking the thread its called from). It then informs you about the success of the operation.
apply() schedules the data to be written asynchronously. It does not inform you about the success of the operation.
If you save with apply() and immediately read via any getX-method, the new value will be returned!
If you called apply() at some point and it's still executing, any calls to commit() will block until all apply-calls and its own commit are finished.

Comments

Post a Comment

Popular posts from this blog

Styling Bottom Navigation

-
Image
Styling Bottom Navigation Off the bat, the library provides considerable styling options. But after recent updates, there has been a lot more. Some of these additions include notification badges and coordinating behaviors. It also includes  on-scroll Quick Return pattern . Its all that one could ever want with the Bottom Navigation. This library is much more feature-rich than  what Android Design Support Library offers . So if you want more customization options and more control, you know what to use. Before we get to that, here’s a heads-up. We’ll be using and referencing a lot of colors. Normally, we reference colors in Android like this: ContextCompat.getColor(context, R.id.yourcolor); Now I’m no fan of writing such a lengthy line for fetching a simple color resource. So I’ll write a simple method that shortens what I have to type. private int fetchColor( @ColorRes int color) { return ContextCompat.getColor(this, color); } Great! From now on I don’t have
Read more

Lottie Animation in Android

-
Gradle is the only supported build configuration, so just add the dependency to your project  build.gradle  file: dependencies { ... compile 'com.airbnb.android:lottie:2.2.5' ... } Lottie supports ICS (API 14) and above. The simplest way to use it is with LottieAnimationView: <com.airbnb.lottie.LottieAnimationView android:id="@+id/animation_view" android:layout_width="wrap_content" android:layout_height="wrap_content" app:lottie_fileName="hello-world.json" app:lottie_loop="true" app:lottie_autoPlay="true" /> Or you can load it programmatically in multiple ways. From a json asset in app/src/main/assets: LottieAnimationView animationView = ( LottieAnimationView ) findViewById ( R . id . animation_view ) ; animationView . setAnimation ( "hello-world.json" ) ; animationView . loop ( true ) ; animationView . playAnimation ( ) ;
Read more

Set Up the AWS Mobile SDK for Android

-
Prerequisites # Before you can use the AWS Mobile SDK for Android, you will need the following: An  AWS Account Android 2.3.3 (API Level 10) or higher (for more information about the Android platform, see  Android Developers ) Android Studio  or  Android Development Tools for Eclipse After completing the prerequisites, you will need to do the following to get started: Get the AWS Mobile SDK for Android. Set permissions in your  AndroidManifest.xml  file. Obtain AWS credentials using Amazon Cognito. Step 1: Get the AWS Mobile SDK for Android There are three ways to get the AWS Mobile SDK for Android. Option 1: Using Gradle with Android Studio # If you are using Android Studio, add the  aws-android-sdk-core  dependency to your app/build.gradle  file, along with the dependencies for the individual services that your project will use, as shown below. dependencies { compile 'com.amazonaws:aws-android-sdk-core:2.2.+' compile 'com.
Read more