1
3 Comments

A form builder where you own the data?

I recently launched a developer-focused form builder that has not gotten any traction. I'm looking for something to pivot to and I had this idea:

A form builder that uses your Firebase or Supabase database. Does that sound interesting to anyone?

on October 31, 2022
  1. 1

    Hey, I've a project that relies on a form builder at the core of the software but which sees 0% of it's differentiation from that form builder.

    So I'd love to outsource that form builder part of the business but that would require a lot more than just owning the data. It would be more akin to a dev white-label form-builder with great developer integration. Like a Stripe of form builders :)

    I think Firebase/Supabase are great storage options as they could also function as a sort of realtime API for the data that comes through the forms. But not everyone knows that either. So I'd focus less on "owning the data" (which probably always implies some lock-in in terms of the storage solution/DB you can offer) and more on "making the data accessible" / "freeing the data" -> create straightforward ways for me as a dev to work with the data, no matter if I'm coming from a Rails or JS or Python background. The backbone of that might still be a Firebase but that's an implementation detail I, as a user of your service would care little about.

  2. 1

    I'm struggling to understand your niche. I guess it's a developer that needs a form, but doesn't want to code their own solution AND wants to fully own the data?

    My hunch is that is too small of a niche, instead of thinking of a solution and asking if it's viable, are you able to get in touch with your potential user and see what functionality they are missing in existing tools?

  3. 1

    I'm not sure I've ever been concerned with my form data being "owned" by the service I'm using, but there could be a niche for it!