How Redux shows up in this material Redux appears in this channel's material as part of the story of Arc's architectural pivot to Dia. Arc was built on a Redux-style, state-driven architecture — an approach the team chose because it let them prototype and ship new features as fast as possible. When the company decided to rebuild the browser as an AI-first personal assistant, it moved away from that architecture to a Swift-based, structured concurrency model, which fixed performance bottlenecks while keeping prototype speed [^242d36d6]. Why the tradeoff matters The Redux-style setup was a deliberate tradeoff: it optimized for rapid prototyping rather than raw performance. As Josh Miller put it: We really had Arc built around how to prototype as fast as possible… So we were really optimizing for how to prototype and build new features. What to take away - Redux here is an architecture choice for speed of iteration, not a performance win. - Rebuilding Dia meant replacing the Redux-style state-driven model with Swift and structured concurrency. - Some users felt the new architecture was less transparent than what came before — a real cost of the pivot.