Where to go next

Continue By Task

The Learn path established the programming model and architecture. Continue by the task your application needs:

• Set up the browser: client setup and static assets.

• Build interfaces and input: HTML and event bindings, typed forms and validation, ordinary HTTP forms and redirects, and file uploads.

• Structure and protect pages: routes and navigation, layouts and live sessions, services and dependency injection, and authentication and sessions.

• Own local and collection state: stateful components, nested LiveViews, and streams.

• Manage lifecycle behavior: asynchronous work, subscriptions, and connected resources, lifecycle hooks, and lifecycle feedback and page state.

• Integrate browser APIs: browser commands, events, and hooks.

• Verify and operate: testing, troubleshooting, configuration, lifecycle observability, and deployment.

The Guides index provides the same complete task map with a summary of each guide.

Explore Working Examples

Start with the typed counter and shopping cart for the model-message-render loop. Then choose a focused executable slice:

• Lifecycle and connection phases for disconnected render, connected mount, and reconnect behavior.

• Typed documentation navigation for checked route destinations and browser history.

• Validated profile form, stable repeated contact rows, form save workflow, and bounded text upload for typed input, field errors, structural edits, persistence coordination, and upload ownership.

• Service injection, connected lifecycle registration, async report, and subscription clock for finite work and lifecycle-owned live data backed by application services.

• Activity stream, voting components, and browser integration for larger changing collections, local component state, and browser-only APIs.

Examples demonstrate one behavior at a time. They are evidence for an API, not a required application architecture.

Look Up The Current API

Use the API reference for exact current signatures. Scalive is alpha software, so prefer the API matching the revision or artifact you use rather than code copied from an older discussion.

Evaluate Scalive For An Application

Read Project status and compatibility scope before depending on a Phoenix feature or deploying a production application. Scalive targets useful behavioral parity, but does not imply that every Phoenix API or operational characteristic is present.

Developers coming from Phoenix can use the Phoenix LiveView orientation to map familiar concepts to Scalive's Scala-first API.