Developers hand-build forms from changing data models
Developers and teams maintaining older software spend time placing, configuring, and updating form controls by hand, or building custom components to handle dynamic fields. Requests span Angular model-driven forms, JSON Schema rendering, and relational subforms; current approaches can miss needed schema support or leave developers handling edge cases themselves. A useful first product should focus on one target framework and a clearly defined input format rather than trying to replace every form builder.
For developers building data-driven forms. Mentioned from Jul 2018 to May 2026 on GitHub, Hacker News and Stack Exchange.
8 different people described this problem in 7 separate discussions.
- Indie fit
- 7.0/10
- Pain
- 6.0/10
- Frequency
- 7.9/10
- Willingness to pay
- 3.5/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Unfortunately there are no such tools when filtering the dialect to draft 2020-12. - Searching NPM for 'Json Schema 2020-12' only yields some validators, no schema to web ui packages
You have no idea, our dynamic form field component is huge so that we can cover each broken outlier
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 6 more quotes from people who have this problem
- Current workarounds, existing solutions and risks