Angular developers work around gaps in form ergonomics
Angular developers building forms want to submit a form from its model, focus a field through a form control, and get more actionable errors when a template control is missing. The requests describe extra DOM references and manual searching as friction points. These signals are from 2017–2019, so they show historical pain but not whether the gaps or demand persist today.
For angular developers building template-driven and reactive forms. Mentioned from Sep 2017 to Jun 2019 on GitHub.
4 different people described this problem in 3 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 6.0/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Low
What people said
Quoted word for word. Follow a link to read the whole discussion.
Create an API on FormControl that would easily allow the input to be focused without having to resort to bringing in Renderer or ElementRef
This is literally one line of code, vs an additional class member for every single field in your form that you want to focus as well as template refs in the template to muddy up your template, @ViewChild decorators up the wazoo, and then you still have to add the line of focus code provided by what I just displayed her…
Build brief
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
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks