SharedPreferences / DataStore in Android Kotlin - UI Render Trace

Component - SharedPreferences / DataStore

This UI component demonstrates how to save and read simple user data using SharedPreferences or DataStore in Android Kotlin. It shows a text input and a button to save the input, and a text display to show the saved value.

Widget Tree

LinearLayout
├─ EditText
├─ Button
└─ TextView

The root is a vertical LinearLayout containing three children stacked vertically: an EditText for user input, a Button to save the input, and a TextView to display the saved data.

Render Trace - 4 Steps

Step 1: LinearLayout

Step 2: EditText

Step 3: Button

Step 4: TextView

State Change - Re-render

Trigger:User types text and presses the Save button

Before

TextView shows 'Saved value will appear here', no data saved

→

After

TextView updates to show the text user typed and saved

Re-renders:The TextView updates to display the new saved value; EditText and Button remain unchanged

UI Quiz - 3 Questions

What happens when the user presses the Save button?

A The app closes immediately

B The typed text is saved and displayed below

C The EditText clears and nothing is saved

D The button disappears

Key Insight

Using SharedPreferences or DataStore allows apps to save small pieces of user data persistently. The UI typically includes input fields and buttons to save data, and text views to show saved values. Keeping the layout simple and clear helps users understand how to save and see their data.

Practice

1. What is the main purpose of SharedPreferences in Android development?

easy

A. To handle network requests and responses

B. To create complex database tables for large data storage

C. To save small amounts of key-value data persistently on the device

D. To design user interface layouts

Solution

1. Step 1: Understand SharedPreferences role

   SharedPreferences is designed to store small amounts of data as key-value pairs persistently on the device.

2. Step 2: Compare with other options

   Options B, C, and D describe unrelated tasks like databases, networking, and UI design, which are not the purpose of SharedPreferences.

3. Final Answer:

   To save small amounts of key-value data persistently on the device -> Option C

4. Quick Check:

   SharedPreferences = small persistent key-value storage [OK]

Hint: Remember SharedPreferences stores simple key-value pairs [OK]

Common Mistakes:

• Confusing SharedPreferences with databases
• Thinking SharedPreferences handles UI or network
• Assuming SharedPreferences stores large files

2. Which of the following is the correct way to get a SharedPreferences instance in Kotlin inside an Activity?

easy

A. val prefs = SharedPreferences("my_prefs")

B. val prefs = getSharedPreferences("my_prefs", Context.MODE_PRIVATE)

C. val prefs = SharedPreferences.getInstance("my_prefs")

D. val prefs = getPreferences("my_prefs")

Solution

1. Step 1: Recall correct method to get SharedPreferences

   The correct method is to call getSharedPreferences(name, mode) on a Context, passing the name and mode.

2. Step 2: Analyze options

   val prefs = getSharedPreferences("my_prefs", Context.MODE_PRIVATE) uses the correct method. Options A, C, and D are invalid constructors or methods. val prefs = getPreferences("my_prefs") uses getPreferences which does not take a name parameter.

3. Final Answer:

   val prefs = getSharedPreferences("my_prefs", Context.MODE_PRIVATE) -> Option B

4. Quick Check:

   Use getSharedPreferences(name, mode) to get prefs [OK]

Hint: Use getSharedPreferences with name and mode inside Activity [OK]

Common Mistakes:

• Trying to instantiate SharedPreferences directly
• Using getPreferences with a name parameter
• Confusing method names or parameters

3. What will be the output of this Kotlin code snippet using SharedPreferences?

val prefs = getSharedPreferences("settings", Context.MODE_PRIVATE)
val editor = prefs.edit()
editor.putString("username", "Alice")
editor.apply()
val name = prefs.getString("username", "Unknown")
println(name)

medium

A. null

B. Unknown

C. Compilation error

D. Alice

Solution

1. Step 1: Store value in SharedPreferences

   The code puts the string "Alice" with key "username" and applies the changes asynchronously.

2. Step 2: Retrieve stored value

   Then it retrieves the value for "username"; since it was stored, it returns "Alice" instead of the default "Unknown".

3. Final Answer:

   Alice -> Option D

4. Quick Check:

   Stored value retrieved correctly = Alice [OK]

Hint: Stored keys return saved value, else default [OK]

Common Mistakes:

• Forgetting to call apply() or commit()
• Expecting default value when key exists
• Confusing synchronous and asynchronous apply

4. Identify the error in this Kotlin code using DataStore to save a boolean value:

val dataStore = context.createDataStore(name = "settings")
fun saveFlag(flag: Boolean) {
  dataStore.edit { preferences ->
    preferences[booleanPreferencesKey("flag")] = flag
  }
}

medium

A. Missing 'suspend' modifier on the saveFlag function

B. Missing commit() call after edit block

C. booleanPreferencesKey should be replaced with stringPreferencesKey

D. DataStore cannot store boolean values

Solution

1. Step 1: Check DataStore function modifiers

   The function saveFlag must be marked suspend because it calls dataStore.edit(), which is a suspend function.

2. Step 2: Verify other code parts

   The createDataStore call is correct. The edit block commits changes automatically. Using booleanPreferencesKey is correct for boolean values. DataStore supports boolean values.

3. Final Answer:

   Missing 'suspend' modifier on the saveFlag function -> Option A

4. Quick Check:

   DataStore edit requires suspend function [OK]

Hint: DataStore edit calls require suspend functions [OK]

Common Mistakes:

• Missing 'suspend' modifier on saveFlag function
• Forgetting suspend modifier on save function
• Confusing preference key types

5. You want to migrate existing user settings from SharedPreferences to DataStore in a Kotlin app. Which approach correctly handles this migration?

hard

A. Use SharedPreferencesMigration with DataStore to copy data automatically on first access

B. Manually read all SharedPreferences keys and write them to DataStore every app start

C. Delete SharedPreferences and start fresh with DataStore without migration

D. Use SharedPreferences.edit() inside DataStore's edit block

Solution

1. Step 1: Understand migration support in DataStore

   DataStore provides a built-in SharedPreferencesMigration class to migrate data automatically from SharedPreferences on first DataStore access.

2. Step 2: Evaluate other options

   Manually read all SharedPreferences keys and write them to DataStore every app start is inefficient and error-prone. Delete SharedPreferences and start fresh with DataStore without migration loses user data. Use SharedPreferences.edit() inside DataStore's edit block is invalid because SharedPreferences and DataStore APIs are separate and cannot be mixed inside edit blocks.

3. Final Answer:

   Use SharedPreferencesMigration with DataStore to copy data automatically on first access -> Option A

4. Quick Check:

   Use SharedPreferencesMigration for smooth migration [OK]

Hint: Use SharedPreferencesMigration for easy migration [OK]

Common Mistakes:

• Trying manual migration every app start
• Deleting old preferences losing data
• Mixing SharedPreferences API inside DataStore