SDK Overview
Lombok exposes several SDK surfaces, each aimed at a different part of the platform.
The most important distinction is:
- App Worker SDK for app backend and worker execution
- App Browser SDK for embedded app UIs
- Core SDK for general typed client access
- UI Toolkit for reusable design-system components
Why multiple SDKs exist
Section titled “Why multiple SDKs exist”Lombok is not a single-process application with one extension API.
Different parts of the platform have different needs:
- app workers need task/runtime/platform APIs
- embedded app UIs need browser-side integration and bridging
- platform clients need typed API access
- UI work benefits from reusable design primitives
That is why the SDK surface is split across packages rather than forced into one abstraction.
SDK packages
Section titled “SDK packages”@lombokapp/app-worker-sdk
Section titled “@lombokapp/app-worker-sdk”Use this when writing:
- runtime workers
- backend app logic
- task handlers
- request handlers
@lombokapp/app-browser-sdk
Section titled “@lombokapp/app-browser-sdk”Use this when building:
- embedded app frontends
- app UIs loaded into Lombok
- browser-side bridges back into the platform
@lombokapp/sdk
Section titled “@lombokapp/sdk”Use this for:
- typed client access to Lombok APIs
- platform consumers that are not specifically app-worker or embedded-app-browser code
@lombokapp/ui-toolkit
Section titled “@lombokapp/ui-toolkit”Use this when you want:
- reusable UI components
- Lombok-aligned presentation patterns
- a shared design-system layer
Suggested selection guide
Section titled “Suggested selection guide”If you are building…
- a worker or app backend → App Worker SDK
- an embedded app frontend → App Browser SDK
- a general typed client → Core SDK
- UI components or app-facing design patterns → UI Toolkit
Next steps
Section titled “Next steps”Continue with: