What Boosthis adds to your app

For the developer deciding whether to install, and the reviewer asked to approve it. Last updated 2026-09-25.

A Boosthis kit runs inside your own application, on your own domain. Two kinds of thing arrive with it: something your end users can see, and addresses your app starts answering. This page lists both, for every runtime we ship, so the decision is yours before you ship rather than a discovery afterwards.

The same list for your runtime is in the install guide the kit arrives with. Both are rendered from one source, and a check fails our build when a kit mounts an address this page does not name, or names one the kit no longer has.

The visible element

The floating bubble is on by default in every environment, including production. BOOSTHIS_BUBBLE set to 0 hides it and the kit carries on measuring; BOOSTHIS_DISABLED stops the kit altogether. Each name is read from the environment where this runtime has one, and otherwise from a value of the same name on the host.

Kits that draw it: Node.js, Python, Go, Java, PHP, Ruby, .NET, Rust, Elixir, Browser / web, React Native / Expo, Flutter, Swift / iOS, Kotlin / Android.

Kits that show your users nothing at all: Edge / V8 isolates. Each says why in its section below.

Addresses anyone can reach

Most of what a kit mounts answers local requests only. A few are deliberately open, because the bubble is injected into your own pages and polls them from wherever your visitor is — a gate there would blank the bubble in production, which is where it is worth having. An open address on your production domain is a thing you are entitled to know about before it is there, so each one below says what it returns, why it is open, and what it deliberately does not contain.

Every open address is listed in its kit's section. None of them carries a credential, a route or screen label, a URL, a raw sample, or anything about one of your visitors.

Kits that mount no address at all: Browser / web, React Native / Expo, Flutter, Swift / iOS, Kotlin / Android, Edge / V8 isolates.

Every kit, in full

Node.js
Python
Go
Java
PHP
Ruby
.NET
Rust
Elixir
Browser / web
React Native / Expo
Flutter
Swift / iOS
Kotlin / Android
Edge / V8 isolates

Node.js

What your users see

A floating bubble in the corner of the page: a score, a rating word, and a panel it opens.
Where: Injected into HTML pages this service itself serves. Pages served by a separate frontend are a different process and get nothing.
The floating bubble is on by default in every environment, including production. BOOSTHIS_BUBBLE set to 0 hides it and the kit carries on measuring; BOOSTHIS_DISABLED stops the kit altogether. Each name is read from the environment where this runtime has one, and otherwise from a value of the same name on the host.

What your app starts answering

/_boosthis Public

The kit's own page: static markup that draws the panel by fetching the panel read below. Both spellings are the same page, because a developer types one or the other and neither habit should 404.

Who can reach it: anyone who can reach your app.

Why it is open: It is the page the bubble links to, opened from any page the app serves, so a gate here would 403 a developer whose bubble works. The markup is static — it holds no measurements to protect.

What it does not contain: No measurements, no route or screen labels, no credential: every number on it arrives afterwards from the panel read.
/_boosthis/ Public

The kit's own page: static markup that draws the panel by fetching the panel read below. Both spellings are the same page, because a developer types one or the other and neither habit should 404.

Who can reach it: anyone who can reach your app.

Why it is open: It is the page the bubble links to, opened from any page the app serves, so a gate here would 403 a developer whose bubble works. The markup is static — it holds no measurements to protect.

What it does not contain: No measurements, no route or screen labels, no credential: every number on it arrives afterwards from the panel read.
/_boosthis/pulse Public

One coarse reading for the bubble itself: a score, a rating word, and how many samples it came from.

Who can reach it: anyone who can reach your app.

Why it is open: The bubble is injected into the app's own pages and polls this from whichever page the visitor is on, so it cannot be limited to local requests without the bubble going blank in production — which is where it is most worth having.

What it does not contain: No route or screen labels, no durations, no per-route rows, no credential, nothing about a visitor.
/_boosthis/panel Public

What the bubble's panel draws: per-meter scores, rating words, meter labels and the numeric captions beside them.

Who can reach it: anyone who can reach your app.

Why it is open: Same reason as the pulse read above — the panel opens on the visitor's page, not on the developer's machine.

What it does not contain: No route or screen labels, no URLs, no raw samples, no install token and no account credential. The account read that does carry one is local-only, below.
/_boosthis/account Local only

The sign-in context the bubble's account card needs, including the token that claims this install.

Who can reach it: local requests only — nothing opens it remotely.
/_boosthis/status Local only

The standalone “is Boosthis working?” page — the surface a back-end service with no UI has instead of a bubble.

Who can reach it: local requests only — nothing opens it remotely.
/_boosthis/dev Local only

This kit's detailed local view: the per-route table, learned budgets, recent samples and the “Connect your AI” card.

Who can reach it: local requests only (your allowRemote opt-in can open it).
/_boosthis/healthz Local only

Whether the kit is running, as JSON.

Who can reach it: local requests only (your allowRemote opt-in can open it).
/_boosthis/summary Local only

Per-route timings and ratings, as JSON.

Who can reach it: local requests only (your allowRemote opt-in can open it).
/_boosthis/recent Local only

Recent individual samples, as JSON.

Who can reach it: local requests only (your allowRemote opt-in can open it).
/_boosthis/budgets Local only

The budgets this app has learned per route, as JSON.

Who can reach it: local requests only (your allowRemote opt-in can open it).
/_boosthis/connect Local only

The install id, a read-only token and a paste-ready AI config.

Who can reach it: local requests only — nothing opens it remotely.

Python

What your users see

A floating bubble in the corner of the page: a score, a rating word, and a panel it opens.
Where: Injected into HTML pages this service itself serves. Pages served by a separate frontend are a different process and get nothing.
The floating bubble is on by default in every environment, including production. BOOSTHIS_BUBBLE set to 0 hides it and the kit carries on measuring; BOOSTHIS_DISABLED stops the kit altogether. Each name is read from the environment where this runtime has one, and otherwise from a value of the same name on the host.

What your app starts answering

/_boosthis Public

The kit's own page: static markup that draws the panel by fetching the panel read below. Both spellings are the same page, because a developer types one or the other and neither habit should 404.

Who can reach it: anyone who can reach your app.

Why it is open: It is the page the bubble links to, opened from any page the app serves, so a gate here would 403 a developer whose bubble works. The markup is static — it holds no measurements to protect.

What it does not contain: No measurements, no route or screen labels, no credential: every number on it arrives afterwards from the panel read.
/_boosthis/ Public

The kit's own page: static markup that draws the panel by fetching the panel read below. Both spellings are the same page, because a developer types one or the other and neither habit should 404.

Who can reach it: anyone who can reach your app.

Why it is open: It is the page the bubble links to, opened from any page the app serves, so a gate here would 403 a developer whose bubble works. The markup is static — it holds no measurements to protect.

What it does not contain: No measurements, no route or screen labels, no credential: every number on it arrives afterwards from the panel read.
/_boosthis/pulse Public

One coarse reading for the bubble itself: a score, a rating word, and how many samples it came from.

Who can reach it: anyone who can reach your app.

Why it is open: The bubble is injected into the app's own pages and polls this from whichever page the visitor is on, so it cannot be limited to local requests without the bubble going blank in production — which is where it is most worth having.

What it does not contain: No route or screen labels, no durations, no per-route rows, no credential, nothing about a visitor.
/_boosthis/panel Public

What the bubble's panel draws: per-meter scores, rating words, meter labels and the numeric captions beside them.

Who can reach it: anyone who can reach your app.

Why it is open: Same reason as the pulse read above — the panel opens on the visitor's page, not on the developer's machine.

What it does not contain: No route or screen labels, no URLs, no raw samples, no install token and no account credential. The account read that does carry one is local-only, below.
/_boosthis/account Local only

The sign-in context the bubble's account card needs, including the token that claims this install.

Who can reach it: local requests only — nothing opens it remotely.
/_boosthis/status Local only

The standalone “is Boosthis working?” page — the surface a back-end service with no UI has instead of a bubble.

Who can reach it: local requests only — nothing opens it remotely.
/_boosthis/dev Local only

