HeyTappr for
HeyTappr for developers
You get asked to build product tours, and they rot the moment the DOM changes. HeyTappr is one script tag on web — src https://cdn.tappr.app/embed.js with a data-tapprid attribute — and after that, guides are authored and maintained in a console, not in your codebase.
Install once, then stay out of the loop
Web install is a single script tag; Android is a Gradle dependency with a small Kotlin API. Guides — intents, URL patterns, copy, and a CSS selector per step — live in the console, so new guides need no deploys from you.
Sane security defaults
Web origins are allowlisted per workspace, so the embed only runs on domains you approve. Admin actions use a workspace key that can be rotated if it is ever exposed.
Breakage is visible, not silent
If a refactor changes the DOM and a selector stops matching, the guide shows up in the analytics needs-attention list. Whoever owns the guide fixes the selector in the console — no emergency ticket to engineering required.
See it in your product
A demo takes fifteen minutes: HeyTappr guiding real users through a real interface.
Questions teams ask
- What exactly does the web install involve?
- One script tag with src https://cdn.tappr.app/embed.js and a data-tapprid attribute identifying your workspace. On Android, you add a Gradle dependency and use a small Kotlin API.
- How are admin operations authenticated?
- Admin actions use a per-workspace key that can be rotated, and web origins are allowlisted per workspace so the embed only operates where you allow it. Email shrit@HeyTappr.com to book a demo.
More use cases
Or just email us and see it in your own product.