In-app Hints — Contextual Help Anchored to Any UI Element

What are in-app hints?

In-app hints, also called contextual help indicators, are persistent UI elements — icons, dots, pulses, or NEW badges — anchored to specific elements inside a product. Each hint opens a popover with a short explanation, a link, or a button that starts a guided tour when a user clicks.

Unlike modals, hints don't interrupt. Unlike browser-native tooltips, they're audience-targeted, frequency-capped (show once per visitor), themed to your brand, and measured per-hint.

This is what Nielsen Norman Group calls a pull revelation — help that responds to user intent rather than interrupting it. Push revelations (like uninvited modals) get dismissed. Pull revelations (like hints) get clicked.

Why your best features go unnoticed

You shipped a feature on Friday. Monday morning, support tickets pile up asking where to find it. The changelog email mostly went unopened. The launch modal was dismissed in seconds. Your best work is invisible — not because users don't care, but because nothing on the page tells them it exists.

Tooltip libraries don't fix this. They're DOM hover-effects with no audience targeting, no frequency capping, and no analytics. You can't show one to enterprise users only. You can't see who clicked it. You can't run two variants and measure which one worked.

In-app hints close that gap. A ? icon next to a confusing form field. A NEW badge on the menu item you just shipped. A pulsing dot on a feature nobody finds. Each one waits on the page until users click, then opens a popover with the next step — targeted, capped, themed, and measured. Hints work alongside feature adoption tours and user onboarding flows, not against them.

This isn't theory. Nielsen Norman Group's research finds that tutorial walls and modal takeovers get skipped by most users, while help anchored to specific UI elements earns higher engagement and retention.

What in-app hints can do

Five indicator styles

Question mark, info, dot, pulse, or NEW badge. Match the visual weight to the moment — a quiet ? for a form field, a pulsing dot for a menu item users miss, a NEW badge for a launch.

CTA actions on click

Each hint opens a popover with a single action: link to a doc or external URL, start one of your product tours, or fire a custom event your app handles however it wants.

Targeting and frequency capping

Show by plan, role, URL, or any custom attribute you pass via the embed. Cap to once per visitor when one chance is enough. Same rules engine as tours.

No-code visual editor

Point and click to anchor a hint to any element. Live preview as you type. Publish to selected domains when you're ready — no engineering handoff.

Theme overrides per hint

Match your brand colors, popover styling, and indicator sizing (8–96px). Inherit defaults from your project theme, override per hint when a moment needs to stand out.

Per-hint analytics

Track viewed, opened, dismissed, and CTA-clicked events for every hint. See which hints drive action and which get ignored — without wiring up your own analytics.

How it works

1. 1

   Add a hint in the dashboard

   Start with a name and a URL pattern (or wildcard for everywhere). No code required — hints live in the same dashboard as your tours.

2. 2

   Anchor it to any element

   Open the visual element picker on your live site, or paste a CSS selector. The hint will follow that element across SPA navigations.

3. 3

   Pick an indicator and a CTA

   Choose from five indicator styles. Optionally add a popover CTA: link to a URL, start a tour, or dispatch a custom event your app handles.

4. 4

   Publish to your domain

   Roll out to the domains you choose. Hints appear for users who match your targeting rules — instantly, no app deploy needed.

In-app hint examples

Hints vs. tours vs. announcements

StepsKit ships three in-app surfaces, each for a different job. The right pick is rarely a guess — it depends on whether the user needs a guided sequence, a broadcast, or persistent contextual help.

Pick tours when there's a workflow to learn — a multi-step onboarding flow, a feature with a sequence of actions, a setup wizard for first-time users. Tours guide a user from A to B in order.

Pick announcements when a launch affects everyone and you need attention now. Banners and modals interrupt — use them sparingly, but use them when broad reach matters more than persistence.

Pick hints when users should find help in context — at the moment of confusion, next to the field they're filling, beside the menu item they keep missing. Hints don't interrupt. They wait until the user is ready to ask.