Have something to say?

Tell us how we could make the product more useful to you.

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.

slaint 7 months ago

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!

slaint 7 months ago