Change the image.
Keep the app running.

Open an app. No account needed.

The travel demo lets you explore and save places. The todo demo lets you add and complete tasks. Both include original artwork and the Assetlib SDK.

Browse them with their bundled images first. When you want to change the artwork, connect either demo to your own workspace using the steps below.

The demos and SDK are open source in the AssetLib GitHub organization.

Connect a demo to your images.

1. Open the Assetlib console and choose Continue with GitHub. Use a GitHub account with a verified email.
2. Choose Create demo workspace, name it, then confirm Create & publish demo. Assetlib creates three image placements, adds sample artwork, and publishes the first release.
3. Choose Get SDK configuration, then Copy configuration.
4. In either demo, open Connect. Paste the complete JSON into Public SDK configuration and choose Connect and check release.
5. Return to the demo’s main screen. Its images now resolve through your workspace, with the bundled artwork kept as a fallback.

This is public connection information. It identifies your app and its verification key; it contains no password or private signing key. The demo remembers the connection on your device.

Publish a different image.

Use artwork with the same aspect ratio as its placement. Travel images use 4:3, such as 1200 × 900 px. The task illustration uses 3:2, such as 600 × 400 px.

1. In the console’s Assets section, choose Choose image and upload a still PNG, JPEG, WebP, or a supported static SVG. Assetlib keeps the original and prepares sizes for delivery: PNG and lossless WebP for artwork, compressed WebP for photos. Web can use the normalized SVG; native apps use raster versions.
2. Open Placements. Under Draft image, assign the uploaded image to travel.coast, travel.ridge, or tasks.garden.
3. Choose Publish release, review the confirmation, and confirm Publish release.
4. Return to the demo’s Connect screen and choose Check for updates. Open the image’s screen to see the new artwork.

You can also try the workflow with the seeded images: assign Alpine weekend to travel.coast, publish, and check for updates in the travel demo.

Inputs are limited to 4 MiB and 20 megapixels. Prepared images must fit within 1 MiB; the preview retains up to 8 MiB of image files per workspace. Updates arrive after a successful check and image download, not instantly on every device.

Restore an earlier version.

1. Open Releases in the console and find the earlier release.
2. Choose Restore this version, then confirm Restore and publish.
3. In the demo, choose Check for updates again and return to its image screen. The earlier artwork appears in the same running app.

Rollback publishes the earlier content with a new release number. It preserves the release history and leaves your draft placement bindings unchanged.

Bring a few placements into your app.

An engineer first adds the SDK, defines image placements and constraints, and supplies bundled fallbacks. That initial integration requires an app release. Compatible artwork changes in those connected placements can then be published separately; new screens, layouts, behavior, and placement contracts still require development.

• SDK source and installation — typed references, signed delivery, cache, and fallback behavior.
• Travel demo source — an Expo app with two connected travel images.
• Todo demo source — an Expo app with a connected task illustration.
• Swift SDK preview and iOS demo source — a native SwiftUI integration.
• Kotlin SDK preview and Android demo source — a native Compose integration.

The MIT-licensed SDK previews are available on GitHub. Follow each repository’s installation instructions and use matching versions. JavaScript packages are distributed through versioned GitHub releases, not npm or an agent marketplace.