I tried every day in August before realizing that no date in August would work. An 'x' or something or changing the icon to a cancel icon might have worked better. Also the calendar icon did absolutely nothing when clicking on it. Same thing with the email icon.<p>Sliders for inputting numbers? As my only option for inputting numbers? No thanks!
A couple things I noticed:<p>- Validation is very slow. It was averaging out to about 5s per submission. This should be able to be done almost instantly on the front-end.<p>- The email input is validated with the type="email" HTML5 attribute. If you write something that doesn't pass, the notification appears (about) 400px above the form. If you write something that does pass, technically, such as "abc@abc", it is returned, by FormCraft, as invalid.<p>- It would be nice if the input button was clickable, although I can see that this would be more of a Bootstrap thing.<p>- I'm not sure how I feel about that Budget sliders reading "0-0" and, once clicked on, reading completely different numbers. If there is a minimum, why not show it?
FYI when I click on "Try the form builder" I get a 500 internal server error<p><pre><code> Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@ncrafts.net and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache Server at ncrafts.net Port 80</code></pre>
There's no fallback for browsers that do not support javascript or have it disabled. That's annoying for users of special devices, NoScript, but likely also people who are blind and use screenreaders, for example.<p>Accessibility deserves <i>at least</i> to be an afterthought.
I've got a bit of a gripe with the "Job Application" form. Asynchronous saves aren't really intuitive to a lot of users -- if you're a web developer who understands AJAX (and the fact that there's a server with a database actually storing the data somewhere), then it makes sense. But if you're an average person who doesn't immediately know the mechanism it can be confusing. At work I recently converted a portion of our UI from this style of saving to an explicit model specifically to avoid this problem.
Very cool. I like how it works, but I'd love to know how it converted compared to other types of forms. Simply some A/B testing would do the trick, no?<p>It reminds me of the credit card form someone posted here, and the discussion that followed.
Great concept. One issue with the dynamically appearing forms is you don't know how long they will go on for. This will lead to people abandoning the form even though they may be 1 step away from completion.