Architecture in the Wild
Field architecture through live state, information, interaction and product-boundary decisions rather than abstract diagrams.
Parts are listed in the recommended reading order.
Where Should Canonical State Live in a Product?
Cache, optimistic UI, recovery storage and cloud data can coexist, but only one layer should own canonical authority.
Information Architecture Is Not Menu Design
Navigation is only the visible layer. Real information architecture defines entities, vocabulary, relationships, context and retrieval.
Loading, Empty, Error, Offline and Conflict: The Invisible Product Architecture
A reliable product knows how to behave when data is missing, writes fail, the device is offline or two valid states conflict.
When Is a Tool a Feature, and When Is It a Separate Product?
A separate brand or URL does not create a product. Independence requires its own user job, value loop, state and operating justification.
Opening a Subdomain Is Not Product Strategy
A subdomain can provide a real runtime or ownership boundary, but it cannot repair a product boundary that was never defined.
If a Product Has Two Sources of Truth, It Has None
Multiple state copies are normal. Multiple authorities are not. Name each state role and keep canonical ownership singular.
Mobile Is Not a Smaller Desktop
390px is a different operating mode: touch, native back, gestures, safe areas and attention change the product interaction model.
Why Opening a Dialog Can Become an Architecture Change
A small dialog can affect route state, entity selection, focus, back behaviour, unsaved work, mutations and accessibility.
Why Removing a Design Element Is Harder Than Adding One
Addition can justify itself locally. Removal requires understanding which decision, state or hierarchy the element actually supports.
Why I Do Not Open a Subdomain for Every New Tool
A subdomain is not an ideas folder. It should express an independent value loop and a real release or ownership boundary.