How a Glance widget is made.

You create a widget and pin it. That slot stays on the Home Screen. Behind it, Glance stores a feed — the live snapshot the widget reads.

The plan cap is on feeds. In the product we call them widgets.

A layout is saved chrome: a JSON tree Glance renders natively in small, medium, or large. Bindings like {{revenue}} become the fields later updates fill.

Reuse a layout when the face should stay the same. Or send a new tree with the update — UI on Demand — and skip a saved layout. That path is on Pro and Power. It does not spend a layout slot.

Layouts follow a short design language: glanceable, native type, one hero. The full rules are in Layout Language.

The feed is what the widget shows right now. Every update writes here — a saved layout and UI on Demand use the same endpoint and the same rate limits.

Push as often as the plan allows. Glance keeps a short history of events.

Something has to write the feed. These are peers, not a stack you have to climb.

• Glance AI — chat in the app. It can design a layout, connect a source, and set an automation. Glance AI
• Automations — Glance pulls on a schedule from connected accounts or the device. Google, GitHub, Weather, Calendar, Reminders. Automations · Integrations
• MCP — ChatGPT, Claude, or Cursor keep their apps and push into Glance. Connect MCP
• API — a write key and POST, including Zapier, Make, and Shortcuts. Dynamic ingest

Two kinds of AI, one Home Screen. Glance AI lives in the app. MCP is the agent you already use.

Keep it private. Share an unlisted link. Or publish and let people subscribe from Discover or a public page.

Pro and Power can set a custom URL, like glance.cool/your-name. Discover & public widgets