Why I Built Fennec Forms

I did not build Fennec Forms because the world needed one more form builder.

I built it because I kept running into the same frustration: the tools already in use around me were capable, established, and deeply embedded in real business workflows, but they felt painfully antiquated.

The two platforms I came to know best were DragonForms and Wufoo. DragonForms is heavily integrated into the Omeda Customer Data Platform, and within that constraint it does its job well. Wufoo has also been around long enough to build a strong feature set and a loyal user base. This is what made the problem so obvious to me. The issue was not that these platforms were empty or weak. It was that they felt old in all the ways that matter when you actually have to use them every day.

The frontend experience especially always stood out. Too many forms in this category still look like they were pulled from a web design time capsule buried somewhere around the turn of the century. The styling feels stale. The interactions feel stale. The experience for respondents feels stale. And once you notice that, you start seeing the same thing on the creator side too. Even when the underlying functionality is strong, the overall product can still feel rigid, clunky, and out of step with how people expect software to work now.

That gap is the reason Fennec Forms exists.

I wanted to build something modern, flexible, and device agnostic for both respondents and creators. Not modern as a cosmetic layer pasted over an old workflow, but modern in the way the platform behaves. It should feel good to build in. It should feel natural to respond to. It should work whether someone opens it on a phone, a tablet, or a desktop. It should hold up whether it lives on a hosted page, inside an embed, behind a QR code, or as part of a broader workflow. It should work anywhere.

That also meant building around the reality that forms are not just forms. Sometimes you are collecting information. Sometimes you are gathering feedback. Sometimes you are running a quiz or assessment. Sometimes you need a direct link. Sometimes you need an embed. Sometimes you need kiosk mode. Sometimes you need to understand exactly where responses came from and keep them organized for a whole team. I wanted Fennec Forms to reflect that reality instead of forcing everything through one stale, generic interface.

A big part of the motivation was respect for the people on both sides of the screen. Respondents should not feel like they are wrestling with a relic just to fill out something simple. Creators should not feel like publishing a polished, flexible form requires compromising on usability or presentation. If forms are often the first interaction someone has with an organization, then the experience matters. A bad form does not just feel inconvenient. It makes the organization behind it feel behind.

The name Fennec Forms comes from that same thinking.

I love foxes, and the fennec fox in particular felt like the right symbol for what I wanted this platform to be. A fennec fox is lightweight and agile, but also highly intelligent. That combination is the ethos behind Fennec Forms. I wanted the platform to feel light on its feet, easy to use, and adaptable to different situations, without sacrificing depth or thoughtfulness. In other words, I did not want “simple” to mean limited, and I did not want “powerful” to mean bloated. The goal was a platform that could move quickly, work anywhere, and still feel smart and capable underneath the surface.

That is really the heart of it.

Fennec Forms was built as a response to a category full of tools that proved how much functionality matters, but also how long bad experience can survive when software becomes entrenched. I took that seriously. There is real value in the depth those older platforms built over time. But I do not think antiquated UX, outdated presentation, and device-fragile experiences should be accepted as the price of maturity.

Fennec Forms is my attempt to build something better from that lesson. A platform that is flexible without feeling chaotic. Modern without feeling trendy. Capable without feeling heavy. Something that helps people create forms, surveys, and quizzes that work anywhere and feel like they belong on today’s web, not yesterday’s.

That is why I built it, and that is what the name is meant to capture.