✳flâneur — a map of the web's best reading

UI = f(statesⁿ) - daverupert.com

daverupert.com · 1,316 words · saved by 1 readers

“UI is a function of state” is a pretty popular saying in the front-end world. In context (pun intended), that’s typically referring to application or component state. I thought I’d pull that thread a little further and explore all the states that can effect the UI layer… Every application whether it’s a to-do list or a shopping cart or some radically complex app will have some state. State isn’t uniform and typically exists at a variety of different levels. We’ll start at the top and drill down… Data stores and feature gating that typically happens at the application level. Vince Speelman’s wonderful Nine States of Design do a great job summing up all the states that a page or component might exist in. Vince’s list is perfect to me and keeps being relevant after all these years, I would add two items. In my experience both the page and each component will contain some mixture of these states as well as being reactive to global state changes. Individual elements can (and will) have the

“UI is a function of state” is a pretty popular saying in the front-end world. In context ( pun intended ), that’s typically referring to application or component state. I thought I’d pull that thread a little further and explore all the states that can effect the UI layer… First-party application states Every application whether it’s a to-do list or a shopping cart or some radically complex app will have some state. State isn’t uniform and typically exists at a variety of different levels. We’ll start at the top and drill down… Global state Data stores and feature gating that typically happen

Explore this link on the map →

saved by

related reading