FieldTest a FORGECHANCE product

The two-minute install.

FieldTest is a plain script tag plus a small folder. It works wherever you can add a tag to your app's HTML and host two small files next to it. Below: every platform we know, with honest labels — green when the platform's own manual confirms the route, amber when it's our best route and we haven't tested it yet.

What you need first:

The kit folder (shared on request while the license is set — the signup on the front page gets you in line). It holds testdrive.js and a vendor folder. On platforms where you can see your project's files (Lovable, Bolt, Replit, v0), they sit next to your app's HTML. On platforms with no file hosting (Bubble, Base44), the tag needs a hosted kit address instead — your early-access invite will include one when your spot opens; that part is not live yet, and we say so rather than pretend.

<script src="testdrive.js"></script>

The universal version

  1. Put the kit files next to your app's page (same folder as your index.html, or your site root).
  2. Paste the one line into the page's HTML — just before </body>, or in the <head> (both work as of kit v0.1.1a).
  3. Open your app. The panel appears bottom-right, already open. Type a thought in its box, press Add note (or Fix this), then press Save the record — if you get a file with your note inside, you're installed.

Platform by platform

Bubble from Bubble's own manual

  1. Open your app in the Bubble editor.
  2. Go to Settings → SEO / metatags.
  3. Find the box "Script/meta tags in header" and paste the tag. (Bubble's manual: "Some services require code to be pasted in the header of the page's HTML. Paste the code here.")
  4. Deploy to live and test on the live URL.

Bubble's manual does not say whether this needs a paid plan. Bubble apps are single-page style; the recorder follows route changes but we have not tested on Bubble yet.

Base44 from Base44's own docs

  1. Open your app in the Base44 editor.
  2. In the AI chat, type: "Add this code inside the <head> of index.html and change nothing else:" and paste the tag.
  3. Click Publish — it runs for visitors only after publishing.
  4. Prefer your own hands? Dashboard Code tab → index.html, paste inside <head>.

Base44's docs describe this route for analytics scripts; ours is the same mechanism. Not yet tested by us.

Lovable our best route — not yet tested

  1. On a paid plan, open the Code tab (Lovable's docs: "Code editing is available on paid plans"; free is read-only).
  2. Open index.html, paste the tag inside <head>, Save, Publish.
  3. Asking the AI chat to add the tag may also work — Lovable's docs don't say either way.

No Lovable doc mentions custom script tags specifically. We'll test with our first Lovable builders and firm this up.

Bolt our best route — not yet tested

  1. Open Code view on desktop (Bolt's docs: read-only on Safari and mobile).
  2. Open index.html, paste the tag inside <head>, Save (Bolt rebuilds; editing uses no tokens), Publish.
  3. Keep the tag in index.html so it survives rebuilds.

Bolt documents file editing; it doesn't address custom script tags specifically. We'll firm this up with first builders.

Replit unverified — ask your Agent

  1. Replit's own docs don't address custom script tags. Their docs advise prompting the Agent rather than editing code.
  2. Try: "Add this script tag to the <head> of index.html and change nothing else:" plus the tag.

Replit's own "Made with Replit badge" page shows a script tag placed in index.html, which is an official hint the route works — but we haven't tested it.

v0 unverified — the hard one

  1. v0 projects are Next.js with no index.html; the tag belongs in the root layout (app/layout.tsx), which means touching code.
  2. If you're comfortable: v0's editor supports manual edits (press Save to commit), then deploy via Vercel.

Honestly the roughest fit today for a non-technical builder. If you're on v0 and want this, tell us — you'll shape how we solve it.

Did it work?

✓ The sixty-second check: open your app, type "install test" in the panel's box, press Add note — if a full-screen drawing window opens (the picture box is on by default), press Keep this picture or No picture — then press Save the record. If your browser hands you a file, open it: your note is inside, with the page name and time — you're done. The kit also ships selftest.html — open it next to the kit files and it runs 43 checks, including the no-network-requests check on the kit as shipped.

Stuck anywhere? Early access comes with a human on the other end — your invite includes a direct address, and your stuck spot becomes the next fix.

FieldTest · a ForgeChance product · kit v0.1.1a · front page This page loads nothing from anyone: no analytics, no cookies, no external scripts, no fonts, no trackers. Platform claims last checked against each platform's own documentation on 2026-10-27. Labels tell you exactly how sure we are.