IdeaWell

Project ideas from Hacker News discussions.

Why don't more developers “use the platform”?

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Theme 1: Native platform features often lack required functionality

“We need a date picker to schedule a visit.” “Okay, use <input type=date>” “It needs to be a date in the future.” “No problem, add a min="2026-10-05" attribute.” “And we’re only available on weekdays.” “Okay, throw the native date picker away completely and build one yourself from scratch.” – JimDabell

Theme 2: Developers prefer libraries/frameworks for better developer experience and convenience

“I actually still use Dragula. I can't quite put my finger on it, but it just feels better than Sortable. I may be imagining it, but I also don't care because, you know, it's just a JS library.” – sodapopcan

Theme 3: Platform evolution is hampered by misaligned incentives and insufficient investment

“But with the balance shifting in favor of the web, new incentive perversions arose. To sell cloud bullshit and lock people into their platforms, web companies obviously don’t want you to have a good time developing or hosting competing products…” – wvbdmp

🚀 Project Ideas

Generating project ideas…

FlexiDate: Configurable Accessible Date Picker

Summary

  • A lightweight, framework‑agnostic date picker component that lets developers easily disable arbitrary dates, restrict weekdays, and enforce i18n accessibility while keeping the native look‑and‑feel.
  • Core value: replaces the need to build custom date pickers from scratch by exposing a simple API for complex constraints that the native <input type="date"> lacks.

Details

Key Value
Target Audience Frontend developers building forms, SaaS apps, or internal tools who need precise date selection logic
Core Feature Programmable date disabling (single dates, ranges, weekday masks) + keyboard/screen‑reader support + optional styling hooks
Tech Stack TypeScript, Stencil (web‑component compiler) or plain JS with optional React/Vue wrappers
Difficulty Medium
Monetization Revenue-ready: SaaS subscription for premium themes & priority support ($9/mo per seat)

Notes

  • HN users complained that native date pickers cannot exclude specific dates or weekdays (e.g., “only weekdays”) forcing them to abandon the platform (JimDabell, pwdisswordfishq).
  • Provides a drop‑in replacement that works across browsers, including iOS Safari, reducing the need for custom JS date‑picker libraries and the associated accessibility bugs.

DialogEnhancer: Backdrop‑Close & Focus‑Trap Polyfill for `<dialog>`

Summary

  • A tiny utility (≈2 KB gzipped) that adds reliable backdrop‑click dismissal, focus trapping, and ARIA‑consistent behavior to the native <dialog> element, fixing the missing default close‑on‑backdrop and iOS Safari issues.
  • Core value: lets teams keep using the semantic <dialog> while gaining the UX polish users expect from modal dialogs without writing repetitive boilerplate.

Details

Key Value
Target Audience Web app developers who rely on <dialog> for modals but need consistent closing behavior and accessibility across devices
Core Feature Automatic backdrop click handler, focus‑in/out management, optional animation hooks, works in SSR environments
Tech Stack Plain JavaScript (ES2022) with optional TypeScript declarations; can be imported as an ES module
Difficulty Low
Monetization Hobby

Notes

  • Commenters noted that <dialog> lacks backdrop dismissal by default and needs hacky JS or the poorly supported closedby attribute (VoidWhisperer, JimDabell).
  • By solving this pain point with a zero‑config import, DialogEnhancer encourages adoption of the native element, aligning with the “use the platform” goal while improving UX.

HeadlessUI‑Primitives: Accessible, Unstyled Building Blocks for Troublesome Widgets

Summary

  • A collection of headless (logic‑only) components for date pickers, comboboxes, multi‑selects, and dialogs that expose state and accessibility primitives, allowing developers to apply their own CSS/Tailwind/Styled‑Components.
  • Core value: eliminates the need to reinvent accessibility and interaction logic for commonly problematic native controls while preserving full design freedom.

Details

Key Value
Target Audience Design‑system teams and product engineers who want full visual control but need reliable, accessible behavior for complex inputs
Core Feature Stateful primitives (open/close, focus management, keyboard navigation, ARIA attributes) with framework bindings for React, Svelte, Vue, and Solid
Tech Stack TypeScript; provides separate adapters per framework; bundle size <5 KB per primitive
Difficulty Medium
Monetization Revenue-ready: Marketplace sale of premium primitive packs ($49 one‑time) or open‑source core with paid enterprise support tier

Notes

  • Multiple commenters lamented that native elements lack features like searchable comboboxes, accessible multi‑selects, and customizable dialogs (usernomdeguerre, sebastiangrill, Joker_vD).
  • By providing the interaction logic without imposing styles, HeadlessUI‑Primitives lets developers build exactly the UI they need while avoiding the accessibility pitfalls that drive them away from the platform.

Read Later