The Elm Architecture

By the end of this guide, you will:

• Identify the three callables: Init, Update, and View

• Explain why UPDATE must be a pure function (no side effects)

• Understand the separation of concerns in MVU architecture

• Explain Model-View-Update in your own words

• Trace data flow through the complete MVU cycle

• Describe how unidirectional data flow prevents bugs

• Draw the MVU loop from memory

• Compare MVU to web server request/response cycle (“unlike a web request, state persists”)

⚠️ This page is a stub. Help us write it! See the Documentation Plan and Style Guide.

Next: Models