Have something to say?
Fieldset And Legend
Helps with complex forms and those with identifiable sections. Example: https://v0.app/t/drPRsxPH9F1
Form with In between verification or validation
lets understand with example: suppose i wanna register a user, but on email submit i want inbetween email verification via otp or link and then after verification of email i will allow to put other things by user.
Duplicate Form Components for Faster Editing
While working on a long form, I had to scroll through the input list every time I needed a textarea. It would be great if we could duplicate an existing component in the form and edit it, instead of repeatedly picking it from the list.
Deep Object Input
I know this is my third submission today, but i feel like this app has a potential to make our work less repetitive and more standarized. Alright, here’s one for the advanced use cases: deep object input. This isn’t for your average name/email form. But if your users need to submit structured data, like nested objects or arrays (think config settings, dynamic rules, form templates, etc.), giving them a flexible way to input and manage that data is a huge win. Yeah, it’s niche. But if your form builder is used by devs, power users, or anyone managing structured setups, this is might be the good stuff. What Is “Deep Object Input,” Exactly? We’re talking about fields that let users input structured data like: { "settings": { "theme": "dark", "notifications": { "email": true, "sms": false }, "roles": ["admin", "editor"] } } So not just flat key-value pairs but nested objects, arrays, maybe even conditional structures. It’s like giving users a mini JSON builder UI without asking them to write raw JSON (unless they want to). Why This Might Be Useful For dev-focused apps or tools Users might need to define config options, API rules, or custom schemas. CMS or dynamic template systems Content blocks, UI layouts, or rules that need nested structure. Form logic and automation Think: “If user selects X, then do Y”which often ends up as deeply nested config. Better than raw JSON Nobody wants to debug a typo in a textarea. Structured input means valid, validated data every time. Final Thoughts Sure, this is a niche feature. But if you’re building a form builder for power users, or anything that deals with dynamic, nested data, having a deep object input is a game-changer. It gives your users superpowers and it makes your backend life way easier because the data comes in clean and predictable.
Geolocation (Coordinates) Input
Okay, let’s be honest not every form needs geolocation input. Most of the time, a name, email, and a few dropdowns do the job. But for certain use cases, being able to collect someone’s exact location (via coordinates) can be a game changer. Sure, it’s a niche need but when you need it, you really need it. Why Coordinates Can Be Super Handy Precision over guesswork No more “near the blue building” vibes users can drop a pin and be done. Great for map-based stuff Whether you’re plotting something on a map, calculating distances, or grouping locations, raw lat/lng makes it all possible. GPS is everywhere now Most phones can give their location instantly. Might as well make use of it when it makes sense. Works without a formal address Perfect for rural areas, pop-up events, temporary work sites, or nature spots where addresses just don’t exist. When It Actually Makes Sense to Use Field reports (like for inspections, surveys, or research) Delivery/pickup/drop-off forms Business or event location submissions Apps that deal with maps, logistics, or travel Emergency or incident reporting Basically, if a user is trying to tell you where something happened or where something is, coordinates are the most reliable way to get that info. How It Could Look A map view (via MapLibre) where users can drop a pin A button to auto-detect location using device GPS Latitude & longitude fields for manual input or copy-paste Optional: show the selected location as a preview on the map Final Thoughts Sure, not every form needs geolocation. But for those that do, offering pinpoint accuracy and multiple input methods (paste or pick) gives users way more control and makes the data way more useful. And with MapLibre, you keep things open, flexible, and free to scale. Let me know if you want a quick prototype or component sketch, will be happy to help!
Rich Text Input Suggestion
Let’s be real, plain text fields just don’t cut it anymore. If we want users to submit anything more than a short sentence, they need a better way to express themselves. That’s where rich text input comes in. It lets people format their text (like bold, italic, lists, links, etc.), which makes their content easier to read and understand. The Basic Idea Sometimes we want users to structure their thoughts clearly. Whether it’s a report, feedback, or a support ticket. Formatting helps a lot. When would this be useful? Long-form feedback or reports Rich support ticket descriptions Course answers or essays Custom email templates Anything where users need more context than just plain text
JSON Edit and $Schema
Add a $schema and JSON edit option, so that we can ask AI to create forms and paste it there. It will be useful in case of large forms.
Modifying the already created form.
I would like to store the JSON representation somewhere and be able to paste that into the form builder to start editing from the same place I left off. Is it possible?
Color Picker Component with preview
It would be greate if there is also a color picker for multipe formats like (hax, rgb, rgba)
Credit Card components
The regular credit card components: Card Holder, this can be just a regular input Card Number with formatting Expiration date, this one is tricky because it needs to have a popup on mobile for easy selection and also the validation. CCV or CVC, can also be just a number input. The amount of code it took me to make something that looks like e-commerce is insane, so maybe having it as a reusable component would be helpful for others.
Star Rating Component
I kinda plan to make an app for selling houses for a friend, i think it would be really nice if you have rating component
Value range picker with double slider
Description: A double slider component allowing users to select a minimum and maximum value within a defined range. The slider should support: Stepped Values: Customizable steps between values. Complete Values: Option to select whole numbers or specific values without steps. Dynamic Range: Ability to set min and max values. Optional Labels: Show current min and max selections above the handles. Optional Tooltips: Display the value while sliding. Use Case: Perfect for forms where users define numeric ranges — like price filters, age ranges, or percentage selections.