There was recent mention about Forms not being prioritized because Fibery doesn’t feel it is important, but I wanted to express my opinion that I think Forms are absolutely critical to product team adoption.
My reasoning:
- A core function of product teams is to manage external input
- As a developer of a tool for product teams, you should be trying to minimize key friction areas
- Getting external input into Fibery has a very large amount of friction and adds cost beyond the core Fibery service cost
- Available workarounds are very labor intensive, slow, and error prone
- Available workarounds force us into using Fibery’s competitors to fill the gap (airtable, coda)
- These forms can’t be integrated into the Fibery experience
My current solution is to use Coda to recreate my Type I want to collect and build a form for it with help text, required fields, etc. You really need to model this out correctly so that you have the information you are expecting, which takes time. Then, I had to create an automation in Integromat to map the coda fields to Fibery’s fields. This automation can only be triggered by a timer, so there is no real time push for Coda, and I’m not sure there are any free form tools out there that would give real time push to Fibery.
To be completely honest, after I quickly built a form for this in Coda, then went through all the trouble with Integromat to get that working, I asked myself “If this was so easy, why don’t I just give Coda another try?” This is not something you want your Product Team target audience doing.