IdeaSift

Frontend developers hand-build UI when libraries don't fit their stack

Frontend developers who want to avoid a framework—or simply avoid hand-coding common UI—struggle to find reusable components that fit their stack. Framework-first kits can require React or a package-install workflow, while building behaviors like menus and state-driven updates by hand takes repetitive work. Some developers also want static components that need no JavaScript.

For frontend developers who want less hand-written UI code. Mentioned from Dec 2023 to Feb 2026 on Bluesky, Hacker News and Stack Exchange.

6 different people described this problem in 6 separate discussions.

Week of 2026-07-13: 0Week of 2026-07-20: 0Week of 2026-07-27: 0Week of 2026-08-03: 0Week of 2026-08-10: 0Week of 2026-08-17: 0Week of 2026-08-24: 0Week of 2026-08-31: 0Week of 2026-09-07: 0Week of 2026-09-14: 0Week of 2026-09-21: 0Week of 2026-09-28: 0
0 mentions in the last 12 weeks
Indie fit
5.0/10
Pain
5.3/10
Frequency
7.0/10
Willingness to pay
4.1/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.

  1. TailwindUI's 101% bet on React for the templates and catalyst is really sad. I would pay extra for TailwindUi vanilla js components
    naiv on Hacker NewsApr 2024Would pay
  2. I need an open source library written in vanilla TypeScript or JavaScript (i.e., no requirement of frameworks such as React or Angular) for building user interface for editor software such as video editors, and graphics editors
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
  • 4 more quotes from people who have this problem
  • Current workarounds, existing solutions and risks