Where to go next

Continue By Task

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

• Build application behavior: HTML and event bindings, typed forms and validation, services and dependency injection, stateful components, and asynchronous work and subscriptions.

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

• Integrate the browser: client setup and static assets and browser commands, events, and hooks.

• Ship and maintain an application: testing, troubleshooting, configuration, and deployment.

The Guides index includes uploads, streams, lifecycle UX, ordinary HTTP forms, and the remaining focused tasks.

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 and bounded text upload for typed input, field errors, and upload ownership.

• Service injection, async report, and subscription clock for finite work and connection-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.