Example application: Faye Tasks
Compose a task manager with the Faye UI package, native forms and browser-local recovery.
A real small application
Faye Tasks is a browser-local task manager built with Faye UI. It demonstrates selected public controls, native forms, typography, icons, dialogs, provider preferences and feedback. Task state and persistence belong to the application; no data engine is added to the library.
Explore the application patterns
Read the example source below to see how to compose the components in your own application. Install Faye UI through npm once a corrected release is available; installation records its current status. Access to the private Faye UI repository is not a requirement for using the published package.
| Flow | Faye UI responsibility | Application responsibility |
|---|---|---|
| Create and edit | Named native controls and dialog behavior | Trimmed title validation and task updates |
| Complete | Checkbox state and keyboard semantics | Stored completion value |
| Delete | Confirmation dialog and focus behavior | Remove the selected record and choose surviving focus |
| Filter | Search input and native select | Filter current records |
| Persistence | Warning feedback and actions | Validate versioned data, retain memory on failure, explicit reset |
| Appearance | Theme/provider, tokens and shared Icon | Select density/direction and explicit artwork |
Read the actual source
Application, task model, client entry, styles, manifest, TypeScript configuration, Vite configuration and setup/limitations are copied from the real application, not a second illustrative implementation.
Package usage
The example imports the same public package paths documented for application developers. The standalone example uses normal package dependencies, with no source aliases. The package must be available from npm before installing the example.
Deliberate limits
The app is CSR, uses English copy and persists in one browser. Invalid stored data is retained until explicit confirmed reset. Failed writes preserve in-memory changes but cannot guarantee persistence after closing the tab. There is no backend, cross-tab conflict resolution, authentication, deployment or publication. Five-language library examples and SSR/streaming/RSC consumers remain separate documented contracts.