Last verified: October 8, 2026
What You Can Now Do
Context Memo now lets you minimize widget X into a compact phone bubble that restores to the full card when tapped. Until now widget X had two states, open or closed, which on a narrow screen made every interaction a forced choice: keep the card in view and give up vertical space, or dismiss it and give up access. There is a third state now. The bubble occupies a fraction of the card's footprint, stays on screen while the page content behind it becomes fully readable, and expands back to the full card view on tap. The practical change is small and frequent. You stop closing widget X to read what is underneath it, and the people you point at the widget stop losing it by accident when they only wanted the screen back for a moment.
Where It Is in Context Memo
The minimize control sits on widget X itself rather than in a settings screen, so wherever widget X renders today, the control is on the card. Once you use it, the bubble appears in that same context and the restore action is on the bubble. This change is scoped to the widget layer of the product. Scanning, memo generation, and publishing behavior are unchanged by it, and nothing needs to be reconfigured at the account level before the new state is available.
How to Use It
- Open a surface where widget X is live and view it at mobile width or inside a compact layout. The full card renders exactly as it does today.
- Tap the minimize control on the card. The card collapses into the phone bubble and the content behind it is immediately visible and scrollable.
- Keep working on the page with the bubble in place. The widget stays accessible in its minimized state instead of being dismissed, so there is nothing to re-open or re-trigger.
- Tap the bubble when you want the widget back. The full card view restores.
- Test the sequence in your own narrow and constrained layouts before rollout, including embeds inside a fixed-width container, and confirm the bubble lands where you expect it relative to your own page chrome.
- Tell whoever owns the page template what changed. The close action still behaves as it always has, so anyone documenting the widget for internal users now has two different dismissal paths to describe.
Why We Built It
Customers were closing widget X entirely when what they actually wanted was to reclaim screen space on mobile or in compact layouts. That solved the space problem and created an access problem: the room came back, and the widget was gone for the rest of the session. Minimizing separates those two things, so reclaiming the screen no longer costs you the widget.