App Architecture
Lombok apps are not just bundles of UI code or simple plugins.
They are structured platform extensions that combine:
- a manifest
- permissions
- triggers
- tasks
- worker execution
- optional embedded UI
- settings and contributions
The major pieces
Section titled “The major pieces”Manifest
Section titled “Manifest”An app begins with config.json, which defines the app’s shape.
Permissions
Section titled “Permissions”The app architecture includes declared permissions as part of the overall app model.
Permissions are part of how Lombok decides what an app is allowed to do and should be understood as part of the app contract rather than a secondary implementation detail.
Triggers
Section titled “Triggers”Triggers connect events or schedules to runnable tasks.
Tasks define work units that Lombok can route into execution.
Runtime workers
Section titled “Runtime workers”Runtime workers are the execution targets most commonly used for app logic.
Optional UI
Section titled “Optional UI”Apps can also include embedded browser UI experiences.
Contributions
Section titled “Contributions”Apps can contribute navigation and UI extensions into Lombok.
Why this architecture matters
Section titled “Why this architecture matters”This model lets Lombok treat apps as first-class platform components rather than simple add-ons.
Next steps
Section titled “Next steps”Continue with: