A poll, a quiz, a job application — describe it and share the link.
New patient intake
DraftFirst name
Last name
Insurance card
Drop a photo or PDF
What you can create
Color lives in the answers — live votes, ratings, lettered choices — not in a pile of identical form fields.
One question, tap to vote, share the tally. Built to look good in a tweet.
Where should we host the offsite?
LiveLettered answers, auto score, then a results card.
Q1 · 10 pts
typeof null returns…
Ratings, scales, follow-ups that only show when they should.
Recommend us to a colleague?
The boring-but-important stuff — jobs, patients, events — with branching that hides fields until they matter.
Or just describe something else
How it works
Four steps. No arrows. Same loop whether it's a poll or a job application.
A sentence is enough. Polls, quizzes, intake — same box.
Fields, types, and the bits that only show when they should.
A collect link for answers, a results link for the tally.
Rank applicants, spot a trend — still just a prompt.
Features
Click through the loop below. Then the three things this project actually cares about.
GitHub URL if they pick frontend. Essay if they don't. Wired from the prompt.
One link to fill it in. One link to watch the votes come in. Copy either into a tweet.
Rank the applicants. Find who said they'd relocate. Same prompt box, different job.
Example ranking — not live data
For the curious
Sketch of the API. The playground is the real thing — no key, no install.
Use the demo instead. The code above is how I'd want the API to feel.