Maybe Call Your UI Configurion Objects ViewData Instead of ViewModel
Joe Fabsevich (@mergesort) proposes to call data to configure UI elements “View Data” and keep the objects dumb. From part 1: In my experience, things become harder to maintain when they start becoming a crutch, as a place to put your code if it doesn’t neatly fall into the Model, View, or Controller label.
Refactoring – Extract Objects Horizontally or Vertically
Let’s say you have a Presenter
that creates a ViewModel
for its View
from incoming data and then presents it in said view. In this case, the Presenter
also is a ReSwift.StoreSubscriber
for good measure, but it could receive the data by any means, really.
Swipe Transitions and ReSwift

In a client meeting yesterday we tried to figure out how to animate scene transitions with swiping left/right when ReSwift is the single source of truth of the app state. What goes into the app state? How do you animate that? Should the % of the transition be part of the app state for some reason? (Spoiler: Nope.)
How to Couple UITableView Cell Identifiers and View Models
Rui Peres proposes to make UITableViewCell
view models the topmost model data. Traditionally, Cocoa developers stored something in arrays that corresponded to the indexPath
of a cell. In principle, this qualifies as “model” data already, but it’s not yet a view model. In practice, it can even be something different than a view model entirely – and make your view controllers slimmer!