Now that we have our editor we can start saving our values.

We learned in a previous video that the on pause life cycle method

is a good place to save any unsaved changes.

Let's make some space at the bottom of our file and

use the Ctrl+O shortcut to override the on pause method.

Then, we can store our string using the putString method of our editor.

It takes two parameters, the key and the value.

Let's type mEditor.putString and

I'll call my key KEY_EDITTEXT.

And for the value, we'll do mEditText.getText,

which returns an editable.

Then .toString, to make it a string.

Then we can use Alt+Enter on the key to create it.

I'll name mine similar to the variable, key_edittext.

Now that we've saved our string to the editor,

we just need to add mEditor.apply

to save our changes to our shared preferences object.

We've now saved the value of our edit text in the on pause method.

All that's left is to retrieve that value in the on create method and

set the text of our edit text to that value.

We can retrieve the value by using the get string method

on a shared preference object.

When retrieving a value from a shared preference we need to provide the key for

the value and a default value to use in case that key isn't found.

In the bottom of our on create, let's retrieve our string by calling

MSharedPreferences.getString and

passing in our KEY_EDITTEXT string for

the key parameter and an empty string for the default value.

Next, let's save this value into a string called editTextString.

Lastly, let's update our edit text by typing mEditText.setText.

And we'll set it to editTextString.

The last step is to test the app to make sure it works as expected.

I'll type in some text.

And close the app by hitting the back button.

And when we reopen the app, our text is still here, perfect.

Before we go on, let's talk about removing shared preference values.

This is especially useful for

testing, or if your users want to reset an app to it's default values.

This can be done by using the clear method of a shared preference editor object.

Also, we can use the remove method, and pass in a key, to remove just one value.

Once you're done removing values,

don't forget to use the apply method to save your changes.

Shared preferences is the easiest way to store data in Android, but

only if that data can easily fit into a key value pair.

If you're interested in how to store more complicated data, like a picture or

a Java file, please check out our videos on data persistence in Android,

which are linked in the teacher's notes.

They also cover shared preferences in a little more detail.

For now, we're going to move onto a practice project

to test everything that you've learned so far.