App Clip and Tap-to-Interact
Learn why Quote/0 opens content through the Dot. App or App Clip, and what to check when tap-to-interact cannot launch.
Why tap-to-interact opens the App Clip / App
Quote/0 tap-to-interact does not open a fixed web page. It opens a content handling entry point.
Because the content currently shown on the device can change, and different content types need different presentation methods, the Dot. App or App Clip needs to retrieve the current content, perform unified permission checks, and choose the appropriate way to open it.
NFC launches the entry point, not the content itself
Quote/0 has an NFC module in the blank area on the right side. When a phone is brought near the device, NFC triggers a fixed entry point that opens the Dot. App or App Clip.
This entry point does not directly store the current screen content, nor does it decide whether the final result should open a web page, text, photo, or third-party app.
The App retrieves current content and checks permission
After tap-to-interact opens the App, the App retrieves the content associated with the current device screen.
This keeps the NFC entry point stable while allowing the opened content to change with the device's current state. Even if the NFC tag itself does not change, the final content can still update based on what the device is showing.
Before showing content, the App performs a unified permission check. This permission check is not specific to one content type; it is a base step in the tap-to-interact flow.
After permission passes, the App chooses the display method based on the content type.
Different content needs different opening methods
| Content type | Opening method |
|---|---|
| News or article content | Open a web page |
| Third-party app content | Jump to the corresponding app |
| API or plain text | Display as plain text |
| Structured text | Display as Markdown |
| Image content | Display as a photo |
If NFC directly opened a fixed web page, it could not adapt to these content forms or complete unified permission checks before opening.
This design also keeps power consumption low
Quote/0 can keep NFC as a low-power trigger entry point instead of keeping the device powered or online just for tap-to-interact.
Content retrieval, permission checks, and display method selection are handled by the App, while the device itself can keep the low-power behavior of an e-ink screen and battery mode.
How to use tap-to-interact
When you are interested in the current content on the device, simply use an NFC-enabled phone to lightly tap the blank area on the right side of the device to quickly launch the Dot. App for viewing or actions.
During "Tap", the device does not need to wake up or be connected to power.
To activate and use Dot. series devices or features, please install the Dot. App first.
Compatibility
- iOS:
iOS 17and later - Android:
Android 12Land later - HarmonyOS:
- Versions
4.0and below: Can be installed directly - Versions
HarmonyOS NEXTand above: Can be installed using Droitong
- Versions
Why the App Clip / App may not launch
iPhone
If tap-to-interact fails to launch the App Clip on iPhone, try locking your iPhone, unlocking it again, then move the iPhone in an upward motion and approach the right side of the device. This typically triggers the App Clip correctly.
This issue is generally caused by iOS system limitations. When you attempt to tap multiple times from the same App Clip source, iOS may block subsequent launches. Only after locking the screen and approaching again with a more pronounced movement will iOS invoke the App Clip again.
If you are using an iPhone intended for Mainland China, verify that NFC is enabled in Settings → General.
Android
If tap-to-interact does not redirect correctly on Android, ensure that the Dot. App is installed, NFC functionality is enabled, and you are aware of your Android device's NFC sensing area location.
Bring the NFC sensing area close to the blank area on the right side of the device to invoke the content.
Did this solve your problem?
Join our community