japagley

One of the best things you can do before building a new product is to start with the problem, not the product.

If you plan to build another form builder, what problem will you solve that the others do not? You should know the answer to this question before writing a single code line.

We did exactly this at Joyfill (http://joyfill.io/developers an embeddable form builder SDK for developers) — a problem was brought to us hundreds of times before we even considered building another form builder.

Joyfill (https://joyfill.io/developers):

A form builder and filler SDK for developers. We make it easy for developers to build form experiences into your SaaS infrastructure. From simple documents and PDFs to large complex dynamic forms. It gives you the tools to provide the very best form solutions that empower your users on every level.

First, congrats! I've seen a lot of form builders for public data collection pop up lately. What makes yours better?

Do your research before embarking on the journey to create another Typeform alternative or Typeform with a twist. There are robust form builders that serve multiple form use cases like Joyfill.io, Tally.so, Fillout.com, just to name a few. I've spent 10+ years in this space and just about every product needs forms of some kind, so definitely a ton of validation for it right now. I just don't want you to start on this endeavor if the problem has already been well solved.

Honestly, you are on the right track to focus on a specific niche or market regardless of the product you build.

We're working on Joyfill — A developer-friendly embeddable form builder that accommodates document-style complex form scenarios inside web and mobile apps.