11–20 of 20 posts
Where do the form responses go? Is it easy to connect them to get pushed to another system?
I've also worked on forms with a rule engine for nearly 3 years almost full-time (started in 2017). It's a hard problem. There are some commercial no-code and low-code solutions.
For forms with a rule engine you really want to have some debugger included that visualizes the data flow. Somehow people think one just has to author rules and then it's finished. And errors never happen.
I take a lot of inspiration by the work of Chris Granger, Bret Victor, and the "Future of Coding" community. But also the UI/UX of Notion and ObservableHQ.
Edit: Fix typos.
>Keenforms started as an idea and a side project. It took more than 3 years of evenings and weekends to get something worth releasing. I've also worked on forms with a rule engine for nearly 3 years almost full-time (started in 2017). It's a hard problem. There are some commercial no-code and low-code solutions. For forms with a rule engine you really want to have some debugger included that visualizes the data flow.…
I'm not familiar with any of the other no code or low code solutions available, can you share them?
>Keenforms started as an idea and a side project. It took more than 3 years of evenings and weekends to get something worth releasing. I've also worked on forms with a rule engine for nearly 3 years almost full-time (started in 2017). It's a hard problem. There are some commercial no-code and low-code solutions. For forms with a rule engine you really want to have some debugger included that visualizes the data flow.…
I'd be interested in connecting, hearing more about some of the challenges you've had. It is definitely a hard problem. I'm not familiar with any of the other no code or low code solutions available, can you share them?
There are at least two Switzerland-based and a US-based company, I'm aware of, working on rule-based forms (or questionnaires) in financial services. For instance Appway AG in Zurich (I'm not related to them).
The challenges seem to be always sort of:
- You have the business domain modelled in a relational (or document, or graph) database. You bind and synchronize the data between database and form.
- You have a rule engine, which uses e.g. RETE-OO, which fires the rules when some object types and some of their object attributes defined in the rule input match changes objects in the form. The rule action changes other fields of the form.
- You have a form editor where you can map form fields to entity attributes of the business model. Besides form components (text fields, selects, checkboxes, radio button groups) you can add headings and paragraphs. You can split forms into multiple pages and add (breadcrumb) navigation. You can add summary pages with an overview of the form data.
- You have a vanilla UI design for the forms but can customize the forms completely. Starting from custom CSS to different CSS frameworks. Tailwind CSS and Headless UI (unstyled UI components) seem to go into the right direction (not only for fancy write-once web-agency marketing websites, but also enterprise web applications). You want to implement the form fields/components and consider labels, error states, disable and hide styles, and accessibility.
Where do the form responses go? Is it easy to connect them to get pushed to another system?
They are saved to our database. At some point we hope to integrate with other applications so you can process that info as you see fit. This is the MVP, hoping to get more feedback on what potential users would see as beneficial to them. Thanks for the comment!
I’ve used Typeform’s webhook feature a number of times to good effect, whereby you receive one POST request to whatever endpoint you specify upon each form submission. This may have changed, but when I last used it that was the only way of getting your data out of their system, which was admittedly frustrating. A lot better than nothing though.
Used it for all kinds of things: quizzes hooked up to a loyalty program, to award the user points for all correct answers; satisfaction surveys after ordering a product; writing and photography competitions (again hooked up to the loyalty program); an in-depth annual user survey; etc.
A bit of feedback on accessibility. By the looks of your demo page, you're not using the 'for' attribute to associate form labels to their fields. This makes the forms very difficult to use for users of assistive tech, including screen readers. Screen readers read out the appropriate label when an input gets focus, but without the 'for' attribute it has no way of knowing which label is intended for which input.
A bit of feedback on accessibility. By the looks of your demo page, you're not using the 'for' attribute to associate form labels to their fields. This makes the forms very difficult to use for users of assistive tech, including screen readers. Screen readers read out the appropriate label when an input gets focus, but without the 'for' attribute it has no way of knowing which label is intended for which input.
I added the for tag to the labels, and deployed it this morning.