Responsive Architecture in iOS: History, Essence, Benefits, and Integration Strategies

First Things First

The article begins by distinguishing responsive architecture from reactive programming and other architectural styles, emphasizing that it does not require FRP frameworks like Rx and can coexist with MVC or MVVM, while being tightly coupled with immutability.

Immutability

It recounts Facebook's 2014 release of immutable.js and the rise of React and Flux, noting that immutability predates modern OOP and that immutable data eliminates shared mutable state, reducing bugs caused by unpredictable state changes.

Immutable data is defined as data that cannot change after creation; mutable data carries state, which reflects the passage of time and introduces complexity such as thread‑safety issues.

Immutable Model Layer in iOS

To mitigate bugs from shared mutable state, the article advocates moving immutability to the model layer. It cites open‑source projects like Facebook’s remodel, LinkedIn’s Consistency‑Manager, and Pinterest’s Plank, which implement an immutable model layer.

Typical model code is repetitive and error‑prone; making models immutable requires boilerplate, but tools like remodel can automate generation.

Flux

Flux, introduced by Facebook, consists of view, dispatcher, store, and action, and enforces a unidirectional data flow. The view (often built with React or ComponentKit on iOS) triggers actions, which are dispatched to stores that hold mutable state, while the rest of the system remains immutable.

view: isolates data storage and mutation, suitable for React‑style immutable views.

store: abstracts mutable data state and its side effects, keeping mutation localized.

dispatcher: centralizes coordination of data changes from multiple sources.

action: encapsulates a request to change data, processed by the dispatcher.

Flux simplifies complex applications by fixing data flow, localizing state changes, and abstracting dispatch, but it is most beneficial for apps where a controller manages multiple views and models.

Essence

The essence of responsive architecture is treating the UI as a direct response to data state, rather than a tool that mutates state. Its three main advantages are predictable fixed data flow, elimination of shared mutable state, and thread‑safe shared data.

Integrating Into Existing Architecture

To adopt responsive architecture, developers should first understand the current product architecture and aim for gradual integration rather than a full rewrite. Suggested approaches include:

Using or building tools that automatically generate immutable models and employing the observer pattern to push new model instances on change (e.g., Consistency‑Manager).

Introducing FRP frameworks like Rx combined with MVVM, following existing articles such as limboy’s guide.

The choice depends on product complexity and existing architecture. While making views immutable can further improve predictability, it often requires substantial refactoring and may not be suitable for fast‑moving teams.

Responsive architecture is especially well‑suited for news or information‑display apps, but in practice most apps can benefit from its principles.

Source: http://blog.mrriddler.com/2017/06/28/iOS%E5%93%8D%E5%BA%94%E5%BC%8F%E6%9E%B6%E6%9E%84/