Flutter Cubit Smart Caching Pattern

Prevent unnecessary data reloads when users navigate between tabs/pages by adding time-based freshness checks to Cubit classes.

The Problem

Flutter apps using BlocProvider at root level keep cubits alive across navigation. But pages often call loadData() in their initState or _EmptyView, triggering a full reload every time the user switches tabs. This causes:

• Unnecessary API/database calls
• Loading spinners on every tab switch
• Wasted bandwidth and battery

The Pattern

Add three things to every data cubit:

1. Freshness Tracking

DateTime? _fetchedAt;
static const _staleAfter = Duration(minutes: 5);

2. Skip Logic in Load Method

Future<void> loadData({bool force = false}) async {
  // Skip if data is fresh (unless forced)
  if (!force && state is DataLoaded && _fetchedAt != null) {
    if (DateTime.now().difference(_fetchedAt!) < _staleAfter) {
      return;
    }
  }

  // Only show loading spinner on FIRST load
  if (state is! DataLoaded) {
    emit(const DataLoading());
  }

  // ... fetch data ...

  _fetchedAt = DateTime.now();
  emit(DataLoaded(data: result));
}

3. Force Refresh on Mutations

Future<void> addItem(Item item) async {
  await _repository.add(item);
  await loadData(force: true);  // Force refresh after mutation
}

Key Decisions

Checklist

When adding smart caching to a cubit:

• Add DateTime? _fetchedAt field
• Add static const _staleAfter with appropriate duration
• Add bool force = false parameter to load method
• Add freshness check at top of load method
• Only emit Loading state on first load (state is! DataLoaded)
• Set _fetchedAt = DateTime.now() before emitting loaded state
• Add force: true to all mutation methods that need immediate refresh
• Ensure cubit is in root MultiBlocProvider (not created per-page)

Anti-Patterns

• Constructing a cubit inside build(), such as BlocProvider.value(value: DataCubit()), which creates a new instance on every build
• Providing a data cubit per page with BlocProvider(create: ...), which disposes the cubit and its cache when the page leaves the tree
• Calling loadData() unconditionally in every page's initState
• Showing loading spinner on every navigation (users see flicker)
• Not forcing refresh after add/delete/update mutations

Sources

• https://pub.dev/documentation/flutter_bloc/latest/flutter_bloc/BlocProvider-class.html