Web developers struggle to separate reusable components from styling
Developers building web apps, especially data-dense ones, want reusable components without being locked into a particular framework, bundled styling, or intertwined behavior. The requests differ on whether components should be CSS-only or include optional JavaScript, but share a desire to control those layers independently. One lower-intensity report also describes repeated stylesheet downloads from web components.
For web developers building custom applications. Mentioned from Apr 2024 to Aug 2026 on Hacker News.
4 different people described this problem in 4 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 6.5/10
- Frequency
- 5.8/10
- Willingness to pay
- 7.1/10
- Momentum
- 4.7/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Specifically, similar breadth, no JavaScript (and no npm), just lots of components styled using CSS. Willing to pay a $250/month subscription fee
I would pay really good money to have a library of web components that implemented only the document structure using semantic HTML and the Javascript interactivity, and kept all the styling on a separate CSS file
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 3 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks