The problem this product is built around
A custom widget is not a tiny app screen. It has fixed sizes, limited refresh opportunities and a glance-time reading task. Starting with decoration often produces a card with no hierarchy or empty state.
How WidgetCraft solves it
WidgetCraft stores the design as a document element tree with data providers and actions. The creator previews the same artifact the extension interprets, so the target size is checked before installation. Open the WidgetCraft product page for current availability and plan details.
A practical workflow
- Choose size from the information you need to read.
- Build primary value before secondary decoration.
- Define loading and empty states first.
- Preview, install and test a refresh before adding more.
What to check before you trust the result
WidgetKit controls size, refresh frequency and APIs. A custom document cannot bypass those rules; design for the system you have.
Who this workflow is for
Use it when templates cannot express your needed information hierarchy.
Go deeper
For detailed mechanics, read Use custom editor, Understand first setup.
WidgetCraft is useful when it shortens a repeated decision while keeping evidence, assumptions and stopping points visible. Try WidgetCraft.