android-widgets-shortcutslisted

# Android Widgets and Shortcuts ## Core Principles - External entry points should open focused, useful flows. - Widgets and shortcuts should reflect stable app capabilities, not temporary experiments. - Keep business logic in repositories/use cases, not in widget or shortcut handlers. - Treat every external entry point as an app navigation boundary. - Updates should be intentional and battery-aware. --- ## When to Use Widgets Good widget use cases: - glanceable status - quick capture actions - simple list snapshots - media or task controls - user-personalized summary surfaces Bad widget use cases: - trying to replicate the full app UI - overly interactive complex forms - constantly refreshing high-cost data without strong user value Widgets should be lightweight and high-signal. --- ## Shortcut Types Common shortcut categories: - static shortcuts for core destinations - dynamic shortcuts based on recent/frequent user actions - pinned shortcuts created explicitly by the user Use shortcuts for actions that are: - frequently repeated - clear out of context - safe to open from outside the app's current state --- ## Navigation Mapping Widgets and shortcuts should map into the same internal destination model as deep links and notifications when possible. ```text widget/shortcut tap -> internal destination -> app navigation ``` This keeps routing consistent. See the **android-deep-links** and **android-navigation** skills. --- ## Data Loading Strategy Widget data