Developers struggle to fit form tools into their app workflows
Developers want forms to work inside their own projects and framework workflows, rather than being tightly coupled to an external service or forcing them to give up existing form features. The clearest pain is among SvelteKit developers who want to adopt Remote Functions without losing Superforms and Formsnap functionality or writing integration glue. Static-site developers also want form tools to fit their generator pipelines.
For developers integrating forms into web apps and static sites. Mentioned from Aug 2024 to Sep 2025 on GitHub and Hacker News.
5 different people described this problem in 3 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 5.2/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
We really want to start using Remote Functions but there is no way we can give up all of the features and functionality that Superforms (and Formsnap) provides
Here is the current logic I'm using to integrate the current version with remote functions for anyone interested https://gist.github.com/sillvva/6515b65d85075133de7c2e533b730e98
Build brief
See what to build and who will buy it
- 2 product ideas 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