[{"data":1,"prerenderedAt":462},["ShallowReactive",2],{"kc-/knowledge/building-better-forms":3,"kc-clusters-/knowledge/building-better-forms":197,"kc-related-/knowledge/building-better-forms":198},{"id":4,"title":5,"author":6,"body":7,"date":160,"description":161,"draft":162,"extension":163,"faqs":164,"image":174,"isPillar":162,"meta":175,"navigation":176,"path":177,"pillar":178,"pillarName":179,"seo":180,"sources":181,"stem":190,"tags":191,"takeaways":194,"updated":195,"__hash__":196},"knowledge/knowledge/building-better-forms.md","Building Better Forms: Our Product Vision","RoundPushPin Team",{"type":8,"value":9,"toc":146},"minimark",[10,14,19,26,29,32,36,41,44,48,57,61,64,68,71,75,115,119,122,143],[11,12,13],"p",{},"Forms are everywhere. Job applications, customer surveys, event registrations, onboarding flows. They're one of the most common ways software collects data from humans. Yet the tools we use to build them force us to choose between great UX and great data.",[15,16,18],"h2",{"id":17},"do-you-have-to-choose-between-form-ux-and-data-quality","Do you have to choose between form UX and data quality?",[11,20,21,25],{},[22,23,24],"strong",{},"No — that trade-off is a false one."," Polished form tools tend to hide your data in a black box, while custom-built forms give you data control at the cost of weeks of work and weaker UX. RoundPushPin gives you both: conversational UX on top of a structured, queryable database.",[11,27,28],{},"On one side, you have Typeform and its clones. Beautiful, conversational, high completion rates. But your data lives in a black box. On the other side, you have custom-built forms. Full control over your data model, but you're spending weeks building something that still doesn't look as good.",[11,30,31],{},"RoundPushPin eliminates this trade-off.",[15,33,35],{"id":34},"what-are-roundpushpins-design-principles","What are RoundPushPin's design principles?",[37,38,40],"h3",{"id":39},"_1-respondent-experience-first","1. Respondent Experience First",[11,42,43],{},"Every form built with RoundPushPin uses a one-question-at-a-time interface. CSS Scroll Snap provides native-feeling transitions. Vue's transition system handles animations. The result feels smooth, focused, and respectful of the respondent's attention.",[37,45,47],{"id":46},"_2-data-as-a-first-class-citizen","2. Data as a First-Class Citizen",[11,49,50,51,56],{},"Behind the scenes, every form maps to a PostgreSQL schema. We use Drizzle ORM with TypeScript to define table structures that mirror your form's questions. This means your data is queryable, joinable, and analyzable from the moment it's collected — the reasoning behind ",[52,53,55],"a",{"href":54},"/knowledge/why-relational-data","choosing a relational model over JSON blobs",".",[37,58,60],{"id":59},"_3-developer-experience-matters","3. Developer Experience Matters",[11,62,63],{},"RoundPushPin is built with TypeScript end-to-end. Validation schemas defined with Zod work on both client and server — the same rules that provide real-time feedback to respondents also protect your API. No duplication, no drift.",[37,65,67],{"id":66},"_4-own-your-infrastructure","4. Own Your Infrastructure",[11,69,70],{},"We believe your data should live on your servers. RoundPushPin is self-hosted by default. A Docker Compose file gets you running with PostgreSQL in one command. No vendor lock-in, no data residency concerns, no surprise pricing.",[15,72,74],{"id":73},"what-is-roundpushpin-built-with","What is RoundPushPin built with?",[76,77,78,85,91,97,103,109],"ul",{},[79,80,81,84],"li",{},[22,82,83],{},"Nuxt 4"," for server-side rendering and client-side interactivity",[79,86,87,90],{},[22,88,89],{},"FormKit"," for schema-driven form rendering",[79,92,93,96],{},[22,94,95],{},"Drizzle ORM"," for type-safe database operations",[79,98,99,102],{},[22,100,101],{},"PostgreSQL"," for relational data storage",[79,104,105,108],{},[22,106,107],{},"Pinia"," for client-side state management",[79,110,111,114],{},[22,112,113],{},"Zod"," for isomorphic validation",[15,116,118],{"id":117},"what-is-roundpushpin-building-next","What is RoundPushPin building next?",[11,120,121],{},"Our roadmap is focused on three areas:",[123,124,125,131,137],"ol",{},[79,126,127,130],{},[22,128,129],{},"The Form Builder",": A visual editor for creating forms with conditional logic, validation rules, and custom themes",[79,132,133,136],{},[22,134,135],{},"The Response Engine",": Real-time data capture with event sourcing for granular analytics",[79,138,139,142],{},[22,140,141],{},"The Analytics Layer",": Built-in dashboards for completion rates, drop-off analysis, and response patterns",[11,144,145],{},"We're shipping fast and improving constantly. If you care about forms and data, follow along.",{"title":147,"searchDepth":148,"depth":148,"links":149},"",2,[150,151,158,159],{"id":17,"depth":148,"text":18},{"id":34,"depth":148,"text":35,"children":152},[153,155,156,157],{"id":39,"depth":154,"text":40},3,{"id":46,"depth":154,"text":47},{"id":59,"depth":154,"text":60},{"id":66,"depth":154,"text":67},{"id":73,"depth":148,"text":74},{"id":117,"depth":148,"text":118},"2026-01-25","How RoundPushPin reimagines the form-building experience with conversational UX, developer-first design, and structured data.",false,"md",[165,168,171],{"q":166,"a":167},"What makes a good form builder?","One that delivers a high-completion experience and keeps the resulting data usable. Many tools optimize the first and neglect the second; the better question after 'how does it look?' is 'how do I query this data?'",{"q":169,"a":170},"Why does form data structure matter?","Because the storage model caps what you can do later: structured, typed data is queryable and joinable, while unstructured blobs must be wrangled before any analysis. Structure is the difference between data you can question and data you fight.",{"q":172,"a":173},"Can I self-host RoundPushPin?","Yes. RoundPushPin is self-hosted, built with TypeScript end to end, so you can run it on your own infrastructure and own your data.","/images/knowledge/building-better-forms.png",{},true,"/knowledge/building-better-forms","conversational-form-design","Conversational form design",{"title":5,"description":161},[182,186],{"title":183,"url":184,"publisher":185},"Progressive Disclosure (Jakob Nielsen)","https://www.nngroup.com/articles/progressive-disclosure/","Nielsen Norman Group",{"title":187,"url":188,"publisher":189},"Galesic, M. & Bosnjak, M. (2009) — Effects of questionnaire length on participation and response quality","https://doi.org/10.1093/poq/nfp031","Public Opinion Quarterly","knowledge/building-better-forms",[192,193],"product","vision",[],"2026-02-12","ZaP-Ua9nq9rSM2PVDqRGSDwZJqhOKm3tSDgefhD4ovk",[],[199,337],{"id":200,"title":201,"author":6,"body":202,"date":301,"description":302,"draft":162,"extension":163,"faqs":303,"image":311,"isPillar":162,"meta":312,"navigation":176,"path":313,"pillar":178,"pillarName":179,"seo":314,"sources":315,"stem":326,"tags":327,"takeaways":332,"updated":301,"__hash__":336},"knowledge/knowledge/building-trust-in-forms.md","How to Build Trust in Your Forms (So People Complete Them)",{"type":8,"value":203,"toc":294},[204,207,211,222,226,244,248,259,263,274,278],[11,205,206],{},"A form asks people to hand over their data, and people only do that for a site they trust. Trust isn't a nice-to-have on a form — it's a precondition for completion, and it's especially fragile the moment you ask for something personal.",[15,208,210],{"id":209},"why-does-trust-matter-for-form-completion","Why does trust matter for form completion?",[11,212,213,216,217,221],{},[22,214,215],{},"Because submitting a form is an act of trust, and doubt converts directly into abandonment."," When credibility is low, people hesitate, skip fields, or leave — and the effect is sharpest on sensitive questions, where distrust drives both refusals and inaccurate answers (Tourangeau & Yan, 2007). Earning trust isn't separate from conversion; it ",[218,219,220],"em",{},"is"," part of conversion.",[15,223,225],{"id":224},"what-makes-a-form-look-trustworthy","What makes a form look trustworthy?",[11,227,228,231,232,235,236,239,240,243],{},[22,229,230],{},"The elements people notice, and the meaning they assign to them."," Fogg's ",[218,233,234],{},"Prominence-Interpretation Theory"," (2003) explains online credibility as a two-step process: a person has to ",[22,237,238],{},"notice"," an element (prominence), then ",[22,241,242],{},"interpret"," it as good or bad. So trust on a form is built from noticeable, positively-interpreted cues — a clean, professional design, a real organization clearly behind the form, plain language, and no jarring or excessive questions (Nielsen Norman Group). Sloppiness and surprises read as risk.",[15,245,247],{"id":246},"how-do-you-reassure-people-about-their-data","How do you reassure people about their data?",[11,249,250,253,254,258],{},[22,251,252],{},"Tell them what you'll do with it, why you're asking, and prove you ask for little."," Concretely: state the purpose in plain language, link a privacy notice near the submit action, keep the form ",[52,255,257],{"href":256},"/knowledge/what-to-ask-on-a-form","minimal",", and when you must ask something sensitive, explain why and place it late — after the person has invested effort. Transparency is what lowers the refusals that distrust causes (Tourangeau & Yan, 2007).",[15,260,262],{"id":261},"do-trust-signals-actually-change-behaviour","Do trust signals actually change behaviour?",[11,264,265,268,269,273],{},[22,266,267],{},"Yes — but only the ones people notice and believe."," Prominence-Interpretation Theory is a useful filter: a trust cue does nothing if it isn't noticed, and backfires if it's interpreted as hollow. Genuine signals (a real company, a clear privacy explanation, a short honest form) beat generic badges. Test which cues move ",[52,270,272],{"href":271},"/knowledge/form-completion-rate","completion rate"," for your audience rather than assuming.",[15,275,277],{"id":276},"how-roundpushpin-helps-you-earn-trust","How RoundPushPin helps you earn trust",[11,279,280,283,284,288,289,293],{},[22,281,282],{},"RoundPushPin supports trustworthy forms by default: clean conversational design, minimal relevant questions, and self-hosted data you genuinely control."," Because responses live in ",[52,285,287],{"href":286},"/knowledge/self-hosted-forms","your own database",", \"we keep your data private\" isn't a slogan — you decide where it lives and how long you keep it, which is the substance behind ",[52,290,292],{"href":291},"/knowledge/gdpr-compliant-forms","GDPR-compliant"," trust claims.",{"title":147,"searchDepth":148,"depth":148,"links":295},[296,297,298,299,300],{"id":209,"depth":148,"text":210},{"id":224,"depth":148,"text":225},{"id":246,"depth":148,"text":247},{"id":261,"depth":148,"text":262},{"id":276,"depth":148,"text":277},"2026-03-16","People won't hand over data to a form they don't trust. This research-backed guide covers how visitors judge credibility, the trust signals that matter on forms, and how to reassure people about their data.",[304,306,308],{"q":210,"a":305},"Filling in a form means handing over data, which people only do when they trust the site. Low credibility raises hesitation and abandonment — and on sensitive questions, distrust increases refusals and misreporting.",{"q":225,"a":307},"Credibility comes from elements people notice and judge positively — clear design, a real organization behind it, plain language about why you ask, visible privacy/security cues, and no surprising or excessive questions.",{"q":309,"a":310},"How do you reassure people about their form data?","Tell them plainly what you'll do with it and why each question is asked, link a privacy notice, keep the form minimal, and place any sensitive question late with an explanation. Transparency reduces refusals.","/images/knowledge/building-trust-in-forms.png",{},"/knowledge/building-trust-in-forms",{"title":201,"description":302},[316,320,322],{"title":317,"url":318,"publisher":319},"Fogg, B. J. (2003) — Prominence-Interpretation Theory: explaining how people assess credibility online","https://doi.org/10.1145/765891.765951","CHI '03 / Stanford Web Credibility Project",{"title":234,"url":321,"publisher":185},"https://www.nngroup.com/articles/prominence-interpretation-theory/",{"title":323,"url":324,"publisher":325},"Tourangeau, R. & Yan, T. (2007) — Sensitive questions in surveys","https://doi.org/10.1037/0033-2909.133.5.859","Psychological Bulletin","knowledge/building-trust-in-forms",[328,329,330,331],"trust","credibility","conversion","research",[333,334,335],"People only submit data to a form they trust — low credibility raises hesitation and abandonment.","Credibility is what users notice and how they interpret it (Fogg's Prominence-Interpretation Theory).","Reassure with clear purpose, visible privacy cues, minimal asks, and sensitive questions placed late.","tzUin9YU-8HMjkplypyURGhSFed0__aoIDxr88QnEPQ",{"id":338,"title":339,"author":6,"body":340,"date":429,"description":430,"draft":162,"extension":163,"faqs":431,"image":440,"isPillar":162,"meta":441,"navigation":176,"path":256,"pillar":178,"pillarName":179,"seo":442,"sources":443,"stem":453,"tags":454,"takeaways":457,"updated":429,"__hash__":461},"knowledge/knowledge/what-to-ask-on-a-form.md","What to Ask (and Not Ask) on a Form",{"type":8,"value":341,"toc":422},[342,345,349,361,365,371,375,389,393,403,407],[11,343,344],{},"Every field on a form is a trade: more data for you, more effort and more drop-off for the respondent — and, for personal data, more legal exposure. Deciding what to ask, and what to leave off, is one of the highest-leverage choices in form design.",[15,346,348],{"id":347},"how-do-you-decide-which-fields-to-include","How do you decide which fields to include?",[11,350,351,354,355,358,359,56],{},[22,352,353],{},"Work backward from what you'll actually do with each answer."," If a field doesn't route the response, qualify a lead, personalize a follow-up, or satisfy a genuine requirement, it shouldn't be there. This is also the GDPR principle of ",[22,356,357],{},"data minimisation"," — collect only what's necessary for your stated purpose (Article 5). Minimisation is both good law and good ",[52,360,272],{"href":271},[15,362,364],{"id":363},"what-should-you-not-ask-on-a-form","What should you not ask on a form?",[11,366,367,370],{},[22,368,369],{},"Anything you won't use — and sensitive data you don't truly need."," Beyond the obvious \"cut vanity fields\", be careful with sensitive topics. Tourangeau and Yan (2007) found that sensitive questions produce more misreporting and more refusals, so adding them costs you both data quality and completions. If you don't need it, don't ask it.",[15,372,374],{"id":373},"how-do-sensitive-questions-change-your-data","How do sensitive questions change your data?",[11,376,377,380,381,384,385,388],{},[22,378,379],{},"They lower honesty and raise refusals — so ask them sparingly and carefully."," When a question feels intrusive or socially loaded, people skip it or answer inaccurately (Tourangeau & Yan, 2007). If you genuinely need sensitive information: explain ",[218,382,383],{},"why"," you're asking, keep it optional where you can, and place it late — after the respondent has invested effort and has some reason to trust you (see ",[52,386,387],{"href":313},"building trust in forms",").",[15,390,392],{"id":391},"should-fields-be-required-or-optional","Should fields be required or optional?",[11,394,395,398,399,402],{},[22,396,397],{},"Require only what you truly need to proceed; defer or drop the rest."," Forcing optional fields to be mandatory inflates abandonment and breeds junk answers from respondents who ",[218,400,401],{},"satisfice"," under pressure (Krosnick, 1991). A short set of genuinely-required fields plus optional or progressively-collected extras beats one long required form.",[15,404,406],{"id":405},"how-roundpushpin-helps-you-ask-the-right-things","How RoundPushPin helps you ask the right things",[11,408,409,412,413,417,418,56],{},[22,410,411],{},"RoundPushPin makes minimal, relevant forms easy — and keeps the data typed and queryable so you only collect what you'll use."," Graph-based ",[52,414,416],{"href":415},"/knowledge/conditional-logic-in-forms","conditional logic"," shows sensitive or follow-up questions only when relevant, and because every field maps to a typed column, it's clear exactly what you store — the foundation of ",[52,419,421],{"href":420},"/knowledge/form-data-ownership","data ownership and privacy",{"title":147,"searchDepth":148,"depth":148,"links":423},[424,425,426,427,428],{"id":347,"depth":148,"text":348},{"id":363,"depth":148,"text":364},{"id":373,"depth":148,"text":374},{"id":391,"depth":148,"text":392},{"id":405,"depth":148,"text":406},"2026-03-14","Every field you add costs completion and risk. This research-backed guide explains how to decide what to ask, what to leave off, and how sensitive questions change both your data quality and your legal exposure.",[432,435,437],{"q":433,"a":434},"How do you decide which fields to put on a form?","Start from what you'll actually do with each answer. If a field doesn't route, qualify, personalize, or fulfil a real need, cut it. Every field costs completion, and under GDPR you should collect only what's necessary.",{"q":364,"a":436},"Anything you won't use, and sensitive data you don't truly need — research shows sensitive questions raise misreporting and refusals. If you must ask something sensitive, explain why, make it optional where possible, and ask it late.",{"q":438,"a":439},"Should form fields be required or optional?","Make required only what you genuinely need to proceed; mark the rest optional or defer it. Forcing optional fields to be required inflates abandonment and encourages junk answers.","/images/knowledge/what-to-ask-on-a-form.png",{},{"title":339,"description":430},[444,445,449],{"title":323,"url":324,"publisher":325},{"title":446,"url":447,"publisher":448},"Krosnick, J. A. (1991) — Response strategies for coping with the cognitive demands of attitude measures in surveys","https://doi.org/10.1002/acp.2350050305","Applied Cognitive Psychology",{"title":450,"url":451,"publisher":452},"Regulation (EU) 2016/679 (GDPR) — Article 5, data minimisation","https://eur-lex.europa.eu/eli/reg/2016/679/oj","EUR-Lex, European Union","knowledge/what-to-ask-on-a-form",[455,357,456,331],"question design","privacy",[458,459,460],"Decide fields by what you'll act on — every field costs completion, and GDPR says collect only what's necessary.","Sensitive questions increase misreporting and refusals (Tourangeau & Yan, 2007); ask them only if needed, and late.","Keep required fields minimal; defer or drop the rest rather than forcing them.","bxIdGpoSliDGGguGfP_6vI3hYQzp3v9UMUBAZvuyqU4",1780692427006]