返回按钮触发后，如何更新栈中前序Activity的Adapter条目？

Hey there! Let's break down how to get your RecyclerView to update its like status when you return from the detail page, and whether Redux is the right fit for your scenario.

First: Lightweight Solutions (No Global State Needed) #

For most cases where you're just syncing two screens, these approaches are simpler and more efficient than spinning up a global state system:

1. Use Activity Result API to Pass Updated State #

This is the most straightforward approach for basic screen-to-screen communication. Here's how it works:

• In your list activity/fragment: Register an activity result launcher to listen for updates from the detail page. When you launch the detail page, pass the item's position and current data.
• In the detail page: When the user toggles the like, update the item's isLiked status, save the change (to local DB or network), then send the updated status and position back to the list page.
• Back in the list page: Update your adapter's data source with the new isLiked value and call notifyItemChanged(position) to refresh just that row (way better for performance than notifyDataSetChanged).

Example code snippets:
List Page:

// Register the launcher
private val likeUpdateLauncher = registerForActivityResult(ActivityResultContracts.StartActivityForResult()) { result ->
    if (result.resultCode == Activity.RESULT_OK) {
        result.data?.let { data ->
            val position = data.getIntExtra("ITEM_POSITION", -1)
            val isLiked = data.getBooleanExtra("UPDATED_IS_LIKED", false)
            if (position != -1) {
                // Update your data source
                yourItemList[position].isLiked = isLiked
                // Refresh the specific row
                yourAdapter.notifyItemChanged(position)
            }
        }
    }
}

// Launch detail page on item click
fun onItemClick(item: YourDataModel, position: Int) {
    val intent = Intent(this, DetailActivity::class.java)
    intent.putExtra("ITEM_DATA", item)
    intent.putExtra("ITEM_POSITION", position)
    likeUpdateLauncher.launch(intent)
}

Detail Page:

private lateinit var currentItem: YourDataModel
private var itemPosition = -1

override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    // Get data from intent
    currentItem = intent.getParcelableExtra("ITEM_DATA")!!
    itemPosition = intent.getIntExtra("ITEM_POSITION", -1)
}

// Toggle like function
fun toggleLike() {
    currentItem.isLiked = !currentItem.isLiked
    // Save the change (e.g., to Room or API)
    saveLikeStatus(currentItem)
    // Send result back to list page
    val resultIntent = Intent().apply {
        putExtra("ITEM_POSITION", itemPosition)
        putExtra("UPDATED_IS_LIKED", currentItem.isLiked)
    }
    setResult(Activity.RESULT_OK, resultIntent)
    finish()
}

2. Shared ViewModel with LiveData #

If you want a more elegant solution (especially if you're using Jetpack components), a shared ViewModel lets both screens observe the same data source. The ViewModel is scoped to the parent activity, so both the list and detail fragments/activities can access it:

Shared ViewModel:

class ItemViewModel : ViewModel() {
    private val _items = MutableLiveData<MutableList<YourDataModel>>()
    val items: LiveData<List<YourDataModel>> = _items

    fun setInitialItems(items: List<YourDataModel>) {
        _items.value = items.toMutableList()
    }

    fun updateItemLikeStatus(position: Int, isLiked: Boolean) {
        _items.value?.let { currentList ->
            currentList[position].isLiked = isLiked
            // Trigger LiveData update
            _items.value = currentList
        }
    }
}

List Page:

// Get the shared ViewModel (scoped to the activity)
val viewModel by viewModels<ItemViewModel>()

override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    // Initialize data
    viewModel.setInitialItems(yourInitialItemList)
    // Observe data changes to update adapter
    viewModel.items.observe(this) { updatedItems ->
        yourAdapter.submitList(updatedItems)
    }
}

// Launch detail page with position
fun onItemClick(item: YourDataModel, position: Int) {
    val intent = Intent(this, DetailActivity::class.java)
    intent.putExtra("ITEM_POSITION", position)
    startActivity(intent)
}

Detail Page:

// Get the same shared ViewModel
val viewModel by viewModels<ItemViewModel>(ownerProducer = { requireActivity() })

fun toggleLike() {
    val position = intent.getIntExtra("ITEM_POSITION", -1)
    if (position != -1) {
        val currentItem = viewModel.items.value?.get(position) ?: return
        val newIsLiked = !currentItem.isLiked
        // Update the ViewModel's data
        viewModel.updateItemLikeStatus(position, newIsLiked)
        // Save the change to DB/API
        saveLikeStatus(currentItem.copy(isLiked = newIsLiked))
        finish()
    }
}

When to Use Redux (or Global State Management) #

Redux is a great tool, but it's overkill for a simple two-screen sync. You should consider it only if:

• Your app has multiple screens/components that need access to the like status (e.g., a profile screen showing liked items, a home feed showing likes).
• You have complex state logic (e.g., handling network requests for likes, undo functionality, or syncing with a backend).
• You want a single source of truth for all app state to avoid inconsistencies.

If you do go with Redux (using libraries like Redux-Kotlin or even Jetpack Compose's state hoisting for simpler cases), you'd:

1. Define an action (e.g., ToggleLikeAction(itemId: String, isLiked: Boolean)).
2. Update your reducer to modify the state's item list when this action is dispatched.
3. Have both the list and detail screens subscribe to the store's state.
4. In the detail page, dispatch the ToggleLikeAction when the user toggles the like.

Key Notes to Avoid Common Issues #

• Always update your actual data source (not just the UI) before notifying the adapter—otherwise, the change will disappear on the next refresh.
• Use notifyItemChanged(position) instead of notifyDataSetChanged to only refresh the affected row (better performance).
• If saving to a backend, make sure to handle success/failure states (e.g., show a snackbar if the like fails, and revert the UI state).

内容的提问来源于stack exchange，提问作者Ammar Alrefai