Observer pattern for UI updates in LLD - System Design Guide

Problem Statement

When UI components directly query data sources or tightly couple with data models, any change in data requires manual updates in multiple places. This leads to inconsistent UI states, duplicated update logic, and harder maintenance as the application grows.

Solution

The observer pattern solves this by letting UI components subscribe to data changes. When the data changes, it automatically notifies all subscribed UI components to update themselves. This decouples data sources from UI, ensuring consistent and automatic updates.

Architecture

Data Model

→Observer 1

↓

→Observer 2

This diagram shows the data model (subject) notifying multiple observers (UI components) when data changes, triggering their updates.

Trade-offs

✓ Pros

→

Decouples data sources from UI components, improving modularity.

→

Automatic updates reduce bugs from stale or inconsistent UI states.

→

Supports multiple observers easily, enabling flexible UI designs.

✗ Cons

→

Can lead to memory leaks if observers are not properly unsubscribed.

→

Notification overhead may impact performance if many observers exist.

→

Debugging update flows can be harder due to indirect communication.

Use when multiple UI components depend on shared data that changes frequently, especially in medium to large applications with dynamic interfaces.

Avoid when UI is simple with few components or data changes are rare, as the pattern adds unnecessary complexity.

Real World Examples

Google

Android UI framework uses observer pattern via LiveData to update UI components automatically when data changes.

React (Facebook)

React's state management uses observer-like subscriptions to re-render components on state changes.

Microsoft

Windows Presentation Foundation (WPF) uses observer pattern with INotifyPropertyChanged interface for UI updates.

Code Example

The before code shows manual UI refresh calls after data changes, risking missed updates. The after code implements the observer pattern where UIComponent subscribes to Subject. When Subject's data changes, it notifies UIComponent automatically to update, ensuring consistent UI refresh.

LLD

### Before: Without Observer Pattern
class DataModel:
    def __init__(self):
        self.data = None

class UIComponent:
    def __init__(self, model):
        self.model = model

    def refresh(self):
        print(f"UI refreshed with data: {self.model.data}")

model = DataModel()
ui = UIComponent(model)

# Manual update required
model.data = 'New Data'
ui.refresh()


### After: With Observer Pattern
class Subject:
    def __init__(self):
        self._observers = []
        self._data = None

    def subscribe(self, observer):
        self._observers.append(observer)

    def unsubscribe(self, observer):
        self._observers.remove(observer)

    @property
    def data(self):
        return self._data

    @data.setter
    def data(self, value):
        self._data = value
        self._notify()

    def _notify(self):
        for observer in self._observers:
            observer.update(self._data)

class Observer:
    def update(self, data):
        pass

class UIComponent(Observer):
    def update(self, data):
        print(f"UI refreshed with data: {data}")

model = Subject()
ui = UIComponent()
model.subscribe(ui)

model.data = 'New Data'

Alternatives

Polling

UI components repeatedly check data for changes instead of being notified.

Use when: Use when data changes are infrequent and notification infrastructure is unavailable.

Data Binding

Automates UI updates by binding UI elements directly to data properties, often using observer pattern internally.

Use when: Use when framework supports data binding for simpler UI update management.

Summary

Observer pattern decouples data sources from UI components by enabling automatic notifications on data changes.

It ensures consistent and timely UI updates without manual refresh calls, improving maintainability.

Proper use avoids stale UI states but requires careful management of subscriptions to prevent memory leaks.