Studio and previews

Open Studio in the notch to find work made for you. Its gallery includes saved previews, widgets, and builds still in progress. Select a tile to open it, or use the build control to begin something new.

Start with a small preview

Ask for one clear outcome, such as “Make a simple countdown card for Friday.” For connected data, first confirm that the required connection and execution access are available. Connecting an account alone does not establish that every tool can run in your build.

A preview can use simple blocks such as a heading, list, chart, clock, or countdown, or an interactive widget. Keep the first request small enough that you can check its behavior yourself.

Inspect before relying on it

Open the preview and review What it can do, Checks, and any Try it actions. Distinguish:

• Sample data: examples built into the preview, not current account information.
• Live data: results from an available connected service.
• Failed checks: evidence of a problem, not a successful empty result.

Do not treat a visually complete card as proof of a working integration. Try a read-only action and compare it with the original service.

Revise and find it again

Use Ask for changes for a focused revision, such as “Use larger numbers.” Check the task state if the old version remains visible while a revision runs. You can change an icon without rebuilding the whole preview using its icon control.

Settings → Apps → My Apps provides management controls, including removal for supported saved items. Keep any important result before removing it.

Building and revising uses AI services. A live preview can also contact connected apps; its data boundaries are not the same as those of a static local image.

Continue with Widget builder, App connections, and Background tasks.