Worked examples
Examples connect a complete source project to a visible result. They should show what the person configures, what the task does, and how to check the outcome. A short syntax fragment is not a substitute for a runnable example.
Featured projects: Federal tax return App · Weather-based sprinkler App · Chart gallery.
Illustrated field walkthrough: Simple Data. Rich Semantics. Adaptive Interaction. shows Boolean defaults, custom answer captions, a tax death-date question and a three-answer Nullable Boolean. Its phone regions are labeled mockups, and its source fragments are not a complete App.
Use the App recipes for declarations and metadata, respecting their explicit runtime limits. For a runnable configuration-form App, start with the complete tutorial source. Use the linked contract and your installed SDK before adapting either. Further illustrated examples will cover these goals:
| Example | Learning goal |
|---|---|
| First TypeScript App | Source-defined settings and text, validation, deployment, and task creation. |
| First Rust App | A library App using public SDK types and the Hub build workflow. |
| Request and live-data service | Operations, responses, subscriptions, and visible controls. |
| Shared TypesOnly package | Public type ownership and a dependent App. |
| Persistent records | Stable data identity and compatible evolution. |
| Localized result | Source documentation, typed messages, translation, and import. |
| Charted result | A typed dataset, ordinary data, preview, full view, and accessible interpretation. |
Each completed example will identify tested SDK/client versions, required devices and permissions, expected output, and meaningful failure cases. Screenshots and diagrams will explain the result alongside source that can be checked. Incomplete schematics will be explicitly labeled.
Start with Developing Apps. Exact behavior belongs in the shared reference, which examples must follow.