This kit's detailed local view: per-route table, recent samples, the rule checklist and the “Connect your AI” card.

Who can reach it: local requests only (your allowRemote opt-in can open it).
/_boosthis/api/context Local only

The project context an AI client reads, as JSON.

Who can reach it: local requests only (your allowRemote opt-in can open it).
/_boosthis/api/rules Local only

The Python rule checklist, as JSON.

Who can reach it: local requests only (your allowRemote opt-in can open it).
/_boosthis/api/rules/ Local only

One rule in full, by id (a prefix route).

Who can reach it: local requests only (your allowRemote opt-in can open it).
/_boosthis/api/samples Local only

Recent individual samples, as JSON.

Who can reach it: local requests only (your allowRemote opt-in can open it).
/_boosthis/api/summary Local only

Per-route timings and ratings, as JSON.

Who can reach it: local requests only (your allowRemote opt-in can open it).
/_boosthis/api/match Local only

A POST read that matches submitted code against the rules.

Who can reach it: local requests only (your allowRemote opt-in can open it).
/_boosthis/api/connect Local only

The install id, a read-only token and a paste-ready AI config.

Who can reach it: local requests only — nothing opens it remotely.

Go

What your users see

A floating bubble in the corner of the page: a score, a rating word, and a panel it opens.
Where: Injected into HTML pages this service itself serves. Pages served by a separate frontend are a different process and get nothing.
The floating bubble is on by default in every environment, including production. BOOSTHIS_BUBBLE set to 0 hides it and the kit carries on measuring; BOOSTHIS_DISABLED stops the kit altogether. Each name is read from the environment where this runtime has one, and otherwise from a value of the same name on the host.

What your app starts answering

/_boosthis Public

The kit's own page: static markup that draws the panel by fetching the panel read below. Both spellings are the same page, because a developer types one or the other and neither habit should 404.

Who can reach it: anyone who can reach your app.

Why it is open: It is the page the bubble links to, opened from any page the app serves, so a gate here would 403 a developer whose bubble works. The markup is static — it holds no measurements to protect.

What it does not contain: No measurements, no route or screen labels, no credential: every number on it arrives afterwards from the panel read.
/_boosthis/ Public

The kit's own page: static markup that draws the panel by fetching the panel read below. Both spellings are the same page, because a developer types one or the other and neither habit should 404.

Who can reach it: anyone who can reach your app.

Why it is open: It is the page the bubble links to, opened from any page the app serves, so a gate here would 403 a developer whose bubble works. The markup is static — it holds no measurements to protect.

What it does not contain: No measurements, no route or screen labels, no credential: every number on it arrives afterwards from the panel read.
/_boosthis/pulse Public

One coarse reading for the bubble itself: a score, a rating word, and how many samples it came from.

Who can reach it: anyone who can reach your app.

Why it is open: The bubble is injected into the app's own pages and polls this from whichever page the visitor is on, so it cannot be limited to local requests without the bubble going blank in production — which is where it is most worth having.

What it does not contain: No route or screen labels, no durations, no per-route rows, no credential, nothing about a visitor.
/_boosthis/panel Public

What the bubble's panel draws: per-meter scores, rating words, meter labels and the numeric captions beside them.

Who can reach it: anyone who can reach your app.

Why it is open: Same reason as the pulse read above — the panel opens on the visitor's page, not on the developer's machine.

What it does not contain: No route or screen labels, no URLs, no raw samples, no install token and no account credential. The account read that does carry one is local-only, below.
/_boosthis/account Local only

The sign-in context the bubble's account card needs, including the token that claims this install.

Who can reach it: local requests only — nothing opens it remotely.
/_boosthis/status Local only

The standalone “is Boosthis working?” page — the surface a back-end service with no UI has instead of a bubble.

Who can reach it: local requests only — nothing opens it remotely.

Java

What your users see

