Ship the bricks
Register trusted Duck components inside your Flutter app. Your code defines what the remote canvas is allowed to render.
Dynamic UI Components Kit for Flutter
Build once.Reconfigure anytime.
Compose interfaces from app-approved Flutter components, publish JSON canvases, and update supported views without waiting on a new store release.
1.0.2 current package98% test coverage6 Flutter platforms
APPROVED COMPONENTS · LIVE CONFIGURATION
Flutter-nativeJSON canvasesCustom componentsPublic libraryOTA configuration
How it clicks together
Three pieces. One controlled workflow.
Build the canvas
Arrange public or custom components in Duck Builder, then save the resulting interface as structured configuration.
Update the view
Publish a canvas update and let the app render the new supported composition—without rebuilding the whole application.
Start with one dependency
Drop Duck into your Flutter project.
Initialize the package with your component registry, then render a saved canvas wherever your product needs a configurable view.
Read the package documentationpubspec.yamlDUCK / 1.0.2
dependencies:
duck: ^1.0.2Designed with boundaries
Remote configuration, not remote code.
Your app owns the component types.
Duck composes components your shipped application already understands.
New capabilities still require a release.
Add a new component type through the normal app update process, then configure it remotely.
Use public building blocks or bring your own.
Start from Duck’s public library or register product-specific Flutter components.
Build · Arrange · Publish