We have recently created a nice Web application that assists clients in building online forms. Most forms are simple tools and do not need to be custom crafted, just so long as they handle the back end properly. Forms are such a ubiquitous feature on Web sites that it becomes easy to forget that there can be some complicated maneuvers required under the hood. Because many of our clients handle sensitive information through their sites (hospitals, banks), we needed to layer in some simple-to-use yet industrial-strength security.
Of course, I could go on about how spiffy the app is, but that isn't the reason for this post. The reason for the post is, we can't figure out what to name the damn thing.
We are skilled at mapping things out, specifying them and creatively solving online problems. We kinda suck at names.
So far, here's what we've come up with:
FormBuilder
ForMaker
FormCreator
FormBundle
FormScaper
FORMulate
FORMulaic
Not particularly demonstrative of creative minds at work. Then it quickly gets silly:
Formidable
Formulary
FormalWare
Forment
Formication
Formaldehyde
Internally, we started calling it FormBuilder. Some now call it FormBundle. I've heard it referred to as The Form Thing. Undoubtedly there are other code names floating around Imaginary, most unsuitable for a general audience.
I entered this naming process believing it to be trivial. Now that I'm immersed in it, I shall never again mock the latte-sipping branding crowd (okay, that's probably not true). But I will pause to remember how close we once came to creating a product called The iFormScapeCreatorBundle.
Updated 07/14/10 @ 10:50AM CDT by brian
Imaginary Landscape