A floating bubble in the corner of the page: a score, a rating word, and a panel it opens.
Where: Injected into HTML pages this service itself serves. Pages served by a separate frontend are a different process and get nothing.
The floating bubble is on by default in every environment, including production. BOOSTHIS_BUBBLE set to 0 hides it and the kit carries on measuring; BOOSTHIS_DISABLED stops the kit altogether. Each name is read from the environment where this runtime has one, and otherwise from a value of the same name on the host.

What your app starts answering

/_boosthis Public

The kit's own page: static markup that draws the panel by fetching the panel read below. Both spellings are the same page, because a developer types one or the other and neither habit should 404.

Who can reach it: anyone who can reach your app.

Why it is open: It is the page the bubble links to, opened from any page the app serves, so a gate here would 403 a developer whose bubble works. The markup is static — it holds no measurements to protect.

What it does not contain: No measurements, no route or screen labels, no credential: every number on it arrives afterwards from the panel read.
/_boosthis/ Public

The kit's own page: static markup that draws the panel by fetching the panel read below. Both spellings are the same page, because a developer types one or the other and neither habit should 404.

Who can reach it: anyone who can reach your app.

Why it is open: It is the page the bubble links to, opened from any page the app serves, so a gate here would 403 a developer whose bubble works. The markup is static — it holds no measurements to protect.

What it does not contain: No measurements, no route or screen labels, no credential: every number on it arrives afterwards from the panel read.
/_boosthis/pulse Public

One coarse reading for the bubble itself: a score, a rating word, and how many samples it came from.

Who can reach it: anyone who can reach your app.

Why it is open: The bubble is injected into the app's own pages and polls this from whichever page the visitor is on, so it cannot be limited to local requests without the bubble going blank in production — which is where it is most worth having.

What it does not contain: No route or screen labels, no durations, no per-route rows, no credential, nothing about a visitor.
/_boosthis/panel Public

What the bubble's panel draws: per-meter scores, rating words, meter labels and the numeric captions beside them.

Who can reach it: anyone who can reach your app.

Why it is open: Same reason as the pulse read above — the panel opens on the visitor's page, not on the developer's machine.

What it does not contain: No route or screen labels, no URLs, no raw samples, no install token and no account credential. The account read that does carry one is local-only, below.
/_boosthis/account Local only

The sign-in context the bubble's account card needs, including the token that claims this install.

Who can reach it: local requests only — nothing opens it remotely.
/_boosthis/status Local only

The standalone “is Boosthis working?” page — the surface a back-end service with no UI has instead of a bubble.

Who can reach it: local requests only — nothing opens it remotely.

PHP

What your users see

A floating bubble in the corner of the page: a score, a rating word, and a panel it opens.
Where: Injected into HTML pages this service itself serves. Pages served by a separate frontend are a different process and get nothing.
The floating bubble is on by default in every environment, including production. BOOSTHIS_BUBBLE set to 0 hides it and the kit carries on measuring; BOOSTHIS_DISABLED stops the kit altogether. Each name is read from the environment where this runtime has one, and otherwise from a value of the same name on the host.

What your app starts answering

/_boosthis Public

The kit's own page: static markup that draws the panel by fetching the panel read below. Both spellings are the same page, because a developer types one or the other and neither habit should 404.

Who can reach it: anyone who can reach your app.

Why it is open: It is the page the bubble links to, opened from any page the app serves, so a gate here would 403 a developer whose bubble works. The markup is static — it holds no measurements to protect.

What it does not contain: No measurements, no route or screen labels, no credential: every number on it arrives afterwards from the panel read.
/_boosthis/ Public

The kit's own page: static markup that draws the panel by fetching the panel read below. Both spellings are the same page, because a developer types one or the other and neither habit should 404.

Who can reach it: anyone who can reach your app.

Why it is open: It is the page the bubble links to, opened from any page the app serves, so a gate here would 403 a developer whose bubble works. The markup is static — it holds no measurements to protect.

What it does not contain: No measurements, no route or screen labels, no credential: every number on it arrives afterwards from the panel read.
/_boosthis/pulse Public

One coarse reading for the bubble itself: a score, a rating word, and how many samples it came from.

Who can reach it: anyone who can reach your app.

