IdeaWell

Project ideas from Hacker News discussions.

98% isn't much

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. 98 % can be “good enough”

“98% is plenty.” — pixl97

2. Business/market calculus

“Profit is often at the margin.” — silvestrov

3. Real‑world technical constraints

“I still have significant traffic at some clients from IE9.” — epolanski

4. Need for graceful degradation / progressive enhancement

“When you add something, are you choosing technology that is widely available and supported, or are you choosing to throw 0.N% of users under the bus for some benefit?” — ryandrake

🚀 Project Ideas

BrowserFeatureDetect

Summary

  • Solves the unmet need for automatic detection of unsupported browsers and graceful degradation of web apps.
  • Core value: Guarantees functional experience for every visitor, eliminating the “2% broken” pain point.

Details

Key Value
Target Audience Web developers maintaining public‑facing websites and SaaS platforms
Core Feature Real‑time browser capability detection with fallback routing
Tech Stack Node.js, CanIUse API, serverless functions
Difficulty Low
Monetization Hobby

Notes

  • HN commenters repeatedly mention loss of traffic from legacy browsers and the desire for automatic fallback handling.
  • Appeals to engineers who want to avoid costly manual testing while preserving full user coverage.

LegacyBrowserOverlay

Summary

  • Addresses frustration of users stuck on old browsers that lack modern CSS/JS features.
  • Core value: Provides a seamless layer that translates cutting‑edge features into compatible equivalents on‑the‑fly.

Details

Key Value
Target Audience Front‑end teams and SaaS providers targeting broad audiences
Core Feature Real‑time CSS feature translation proxy with polyfill generation
Tech Stack Python, WebAssembly, Cloudflare Workers
Difficulty Medium
Monetization Revenue-ready: $0.02 per pageview

Notes

  • Discussions around “graceful degradation” and the need to support users who cannot upgrade browsers highlight a clear market gap.
  • Developers want an off‑the‑shelf solution rather than manual polyfills, making this service highly desirable.

BrowserScorecard

Summary

  • Solves the ambiguity of how to interpret 98% vs. 2% support numbers for business decisions.
  • Core value: Delivers actionable analytics that quantify coverage and cost‑benefit of feature adoption.

Details

Key Value
Target Audience Product managers, engineering leads, and decision‑makers in web products
Core Feature Browser support heatmap & financial impact estimator
Tech Stack React, Python/Django, PostgreSQL
Difficulty Medium
Monetization Revenue-ready: $49/mo per project

Notes

  • Users in the thread stress the importance of data‑driven decisions when choosing to drop support for legacy browsers.
  • A dashboard that visualizes coverage and revenue impact would directly address that need.

GracefulFallback Kit

Summary

  • Tackles the repetitive effort required to write manual fallbacks for edge‑case browsers.
  • Core value: Offers plug‑and‑play components that automatically degrade gracefully with minimal configuration.

Details

Key Value
Target Audience Open‑source contributors, small dev shops, and hobbyist developers
Core Feature Declarative progressive‑enhancement wrappers for CSS/JS
Tech Stack TypeScript, Vite, PostCSS
Difficulty Low
Monetization Hobby

Notes

  • Commenters lament the “hand‑rolled” approach to handling old browsers and desire reusable tools.
  • An easy‑to‑integrate library that enforces graceful degradation would resonate strongly.

ImpactCalculator

Summary

  • Addresses the anxiety of losing revenue by dropping support for the “long tail” of users.
  • Core value: Interactive SaaS that models financial outcomes of browser‑support policies.

Details

Key Value
Target Audience Marketing analysts, financial planners, and product strategists
Core Feature Interactive ROI calculator for legacy‑support decisions
Tech Stack Next.js, Node.js, GraphQL
Difficulty Medium
Monetization Revenue-ready: $0.01 per calculation

Notes

  • Participants repeatedly ask how to quantify the cost of excluding 2% of users.
  • Providing a tool that lets businesses explore these scenarios directly fulfills an expressed need.

Read Later