> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/play/properties/interactions/gestures/single-tap.md).

# Single Tap

Trigger an action when the user taps or clicks a layer.

<figure><img src="https://3019081569-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZBycFFNxrdS0X9OsGtmT%2Fuploads%2Fgit-blob-cf85176d2089b1df2d3a3363d8af4e292ef56632%2Fgestures-single-tap.png?alt=media" alt="The Interaction Properties popup with the Single Tap gesture selected"><figcaption></figcaption></figure>

The **Single Tap** gesture runs an action when the user taps a layer on mobile or clicks it on desktop. It is the default gesture for every new interaction and the right choice for buttons and CTAs.

This is useful for patterns like:

* Buttons and CTAs
* Tap-to-continue screens
* Tappable items in a game or story

### How it Works

Single Tap has one **Action** slot.

The action fires when the user **lifts their finger** (or releases the mouse button), not when they first press down. A tap counts when:

* The press starts on the layer.
* The finger moves only a short distance before lifting. A longer movement is treated as a swipe or drag, and the tap is ignored.
* Only one finger is on the screen. A second finger cancels the tap.

Lifting the finger outside the layer still counts, as long as it has not moved too far.

If the layer has a [Press Effect](https://help.craftsmanplus.com/play/properties/interactions/press-effect.md), it shows while the finger is down and clears on release.

### Single Tap and CTAs

Single Tap is the only gesture that counts as compliant for [Launch URL](https://help.craftsmanplus.com/play/general/actions/launch-url.md), [Launch App Store](broken://pages/BceD3nnJOe4CewmqequV) and [Call Number](https://help.craftsmanplus.com/play/general/actions/call-number.md). Some devices block click-outs that come from any other gesture. If one of these actions is wired to anything else, PLAY shows a **Non-compliant CTA Link** suggestion in the [Project Score](https://help.craftsmanplus.com/play/export/project-score.md).

### Where You Can Use It

Single Tap is available on every layer type that supports interactions, including Images, Text, Shapes, Videos, Sequences, Groups and [Hotspots](https://help.craftsmanplus.com/play/layers/hotspots.md).

### Setting Up Single Tap

{% stepper %}
{% step %}

### Select a layer and click **+** in the Interactions section.

{% endstep %}

{% step %}

### Leave the **Gesture** set to **Single Tap.**

New interactions use Single Tap by default.
{% endstep %}

{% step %}

### Choose an **Action.**

{% endstep %}

{% step %}

### Preview and tap the layer to test it.

{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Avoid putting Single Tap and [Double Tap](https://help.craftsmanplus.com/play/properties/interactions/gestures/double-tap.md) on the same layer. A double tap is two single taps, so the Single Tap action runs twice and the Double Tap action runs as well.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.craftsmanplus.com/play/properties/interactions/gestures/single-tap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