Why it is open: The bubble is injected into the app's own pages and polls this from whichever page the visitor is on, so it cannot be limited to local requests without the bubble going blank in production — which is where it is most worth having.

What it does not contain: No route or screen labels, no durations, no per-route rows, no credential, nothing about a visitor.
/_boosthis/panel Public

What the bubble's panel draws: per-meter scores, rating words, meter labels and the numeric captions beside them.

Who can reach it: anyone who can reach your app.

Why it is open: Same reason as the pulse read above — the panel opens on the visitor's page, not on the developer's machine.

What it does not contain: No route or screen labels, no URLs, no raw samples, no install token and no account credential. The account read that does carry one is local-only, below.
/_boosthis/account Local only

The sign-in context the bubble's account card needs, including the token that claims this install.

Who can reach it: local requests only — nothing opens it remotely.
/_boosthis/status Local only

The standalone “is Boosthis working?” page — the surface a back-end service with no UI has instead of a bubble.

Who can reach it: local requests only — nothing opens it remotely.

Ruby

What your users see

A floating bubble in the corner of the page: a score, a rating word, and a panel it opens.
Where: Injected into HTML pages this service itself serves. Pages served by a separate frontend are a different process and get nothing.
The floating bubble is on by default in every environment, including production. BOOSTHIS_BUBBLE set to 0 hides it and the kit carries on measuring; BOOSTHIS_DISABLED stops the kit altogether. Each name is read from the environment where this runtime has one, and otherwise from a value of the same name on the host.

What your app starts answering

/_boosthis Public

The kit's own page: static markup that draws the panel by fetching the panel read below. Both spellings are the same page, because a developer types one or the other and neither habit should 404.

Who can reach it: anyone who can reach your app.

Why it is open: It is the page the bubble links to, opened from any page the app serves, so a gate here would 403 a developer whose bubble works. The markup is static — it holds no measurements to protect.

What it does not contain: No measurements, no route or screen labels, no credential: every number on it arrives afterwards from the panel read.
/_boosthis/ Public

The kit's own page: static markup that draws the panel by fetching the panel read below. Both spellings are the same page, because a developer types one or the other and neither habit should 404.

Who can reach it: anyone who can reach your app.

Why it is open: It is the page the bubble links to, opened from any page the app serves, so a gate here would 403 a developer whose bubble works. The markup is static — it holds no measurements to protect.

What it does not contain: No measurements, no route or screen labels, no credential: every number on it arrives afterwards from the panel read.
/_boosthis/pulse Public

One coarse reading for the bubble itself: a score, a rating word, and how many samples it came from.

Who can reach it: anyone who can reach your app.

Why it is open: The bubble is injected into the app's own pages and polls this from whichever page the visitor is on, so it cannot be limited to local requests without the bubble going blank in production — which is where it is most worth having.

What it does not contain: No route or screen labels, no durations, no per-route rows, no credential, nothing about a visitor.
/_boosthis/panel Public

What the bubble's panel draws: per-meter scores, rating words, meter labels and the numeric captions beside them.

Who can reach it: anyone who can reach your app.

Why it is open: Same reason as the pulse read above — the panel opens on the visitor's page, not on the developer's machine.

What it does not contain: No route or screen labels, no URLs, no raw samples, no install token and no account credential. The account read that does carry one is local-only, below.
/_boosthis/account Local only

The sign-in context the bubble's account card needs, including the token that claims this install.

Who can reach it: local requests only — nothing opens it remotely.
/_boosthis/status Local only

The standalone “is Boosthis working?” page — the surface a back-end service with no UI has instead of a bubble.

Who can reach it: local requests only — nothing opens it remotely.

.NET

What your users see

A floating bubble in the corner of the page: a score, a rating word, and a panel it opens.
Where: Injected into HTML pages this service itself serves. Pages served by a separate frontend are a different process and get nothing.
The floating bubble is on by default in every environment, including production. BOOSTHIS_BUBBLE set to 0 hides it and the kit carries on measuring; BOOSTHIS_DISABLED stops the kit altogether. Each name is read from the environment where this runtime has one, and otherwise from a value of the same name on the host.

What your app starts answering

