Ask HN: Use cases for forms-based software tool?
We are working on a prototype of FormBig, a platform to quickly create forms-based software.
https://formbig.com/ [video]
To prioritize our development goals, we are looking for community feedback about:
1) What use cases would you use FormBig for?
2) What features are important for your use case?
11 comments
[ 3.3 ms ] story [ 36.2 ms ] threadWe found that there was a tremendously high hurdle to building forms-based applications to meet user expectations (eg rich-text editing, PDF generation, auto-saving, real-time collaboration, per-field versioning, etc). FormBig factors out this plumbing, allowing developers to instead focus on the specific forms, business logic, and end-user use cases instead.
Can you describe your use case a bit and the other platforms you have looked at thus far?
I cannot help but immediately want to compare it to Ruby On Rails or Microsoft's MVC framework. They both offer a lot of the plumbing for you, and leave the actual content to you.
Maybe it is more akin to Microsoft Lightswitch, not sure.
But that might be just from my misunderstanding. It should be noted I watched the video without audio, and it just shows someone entering XML and showing a form.
The original idea with the video was to show the types of functionality that FormBig exposes (eg: integrated logins, JS-based logic, rich text editing, etc) rather than the details of how one achieves them. However, I think since we went that path it is important to get more details in the body of the page.
Thanks for the pointer to MS Lightswitch I'm learning more about it now.
-Proper handling of an other field, like there is on paper forms. I.e. What is your favorite salad? a) Fruit b) Vegetable c) Other __________
-Ability to string multiple forms together in a workflow (kind of like a CRM). Form 1 must be completed before the user can move on to Form 2. However, when some or all of the fields are optional, there needs to be some type of trigger logic to mark the form in the workflow as completed. (I sort of saw this in the video, but it seemed that the forms were marked simply as steps and the end user could skip from Step 1 to Step 9)
-Sub-forms, both in terms of adding multiple contact addresses (for example) or switching from Sub-form A to Sub-form B in the context of a form workflow (you guys seems to have this)
-Permissions on every question and on every part (Form 1, Form 2, etc) in the workflow (you guys seems to have the question permissions down, but I'm not sure about the statistics)
-A rich query language to crunch statistics from every form field filled out (It seems your application outputs CSVs and leaves the user to crunch them in Excel)
-If a form is tied to an entity (say a Student, for example), the ability to assign that Student to a Teacher or an Administrator. (I did not see this)
-Ability for daily e-mail reports on what new forms have been created and updated and what new Students have been added to the system. (this was mentioned on the about section, but I did not see it in the video)
My forms framework does all this and more, but it took quite a bit of effort to build. I would be more than happy to talk specifics with you guys; my e-mail is in my profile.
I must warn you though, you are entering a rabbit-hole.
I think you said it well when you said you're entering the rabbit hole :). Building these types of applications is HARD, and there's a high barrier to MVP. We're currently working to get as much feedback as we can to scope our problem more narrowly. We've found interest from people in developing applications in government and K-12 especially - have you had similar experiences?
While its a tough nut to crack, we think if we can grab a toehold and iterate, this type of solution could save vast amounts of developer time.
For us, there wasn't a very high barrier to MVP. We went from initial concept to MVP in about 2 weeks using some of the ideas around superfast development I outlined in this talk [0].
Where the rabbithole came in is once we put out the MVP, we were bombarded with feature requests for things that were beyond simply an easier way to fill out forms (this is where alot of the CRM functionality came in).
We haven't reached out to anyone in government or K-12. We'd like to build our forms framework and keep it in this little niche market we've discovered and then start reaching out to other markets.
Our forms application has been very hard to build as well, but I think we are one major re-factor away from having a good platform. I'm thinking at the end of the day we are going to get something that looks like a cross between Redmine's CRM functionality and Drupal's modularity/observer pattern-ness/business logic in the database-ness.
What are you guys writing FormBig in? I'd be interested in collaborating on a set of open-source HTML5 form controls with you guys if that's something that you're finding a need for. It could address some of the things that I've found lacking in the standard HTML forms (such as the support for an other field and dynamic switching of sub-forms). I'm probably going to end up writing this library anyway, but it would be good PR for both of us :)
[0] http://www.slideshare.net/LeeGillentine/superfast-developmen...
We'll shortly be leaving the WP site. Please email me more information about your product. We might want to try it for the above and for new user sign up and preferences.
Many Thanks - Michelle Z., michelle@inthestacks.tv