Install guides
TellTide is one script tag for the web and one HTTP endpoint for everything else. Pick your platform below for the exact steps — where to paste, what plan you need, and how to verify your first submission lands in the private inbox.
One script tag before </body>. These guides show exactly where each platform hides its custom code box.
If you can edit your site’s HTML, you can collect structured user feedback in the next five minutes. TellTide is a single script tag — no build step, no npm package, no iframe wrangling.
See the install stepsWordPress powers everything from blogs to full storefronts, but its comment box is built for posts — not for bug reports or feature requests about your product. A feedback widget gives visitors a purpose-built place to tell you what is broken or missing.
See the install stepsWebflow sites look polished, but polish does not tell you which page confuses visitors or which feature your users wish existed. A feedback launcher closes that gap without touching your carefully built layout.
See the install stepsStore owners hear about problems too late — usually in a support email after the sale is lost. A feedback launcher on your storefront catches “the size chart is confusing” and “do you ship to Canada?” while the shopper is still on the page.
See the install stepsWix makes publishing easy; hearing from your visitors afterward is the part it leaves out. A feedback widget turns silent visitors into a steady stream of bug reports, ideas, and reviews you can actually act on.
See the install stepsSquarespace forms are fine for “contact us,” but they flatten every message into one email pile. Structured feedback — is this a bug, an idea, or a review? — needs a purpose-built entry point.
See the install stepsFramer sites ship fast and look sharp — the perfect stage for an early product. What they lack is a way to hear whether visitors actually understood your pitch or hit a broken link on launch day.
See the install stepsBubble apps are real products with real users — which means real bug reports and feature requests, usually scattered across DMs and email. Your feedback deserves the same structure as the app you built.
See the install stepsA Carrd one-pager is often the first public face of an idea. The visitors it attracts are exactly the people whose objections and questions you need to hear before building more.
See the install stepsGhost publications live and die by member trust, and members constantly have small reactions — a broken archive link, a topic request, praise worth quoting. Comments catch some of it; most evaporates.
See the install stepsSingle-page apps and meta-frameworks: load the script once in your shell or layout and the launcher follows every route.
React apps re-render constantly; your feedback widget should not. TellTide mounts itself outside your component tree from a single script tag, so there is no wrapper component, no context provider, and nothing to memoize.
See the install stepsNext.js gives you layouts that wrap every page — which is exactly where a feedback widget belongs. One script in the root layout and the launcher follows users through server components, client components, and route transitions alike.
See the install stepsVue’s single-file components keep your app tidy; a feedback widget should not need one. TellTide mounts from a plain script tag in index.html — no plugin registration, no app.use(), nothing reactive to manage.
See the install stepsNuxt manages your document head for you, so third-party scripts belong in its config — not pasted into templates. TellTide registers cleanly through app.head, keeping your setup declarative and SSR-safe.
See the install stepsAngular apps tend to be serious, long-lived products — the kind whose users file real bug reports if you give them somewhere to do it. TellTide adds that channel without an Angular module, service, or dependency injection entry.
See the install stepsSvelte compiles your components away; TellTide never needed to be one. The widget loads from the app template — SvelteKit’s app.html — so it ships zero bytes in your compiled bundle.
See the install stepsAstro strips JavaScript by default — great for speed, inconvenient for a widget that is JavaScript. The fix is Astro’s is:inline directive, which tells the compiler to leave your script tag exactly as written.
See the install stepsThe widget is web-only, so native apps post JSON to the TellTide API instead — same inbox, same roadmap.
Mobile users rarely email support — they either churn quietly or leave a public store review you cannot triage. An in-app feedback form, wired to TellTide’s HTTP API, catches those signals privately first.
See the install stepsFlutter renders its own pixels, so a web feedback widget was never going to fit. What fits is a small Dart form that posts straight to TellTide’s feedback endpoint — same inbox, same roadmap, native feel.
See the install stepsDesktop users hit desktop-shaped bugs — window states, file paths, OS quirks — that web analytics never see. A feedback command in your Electron app routes those reports somewhere more useful than a GitHub issue from a confused user.
See the install stepsThe App Store review box is public, rate-limited by Apple’s prompts, and impossible to triage. Your TestFlight testers and production users both need a direct line that lands in an inbox you control.
See the install stepsPlay Store reviews arrive without context and often without a way to follow up. An in-app feedback screen posting to TellTide captures the same voice with the detail — screen, app version, device — that makes it fixable.
See the install steps