/_boosthis Public

The kit's own page: static markup that draws the panel by fetching the panel read below. Both spellings are the same page, because a developer types one or the other and neither habit should 404.

Who can reach it: anyone who can reach your app.

Why it is open: It is the page the bubble links to, opened from any page the app serves, so a gate here would 403 a developer whose bubble works. The markup is static — it holds no measurements to protect.

What it does not contain: No measurements, no route or screen labels, no credential: every number on it arrives afterwards from the panel read.
/_boosthis/ Public

The kit's own page: static markup that draws the panel by fetching the panel read below. Both spellings are the same page, because a developer types one or the other and neither habit should 404.

Who can reach it: anyone who can reach your app.

Why it is open: It is the page the bubble links to, opened from any page the app serves, so a gate here would 403 a developer whose bubble works. The markup is static — it holds no measurements to protect.

What it does not contain: No measurements, no route or screen labels, no credential: every number on it arrives afterwards from the panel read.
/_boosthis/pulse Public

One coarse reading for the bubble itself: a score, a rating word, and how many samples it came from.

Who can reach it: anyone who can reach your app.

Why it is open: The bubble is injected into the app's own pages and polls this from whichever page the visitor is on, so it cannot be limited to local requests without the bubble going blank in production — which is where it is most worth having.

What it does not contain: No route or screen labels, no durations, no per-route rows, no credential, nothing about a visitor.
/_boosthis/panel Public

What the bubble's panel draws: per-meter scores, rating words, meter labels and the numeric captions beside them.

Who can reach it: anyone who can reach your app.

Why it is open: Same reason as the pulse read above — the panel opens on the visitor's page, not on the developer's machine.

What it does not contain: No route or screen labels, no URLs, no raw samples, no install token and no account credential. The account read that does carry one is local-only, below.
/_boosthis/account Local only

The sign-in context the bubble's account card needs, including the token that claims this install.

Who can reach it: local requests only — nothing opens it remotely.
/_boosthis/status Local only

The standalone “is Boosthis working?” page — the surface a back-end service with no UI has instead of a bubble.

Who can reach it: local requests only — nothing opens it remotely.

Rust

What your users see

A floating bubble in the corner of the page: a score, a rating word, and a panel it opens.
Where: Injected into HTML pages this service itself serves. Pages served by a separate frontend are a different process and get nothing.
The floating bubble is on by default in every environment, including production. BOOSTHIS_BUBBLE set to 0 hides it and the kit carries on measuring; BOOSTHIS_DISABLED stops the kit altogether. Each name is read from the environment where this runtime has one, and otherwise from a value of the same name on the host.

What your app starts answering

/_boosthis/pulse Public

One coarse reading for the bubble itself: a score, a rating word, and how many samples it came from.

Who can reach it: anyone who can reach your app.

Why it is open: The bubble is injected into the app's own pages and polls this from whichever page the visitor is on, so it cannot be limited to local requests without the bubble going blank in production — which is where it is most worth having.

What it does not contain: No route or screen labels, no durations, no per-route rows, no credential, nothing about a visitor.
/_boosthis/panel Public

What the bubble's panel draws: per-meter scores, rating words, meter labels and the numeric captions beside them.

Who can reach it: anyone who can reach your app.

Why it is open: Same reason as the pulse read above — the panel opens on the visitor's page, not on the developer's machine.

What it does not contain: No route or screen labels, no URLs, no raw samples, no install token and no account credential. The account read that does carry one is local-only, below.
/_boosthis/account Local only

The sign-in context the bubble's account card needs, including the token that claims this install.

Who can reach it: local requests only — nothing opens it remotely.

Elixir

What your users see

A floating bubble in the corner of the page: a score, a rating word, and a panel it opens.
Where: Injected into HTML pages this service itself serves. Pages served by a separate frontend are a different process and get nothing.
The floating bubble is on by default in every environment, including production. BOOSTHIS_BUBBLE set to 0 hides it and the kit carries on measuring; BOOSTHIS_DISABLED stops the kit altogether. Each name is read from the environment where this runtime has one, and otherwise from a value of the same name on the host.

