Overview
Start Here
Installation
Tutorial
Architect App Builder
Todo List App
Beacon Beats Audio Store
UCAL App
Authoring
Dynamic Apps
Static Apps
dev_docs
Why Pharos Feels Different
Architect Builder
Framework
Artifacts & Layout
Configuration
Outbound Email
How to Use CLI
Contracts
YAML Authoring
Action Hooks and Middleware
Feature Transaction Primitives
Generated Surfaces
Declarative CRM
Input Validation
Identity and Tenancy
UI Surface Library
Social Connections
Payment Provider Management
Integration Adapters
Reference
Contract, UI, and Surface Reference
Styling UI Elements
Architect Media Artifacts
API Docs
Use Cases
Dynamic SPAs
Generated Admin and APIs
Scheduling and Marketplaces
Multi-App Hosting
Release Notes
Vision
Pharos Framework

← Back

Server-Driven Dynamic SPAs

Pharos pages remain real URLs and complete server-rendered documents. Declared navigation can replace a named main region and update browser history, while declared form actions can return smaller committed-state fragments. Direct navigation, reload, and normal form fallback remain valid.

This works well for catalogs, dashboards, account portals, collaboration tools, content applications, and operational products. Add app JavaScript where the browser has a genuine job—such as Beacon Beats audio playback—not merely to mirror database state or hand-carry every mutation through JSON.