A finished looking end card can still leave its most important question unanswered: what happens when someone chooses an action?

Clickability is one property. The result promised by the label is another. Replay and Install are a useful pair because they imply different routes out of the same final screen.

Two branches in a teaching prototype

We built an owned local demo that starts on a completed end card. It is a teaching example, not a client delivery, a store integration or a user test.

Replay returns the demo to its starting position and resets its move count. Completing the small demo brings the end card back. That is a local state change.

Install takes the other branch. In this prototype, it opens an explicitly labelled destination preview and leaves the completed demo state intact. There is no connected store, download or installation. The preview makes the intended handoff visible without pretending the live integration has been tested.

Review the promise, not only the response

A useful acceptance note pairs the label with its intended action and resulting state. For Replay, that includes what resets and where the next attempt begins. For the install path in a real delivery, it includes the actual destination and the integration requirements agreed for that environment.

Our local preview proves only the separation of the two prototype branches. It cannot certify a store URL, a network SDK or device behavior. Those belong to the real implementation and its own checks.

Priority is a separate decision

Showing two actions does not establish that they should have equal visual weight. It also does not establish that one should always dominate. Their priority depends on the brief and intended next step.

Keeping priority separate from behavior makes the review more precise. The team can discuss which action should be prominent without losing the requirement that each action fulfills its own label.

For a production partner, the deliverable is more than a picture of the final screen. It includes the intended transition after each choice, plus a clear account of what has and has not been tested.

Follow both end card actions and check that each matches its label.