What your app starts answering

/_boosthis/pulse Public

One coarse reading for the bubble itself: a score, a rating word, and how many samples it came from.

Who can reach it: anyone who can reach your app.

Why it is open: The bubble is injected into the app's own pages and polls this from whichever page the visitor is on, so it cannot be limited to local requests without the bubble going blank in production — which is where it is most worth having.

What it does not contain: No route or screen labels, no durations, no per-route rows, no credential, nothing about a visitor.
/_boosthis/panel Public

What the bubble's panel draws: per-meter scores, rating words, meter labels and the numeric captions beside them.

Who can reach it: anyone who can reach your app.

Why it is open: Same reason as the pulse read above — the panel opens on the visitor's page, not on the developer's machine.

What it does not contain: No route or screen labels, no URLs, no raw samples, no install token and no account credential. The account read that does carry one is local-only, below.
/_boosthis/account Local only

The sign-in context the bubble's account card needs, including the token that claims this install.

Who can reach it: local requests only — nothing opens it remotely.

Browser / web

What your users see

A floating bubble in the corner of the page: a score, a rating word, and a panel it opens.
Where: On the pages of the web app the kit is started in.
The floating bubble is on by default in every environment, including production. BOOSTHIS_BUBBLE set to 0 hides it and the kit carries on measuring; BOOSTHIS_DISABLED stops the kit altogether. Each name is read from the environment where this runtime has one, and otherwise from a value of the same name on the host.

What your app starts answering

Nothing. A browser kit runs on the page. It mounts nothing on the app's server and adds no address anyone can request.

React Native / Expo

What your users see

A floating bubble over the app's own screens, opening the same panel.
Where: Inside the app itself, on the device.
The floating bubble is on by default in every environment, including production. BOOSTHIS_BUBBLE set to 0 hides it and the kit carries on measuring; BOOSTHIS_DISABLED stops the kit altogether. Each name is read from the environment where this runtime has one, and otherwise from a value of the same name on the host.

What your app starts answering

Nothing. A phone app serves nothing. The kit adds no address a stranger could request.

Flutter

What your users see

A floating bubble over the app's own screens, opening the same panel.
Where: Inside the app itself, on the device.
The floating bubble is on by default in every environment, including production. BOOSTHIS_BUBBLE set to 0 hides it and the kit carries on measuring; BOOSTHIS_DISABLED stops the kit altogether. Each name is read from the environment where this runtime has one, and otherwise from a value of the same name on the host.

What your app starts answering

Nothing. A phone app serves nothing. The kit adds no address a stranger could request.

Swift / iOS

What your users see

A floating bubble over the app's own screens, opening the same panel.
Where: Inside the app itself, on the device.
The floating bubble is on by default in every environment, including production. BOOSTHIS_BUBBLE set to 0 hides it and the kit carries on measuring; BOOSTHIS_DISABLED stops the kit altogether. Each name is read from the environment where this runtime has one, and otherwise from a value of the same name on the host.

What your app starts answering

Nothing. A phone app serves nothing. The kit adds no address a stranger could request.

Kotlin / Android

What your users see

A floating bubble over the app's own screens, opening the same panel.
Where: Inside the app itself, on the device.
The floating bubble is on by default in every environment, including production. BOOSTHIS_BUBBLE set to 0 hides it and the kit carries on measuring; BOOSTHIS_DISABLED stops the kit altogether. Each name is read from the environment where this runtime has one, and otherwise from a value of the same name on the host.

What your app starts answering

Nothing. A phone app serves nothing. The kit adds no address a stranger could request.

Edge / V8 isolates

What your users see

Nothing. An isolate function has no screen of its own to draw a bubble on, so this kit adds nothing an end user can see.

What your app starts answering

Nothing. The edge kit measures the function it wraps and mounts no address of its own.

If your reviewer wants more

What Boosthis collects inside your app — what the kit sends us, what it never sends, where it is processed and how long it is kept.
The help centre, for what Boosthis measures and how it is installed.
support@boosthis.com — a question about your own deployment reaches a person.