Building Flowork Apps — The Dual-Engine Architecture

📱 Application • javascript • v1 •

Every Flowork app follows the Dual-Engine Architecture: an HTML/JS frontend (Online Mode) running in Chromium, and an optional Python/Node backend (Offline Mode). Each app must include schema.json, icon.svg, and entry files.

App Structure

Every Flowork app follows this minimal structure:

apps/my-app/
├── schema.json    # App manifest (REQUIRED)
├── icon.svg       # App icon (REQUIRED)
├── index.html     # Entry point (online mode)
├── style.css      # Styles
├── script.js      # Logic
└── systemBridge.js # Engine communication

The Manifest

schema.json is the heart of every app. It tells the engine:

  • What the app is called
  • What mode it runs in (online/offline)
  • What file to load as entry point
  • Version, description, and category

AI Builder

The AI Builder (ai-builder.html) can generate complete apps autonomously. It: 1. Takes a natural language prompt 2. Generates schema.json, index.html, style.css, script.js, icon.svg 3. Writes files via /api/ai-write 4. Can test and iterate on the code

Distribution

Apps are packaged into .flow encrypted containers using internal/packer/. These containers can be uploaded to the Flowork App Store for distribution.

INDEXED KEYWORDS:
app development dual-engine manifest schema packaging