Owned product · Device-local Poppy bot shelf and QR sharing
Boop
Save public Poppy chatbot links in a device-local shelf, generate kiosk-ready QR cards, and send the right bot from the browser already in your hand.
Ownership disclosure
Boop is an owned SharetoBoard product. This is a founder product record, not an independent review or an endorsement by Poppy.
The project decision
A public chatbot link is not useful if the right person cannot quickly find, open, scan, or share it at the moment it matters.
Who it is for: Poppy users who want a small, installable web app for organizing and sharing public chatbot links without creating another account or backend.
What works
Verified or explicitly documented behavior.
- Save, edit, select, and remove a shelf of public Poppy chatbot links in the current browser.
- Generate a QR card, kiosk view, downloadable PNG or SVG, direct-open action, and supported device share action.
- Export a local catalog backup.
- Keep the shelf device-local without fetching, proxying, shortening, or logging the saved links through a Boop backend.
Known limitations
What this project is not allowed to claim yet.
- One real Poppy-generated public chatbot share-link acceptance on desktop and Android remains open.
- The shelf does not sync across browsers or devices.
- A native Play Store package is not part of the current public web beta.
- Users must never paste API keys, private board links, passwords, or secret tokens.
Current evidence
The public claim must stay inside this boundary.
- 01SharetoBoard product-status schema version 3 identifies Boop 0.1.0 as public_web_beta and public_release true.
- 02The public route is https://sharetoboard.com/boop/.
- 03The recorded automated gate is 20 of 20 tests, a passing production build, and zero known dependency-audit vulnerabilities.
Current blockerReal public-chatbot link acceptance across desktop and Android is not yet recorded, and cross-device sync remains an explicit product decision.
Next gateRun one consented real-link acceptance on desktop and Android, record the result, then decide whether device-local storage is the permanent boundary.
Follow the next gate