Activity中Fragment导航状态保存与全Fragment数据刷新的最佳实践

Hey there! Let's talk through the best practices for preserving Fragment state during navigation and refreshing data across all Fragments in your Activity, plus how to tweak your current implementation for better reliability and maintainability.

First, let's quickly note that your current approach of preloading all Fragments as Activity fields works for fast switching, but it can lead to unnecessary memory bloat and state loss when the Activity is recreated (like on screen rotation). Let's dive into the improvements:

• Leverage Fragment's built-in state saving
  Each Fragment should handle its own state by overriding onSaveInstanceState(Bundle outState) to store critical data (like scroll positions, input text, or filter settings). Then restore this state in onCreateView or onViewCreated. Avoid relying on Activity fields to hold Fragment instances—when the Activity is recreated, these fields are reset, but the FragmentManager will automatically recreate your Fragments if they were properly added via transactions.

• Skip preloading all Fragments
  Preloading eats up memory, especially if your Fragments hold large datasets or complex views. Instead, create/retrieve Fragments on demand using findFragmentByTag():

  private static final String TAG_FEED = "feed_topics";
  
  // When switching to FeedTopicsFragment
  Fragment feedFragment = getSupportFragmentManager().findFragmentByTag(TAG_FEED);
  if (feedFragment == null) {
      feedFragment = FeedTopicsFragment.getInstance();
      getSupportFragmentManager().beginTransaction()
          .add(R.id.fragment_container, feedFragment, TAG_FEED)
          .commit();
  }
  // Hide other Fragments and show this one
  getSupportFragmentManager().beginTransaction()
      .hide(otherActiveFragment)
      .show(feedFragment)
      .commit();
  

• Use ViewModel for cross-configuration data persistence
  For data that needs to survive configuration changes (like user IDs, shared lists), use a ViewModel scoped to the Activity. ViewModels aren't destroyed when the Activity recreates, so you can store shared data here, and each Fragment can access the same ViewModel instance via ViewModelProvider(requireActivity()).

• ViewModel + LiveData (Most Recommended)
  Create a shared Activity-level ViewModel with MutableLiveData to act as a refresh trigger. Each Fragment subscribes to this LiveData, and when you need to refresh all Fragments, you update the LiveData value. Here's how:

  // Shared ViewModel
  public class MainActivityViewModel extends ViewModel {
      private final MutableLiveData<Boolean> refreshTrigger = new MutableLiveData<>(false);
  
      public void triggerFullRefresh() {
          refreshTrigger.setValue(true);
      }
  
      public LiveData<Boolean> getRefreshTrigger() {
          return refreshTrigger;
      }
  }
  
  // In each Fragment
  @Override
  public void onViewCreated(@NonNull View view, @Nullable Bundle savedInstanceState) {
      super.onViewCreated(view, savedInstanceState);
      MainActivityViewModel viewModel = new ViewModelProvider(requireActivity()).get(MainActivityViewModel.class);
      
      viewModel.getRefreshTrigger().observe(getViewLifecycleOwner(), shouldRefresh -> {
          if (shouldRefresh) {
              // Run your data refresh logic here
              loadLatestData();
              // Reset the trigger to avoid repeated refreshes
              viewModel.getRefreshTrigger().setValue(false);
          }
      });
  }
  

  When you need all Fragments to refresh (e.g., after a user updates their profile), just call viewModel.triggerFullRefresh() from your Activity or any Fragment.

• Direct Fragment method calls (Use sparingly)
  If you absolutely need to call a refresh method directly on a Fragment, retrieve it via findFragmentByTag() and check if it's added to the Activity:

  FeedTopicsFragment feedFrag = (FeedTopicsFragment) getSupportFragmentManager().findFragmentByTag(TAG_FEED);
  if (feedFrag != null && feedFrag.isAdded()) {
      feedFrag.refreshData();
  }
  // Repeat for other Fragments
  

  Note: This increases coupling between components, so only use it if ViewModel isn't feasible.

• EventBus (Avoid if possible)
  Libraries like GreenRobot EventBus let you send refresh events across components, but they make code harder to debug and increase coupling. Stick to ViewModel unless you have a specific use case that demands it.

Here's how to adjust your navigation code to follow these practices:

private static final String TAG_FEED_TOPICS = "feed_topics";
private static final String TAG_USER_DISCUSSIONS = "user_discussions";
private static final String TAG_USER_CONVERSATIONS = "user_conversations";

activityMainNavigation.setOnNavigationItemSelectedListener(item -> {
    Fragment targetFragment = null;
    String targetTag = null;

    switch (item.getItemId()) {
        case R.id.nav_feed:
            targetTag = TAG_FEED_TOPICS;
            targetFragment = getSupportFragmentManager().findFragmentByTag(targetTag);
            if (targetFragment == null) {
                targetFragment = FeedTopicsFragment.getInstance();
            }
            break;
        case R.id.nav_discussions:
            targetTag = TAG_USER_DISCUSSIONS;
            targetFragment = getSupportFragmentManager().findFragmentByTag(targetTag);
            if (targetFragment == null) {
                targetFragment = UserDiscussionsFragment.getInstance(SessionPersistor.getSignedInUserId());
            }
            break;
        case R.id.nav_conversations:
            targetTag = TAG_USER_CONVERSATIONS;
            targetFragment = getSupportFragmentManager().findFragmentByTag(targetTag);
            if (targetFragment == null) {
                targetFragment = MyConversationsFragment.getInstance(SessionPersistor.getSignedInUserId());
            }
            break;
    }

    if (targetFragment != null) {
        FragmentTransaction transaction = getSupportFragmentManager().beginTransaction();
        // Hide all currently added Fragments
        for (Fragment frag : getSupportFragmentManager().getFragments()) {
            transaction.hide(frag);
        }
        if (!targetFragment.isAdded()) {
            transaction.add(R.id.fragment_container, targetFragment, targetTag);
        }
        transaction.show(targetFragment).commit();
        return true;
    }
    return false;
});

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