Widgets display information without opening the application. This creates a wider display surface and a separate refresh lifecycle.
Evaluation approach
Send only suitable summary data. Define cleanup for logout, permission changes and stale caches.
Application example
A financial widget may offer a limited user-selected summary instead of full account details. Previous-account data must not remain for another user.
Limits and considerations
Locking the main app may not remove a widget's existing copy.
Why cache ownership matters
A widget can keep showing its last update. Associate cached summaries with account identity and validity. On logout or switching, update the widget's data source as well as the main application's lists.
Checks and decisions
- Reduce visible data
- Clear stale caches
- Test account changes
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.