Batoi UIF Docs

Micro App Lifecycle

Learn how a Batoi UIF Micro App is initialized, updated, exported, and promoted to production.

Start Reading Open GitHub
On this page

Micro App Lifecycle

A UIF Micro App starts as a bounded browser surface and can later be connected to governed backend services.

Lifecycle Diagram

Initialize Interact Validate Export Governed Proxy defaults/state controls rules/status JSON/CSS/SVG optional service

Lifecycle Steps

1. Define the root element and purpose. 2. Load route-scoped UIF CSS and JavaScript. 3. Initialize state from defaults, URL, file input, or local data. 4. Render controls, preview, output, and status. 5. Respond to user interaction. 6. Export or submit the result. 7. Add server integration only when persistence, audit, identity, or policy requires it.

State

Client-only examples should keep state in memory by default.

Use downloads for portable outputs:

  • JSON project files
  • CSV exports
  • SVG charts
  • generated CSS
  • generated HTML snippets

Avoid storing secrets in local storage.

Production Promotion

Before promoting a Micro App to production, define:

  • authentication and authorization needs
  • audit trail requirements
  • service endpoints
  • API key handling
  • validation rules
  • error recovery behavior