OneStar Feedback

Forms, polls and NPS questions on your own site or app, with every answer counted by code next to your store reviews.

OneStar reads the reviews people leave in the App Store, on Google Play and on Steam. Feedback asks the people who never leave one. You put a short form on your site or in your app, people answer it, and OneStar counts every answer by code and keeps it next to your store reviews, never mixed in.

Forms are part of Pro and Max. The REST API, webhooks and imports are part of Max. See pricing for what each plan includes.

What you can ask#

• A quick reaction: one rating (stars, thumbs, faces, a scale or a slider), with an optional question about why.
• NPS: the 0 to 10 question, with promoters, passives, detractors and the score's 95% range.
• A poll: one choice or several, with an optional Other.
• A survey: up to 20 questions mixing ratings, NPS, choices, rankings and written answers, with questions that show only after a given answer.

Every form is versioned: questions go live when you publish, and answers to versions that ask the same questions are counted together.

How it fits together#

1. You build the form in OneStar and publish it.
2. You add the sites the form may run on (its allowed sites), or share its own page by link or QR code.
3. Your page loads the loader from https://embed.onestar.sh/v1/loader.js and places a <onestar-feedback> element. The element draws the form in a shadow root, so your CSS and the form's never collide.
4. Answers go to https://api.onestar.sh/v1/f/. The first tap is saved at once, so a one tap reaction counts even when the person skips the rest.
5. Results in OneStar count each question by code, with ranges, completion, who answered, where the form ran and how many people who saw it answered.

Where to go next#

• Quickstart: a form on a page in a few minutes.
• Frameworks: React, Next.js, Vue, Svelte, Astro and plain HTML.
• Native apps: iOS, Android, React Native and Flutter.
• JavaScript API and Your own UI: open forms from code or send answers from a form you draw yourself.
• Signed in users: answers that carry a verified user and traits.
• Context and placements: split results by app version, plan or where the form sits.
• REST API and Webhooks: read answers on your own server.

What OneStar keeps#

Nothing is stored in the visitor's browser before they answer. After the first answer the widget keeps a random device key and a note that this browser answered, so a reply can reach them and a form set to one answer per person does not ask twice. No cookies. Contact details are kept only when the form asks for them, sealed, and shown to no one but you. The security page has the full list.

For AI assistants#

Every page of these docs is Markdown at its address plus .md (this one is /docs/feedback.md), and the site's llms.txt lists them all. A coding agent can read the Quickstart and the Frameworks page and install a form for you.