Weavely

What Weavely is

Forms are assembled inside a design application here. Pieces come from a component library in that program, so how one looks is decided where the designer already works rather than in an editor offering fixed layouts.

What gets published is a working web form carrying logic and somewhere for answers to go, which is usually the stage forcing a designer to pass the work to somebody who can build it. Note first that the maker's own address returns not-found, both bare and abbreviated, so nothing came from its marketing — this rests on help pages and on its listing in a design tool's community.

What you can do with it

Elements drop in from that library and the design goes live as something interactive rather than being exported as a picture of one.

Logic can depend on earlier answers, so questions appear or vanish, which is the difference between a form and a questionnaire in a document. Answers are gathered and can be forwarded through connections, so results reach wherever the work continues instead of staying in one tool. Appearance is as free as a design file, which is the entire argument: the limits of a usual builder disappear, and needing a developer is meant to disappear with them. No amounts could be read, since no pricing page was reachable, and neither an operating company nor a publication date nor an author appeared anywhere available.

Who it is for

Designers and product groups needing a form to match a brand precisely, unwilling to accept whatever layouts a builder offers.

Studios and compact teams building things for others come next, because an unusual-looking form is among the things a client notices and has paid for.

Teams wanting logic nobody can quietly break may prefer a conventional builder with validation built in. Where appearance is what the client is buying, this removes the argument about what the form should look like.

What to watch out for

Answers typed into a form are how personal information reaches a company, and putting one live means taking on the obligations: a lawful basis for every field, a statement of purpose, a retention period, and a way for somebody to ask for deletion. Designing it attractively discharges none of that, and something tailor-made reads as more credible than a plain one, which strengthens rather than weakens the duty to say clearly what you are gathering.

Questionnaires assembled away from engineers are likewise where questions multiply. Requesting somebody's date of birth or a government number simply because it occurred to whoever designed it gathers protected information for no stated reason, and the freedom that makes this appealing arrives without the prompt a builder might give about why a field is needed. Embedded in a site a visitor recognises, nothing tells them which service actually receives the answers, so which party handles answers and the country holding them belong settled in writing before anybody replies — people cannot agree to terms the publisher never read. That the main address returns not-found is itself the thing to resolve: its documentation and its entry in that program's library both respond, so something is there, though sales pages failing while help pages work ought to be raised with the seller before depending on it.