Decide what one tap should do
Choose an opening action to launch a destination. To complete a task or add an amount to a goal, select the corresponding data operation. Showing dynamic content does not configure a tap action, and a circular graphic may simply be decoration.
Start with one clear purpose, such as opening a reading record, and verify it before adding more actions. A button label should describe its actual effect. A “Check in” area that only opens the app may make someone think an entry has already been recorded.
Choose the area, action and record
- Select the layer or container that should respond, then open Interaction in the editor.
- Inspect its current action and choose a type offered by the panel.
- For an app or link, check the destination. For a data operation, check the specific task or daily goal and its parameters.
- Complete any required state or data-source binding before testing.
See Set tap actions for the controls. To add 5 pages to a reading goal, check the goal identity, unit and increment. Changing a button label to “+5” does not change the operation’s parameters.
Recheck action targets after copying a design. Showing a new goal name does not establish that the button now operates on that goal. Several designs may still update the same record. See Personal content and designs.
Inspect the hit area in the editor
Open Test in the interaction tools and tap the target on the canvas. Inspect the layer and action that were hit. Try the text center, its edge and nearby empty space to check whether the active area matches your intent.
Open in the test actually follows its destination. Other actions are simulated and do not update real records. After a successful simulation, leave testing, save and verify the supported home screen behavior. Repeated taps in simulation will not create a real entry.
“No independent action” does not always mean no response: a parent container may supply an action. If a small button triggers the whole card, inspect parent actions, overlapping layers and hit areas. See Editor basics for layer selection.
Verify the saved design on the home screen
Save and prepare the design, then select it using the iPhone setup guide or Android home screen steps. Check download availability for supported releases. Perform one action on a recognizable test record, then check its real state or value in the app.
For an “Add 5 pages” action, note the daily total beforehand, tap once, then open the goal details to check the change. If the home screen has not changed yet, inspect the real record before tapping again and accidentally adding more entries. Follow Refresh troubleshooting when needed.
iOS interactive widgets can provide buttons or toggles, but an app must implement the action. Platform capability does not mean every MuseScreen design, size or placement performs the same operation. Check Lock Screen behavior separately; an editor test cannot establish that result.
Troubleshoot missing or incorrect responses
- Check that the home screen uses the design you just saved.
- Inspect the hit layer and action in the editor, including parent and overlapping areas.
- Check that the bound record still exists, the target is valid and parameters are complete.
- If an external app will not open, check that it is installed and its link is valid. A failed link does not establish a successful data update.
If the cause is still unclear, include the system version, widget placement, tap area and expected action in reproducible feedback. For record checks, see the To-do list guide and Habit tracker guide.
Frequently asked questions
Why did a successful editor test not increase my goal total?
Apart from actually opening destinations, editor tap tests simulate actions. Leave testing, save the design and verify supported home screen behavior, then check the real record in the app.
Why does tapping text run the whole card’s action?
A parent container may supply the action, and overlapping layers can affect the hit area. Use the tap test to identify the actual target before adjusting its layer or container.
Does changing the displayed name change the action’s record?
Not necessarily. Check the display field and action target separately, especially after copying designs or switching personal content. A button label is not its record binding.
Can every widget run actions directly on the home screen?
No. Behavior depends on the design, action, placement and installed version. Some areas only open the app. Use the available configuration and actual result as the guide.
Official references
Sources checked: 2026-10-18. After a system update, follow the official instructions and device interface for your version.