● A free public tool  ·  Built by Poptani Labs  ·  No sign-up  ·  Your data never leaves your browser
Built in the Lab · 5-minute read

How this site's feedback button works without a server

A hand resting on a laptop keyboard, pressing a key
Image: 'A hand rests on a laptop keyboard, pressing a key.jpg' by Shixart1985, CC BY 2.0, via Wikimedia Commons

Look at the bottom-right corner of this page and you will find a small pill-shaped button that says Feedback. It is on every page of this site, and it does something that sounds like it should need a server: it takes your message and delivers it to the site owner. There is no server behind it. There is no account to create, no cookie set, no tracking script involved, and the site itself never stores what you type. This post is different from the others in this batch: it describes a feature on this very site, from the code that runs it — no outside research, and no claim that anything here was tested anywhere else.

What happens when you tap it

Tapping the button opens a small panel with three things: four category pills — Bug, Idea, Content fix, Other — a message box, and an optional email field, for use only if you want a reply. Pressing Send does not post your message to this site at all. Instead, the page in your browser sends it directly to the reply address of an online form, the same kind of form anyone can make for free, and the answer lands in a spreadsheet the site owner reads. The message travels from your browser to the form's service and never touches a server belonging to this site — because there is not one. The button, the panel and all of its styling are drawn by the page itself, using the site's own colours, so it follows the light and dark theme automatically. If sending fails — no connection, for example — the panel says so plainly instead of pretending it worked.

The messages that vanished

Here is the fun anecdote — the version of this button that ate every message it was given. The form has two sets of field names: the ones its own tools display, and the hidden ones the live form actually uses when someone types in it. They are not the same, and nothing in the form's own interface warns you about it. The first version of the button posted to the names shown by the tools — the plausible, documented-looking ones — and every single message failed quietly. Nothing was recorded, no error was visible, and the button cheerfully reported success. The fix was detective work, not cleverness: open the real form in a browser, type in it, and watch which hidden fields actually update as you type. Those are the names that work. The lesson stuck, and it is now a standing rule for this site: whenever the form's questions are ever recreated, the field names must be re-read from the live form before anything is changed — never trusted from memory, and never taken from the tools' display.

The menu that went invisible

The category picker was not always pills. The first version used the browser's standard dropdown menu — the ordinary, sensible choice. Then a reader reported that on their Android phone the options were unreadable: light text on a light background, effectively invisible. The cause was a quiet mismatch of themes. The dropdown menu followed the phone's system theme, not the page's theme — so with the site in dark mode and the phone in light mode, the menu drew itself light-on-light. The fix was to stop using the phone's menu entirely and draw the choices as pill buttons in the page itself, where the site controls every colour. Two more small decisions came from real use. The button has no dismiss control: an earlier version had a close button, the site owner dismissed it once and could not get it back on refresh, so the button now always renders. And on the poker page, where the game controls sit along the bottom of the screen, the button rides higher, so it never covers the cards mid-hand.

The trap for bots

One last piece of the design is invisible by intent. The panel contains an extra field that no human ever sees — positioned far off the screen, with no label. Automated spam scripts fill in every field they find, so if that hidden field arrives filled, the message is quietly dropped and the sender is shown a thank-you anyway. Real readers never trip it, because they cannot see it. If spam ever does get through, the planned upgrade is a human-verification check on the submit path — but so far the invisible field has been enough. The whole feature is a study in doing less: no server to run, no database to guard, no account system to maintain. Borrow a free form's plumbing, draw your own interface, guard it with a trap only robots can see, and spend the saved effort on the details people actually notice — like a menu they can read.

Under the Hood

The feedback button is the smallest feature on this site, and it carries the largest lesson in how the site is built: borrow the plumbing, own the interface. A free form handles the delivery; the page handles everything the reader sees; a hidden field handles the bots. The hard parts were never the sending. They were the field names nobody documents, the menu that followed the wrong theme, and the dismiss button that worked too well. Small features, honestly built, are mostly small human details — and getting those right is the whole job.

Related on Poptani Labs: Inside the nightly blog pipeline: how this post got written, checked and published, How this site's search actually works (no server, no database), Inside the SWP Simulator: how a retirement withdrawal plan is actually calculated. More in this category: Built in the Lab.

Sources: Poptani Labs blog, Inside the SWP Simulator (Poptani Labs), How this site's search actually works (Poptani Labs)

← All posts