Widgetbook Cloud hosts a build for every commit and turns the scenarios you already wrote into automated checks on every pull request.
Widgetbook itself stays open source and free. Cloud is optional.
A code review shows a diff of the source, not the rendered UI. To judge a UI change, a reviewer has to check out the branch, run the app, navigate to the screen, and reproduce every state and configuration by hand. Most reviewers skip that and review only the code.
| Code review | Widgetbook Cloud | |
|---|---|---|
| Compares | Source between base and head commits | Snapshots and semantics trees between base and head builds |
| Setup per widget | None | None, scenarios are reused |
| Sign-off | Git provider | Reviews reported back as a commit status |
| Reviewer needs | The repo and a running app | A browser |
Cleantech company running 3 Flutter apps on a shared in-house design system.
- 0 visual bugs shipped since adopting Widgetbook Cloud.
- 20% time saved across designers and developers.
Smart access and IoT company serving over 40,000 clients in more than 40 countries, with seven production Flutter apps.
- 50% time saved for developers.
- Every UI change surfaced in the merge request.
Building UI in isolation
Lotum speeds up app development by building widgets in isolation.
1KOMMA5° on an in-house design system used across 3 apps.
LeanCode on a design system template shared with every new client.