Studio Widgets

Summary

Studio Widgets are lightweight panels. In the current implementation they belong to Desktop Runtime. They are not normal app windows and they are not automatically available in every Studio Engine.

The current v0 implementation includes mock Weather and Calendar Widgets on Desktop Runtime. They sit in the lower-left widget rail so they do not block the upper desktop folder area. They do not call weather or calendar APIs, request location, connect accounts, or persist widget layout.

Boundary

• Widgets belong to Desktop Runtime unless a future Studio Engine explicitly supports them.
• Widgets should not replace app windows.
• Widgets should not be registered as full apps unless they also have a launchable app surface.
• Widgets should not sit above the app window layer in a way that blocks normal window focus.

Future Sources

Widget data can eventually come from:

• connectors;
• backend APIs;
• browser APIs with explicit permission;
• mock seed data;
• Alma summaries;
• local app state.

Candidate Widgets

• Weather
• Calendar
• Tasks
• System status
• AI suggestions
• Connector summaries
• Support queue
• Community signals

Roadmap

The first implementation is intentionally small: Weather uses mock Madrid data and Calendar uses a mock agenda. The next step is a widget registry with placement, visibility, data source, and permission metadata.