1# Developing a Fun-based Widget 2 3Currently, fun-based widgets support mini-games developed with quick games. This kind of widget is in the inactive state by default. When a user taps the widget, it switches to the active state and the game begins. During the game, users can tap the pause icon to pause the game. In the paused state, users can resume the game by tapping the resume icon or end the game by tapping the stop icon. 4## Basic Concepts 5 6Fun-based widgets can be in one of the following states: active (game running), paused (game paused), and inactive (game ended). 7 8### Active State 9 10In this state, the widget UI is carried by the mini-game page developed by the widget provider using quick games. The system supports an "overflow" effect, allowing game content to render beyond the widget rendering area. 11 12**Figure 1** Fun-based widget in the active state 13 14 15 16### Paused State 17 18In this state, the widget UI is carried by the content in **widgetCard.ets** of the widget provider. Meanwhile, the system renders the resume and stop icons on the widget by default. 19 20**Figure 2** Fun-based widget in the paused state 21 22 23 24### Inactive State 25 26In this state, the widget behaves like a common widget, complying with the existing widget development specifications. The widget UI is carried by the content in **widgetCard.ets**. 27 28**Figure 3** Fun-based widget in the inactive state 29 30 31 32## Constraints 33 341. When a user interacts with a widget, for example, by tapping, long-pressing, or dragging, the interactive target area is always the same size as the widget rendering area. Even if the animation rendering area extends beyond the widget rendering area, the excess part is only used for UI display and does not respond to interactive events. 352. In the active state, interactive events within the widget's rendering area are responded to by the mini-game page developed by the widget provider. In other states, interactive events are responded to by the common widget developed by the widget provider. 363. At a time, only one widget can be in the active or paused state for fun-based interactions. When a user taps a widget to activate it, all other fun-based widgets are automatically switched to the inactive state. 374. For details about other design specifications and restrictions, refer to how to develop a creative widget. 38 39## How to Develop 40 41For details about how to develop game content, refer to how to develop a game widget. 42 43For details about on-device widget configuration and development, see [the configuration of fun-based widgets](arkts-ui-widget-configuration.md#funinteractionparams-field). 44
