Forms are conversations, not database rows
What changed when we redesigned Orbit Forms around respondents, reviewers, and the awkward space between them.
A form builder can look complete while producing a miserable form. Add a text field, add a select, save some JSON, declare victory. The missing part is that forms are used by three different people: the author trying to ask clearly, the respondent trying to answer confidently, and the reviewer trying to make a fair decision later.
The author needs structure, not configuration noise
The new editor separates the question palette, the live document, and the selected question’s settings. Authors can reorder questions, divide work into pages, preview the respondent view, set Discord requirements, and combine conventional inputs with visual choice cards, scales, ranking, consent, and section content.
The respondent needs momentum
Public and official forms now use the same focused layout, clear progress, consistent identity notices, readable pages, and phone-friendly controls. Temporary workspaces no longer appear as an empty input floating in the middle of a large screen. Context, status, required actions, and completion are visible together.
The reviewer needs evidence
A submission is rendered as the form the person actually answered, with long text allowed to breathe and compact answers kept compact. Reviewers can see total completion time, time per field, identity context, internal notes, the decision history, and four-eyes state without opening a sequence of broken review links.
The best form is not the one with the most field types. It is the one where nobody has to ask what happens next.
Our product rule for Orbit Forms