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

Coverage Analyzer Pro

Summary

  • Provides website owners a real‑time coverage report of modern CSS/JS features based on their actual visitor stats, solving the “98% vs 2%” uncertainty.
  • Enables data‑driven decisions on graceful degradation, turning the uncertainty into actionable insight.

Details

Key Value
Target Audience Web developers and product managers of commercial sites
Core Feature Automated feature‑coverage dashboard with actionable fallback recommendations
Tech Stack Python, React, CanIUse API, analytics integration
Difficulty Medium
Monetization Revenue-ready: tiered subscription

Notes

  • HN commenters repeatedly asked for a way to quantify the long‑tail of unsupported browsers; this tool answers that need.
  • Generates discussion about data‑driven graceful‑degradation thresholds and cutoff decisions.

Graceful Degrader CLI

Summary

  • Generates fallback HTML/CSS/JS automatically when a modern feature is added, ensuring the site still works for older browsers.
  • Lets developers set a coverage cutoff (e.g., 98%) and outputs minimal degradation code.

Details

Key Value
Target Audience Front‑end engineers who want progressive enhancement without manual polyfills
Core Feature CLI that reads a feature list and outputs fallback bundles with browser‑support scores
Tech Stack Node.js, PostCSS, Sass compilation, CanIUse JSON data
Difficulty Medium
Monetization Hobby

Notes

  • Directly addresses the “CSS nesting all‑or‑nothing” frustration discussed on HN; users would love an automated safety net.
  • Can be integrated into CI pipelines for regression testing on legacy browsers.

Browser Tail Dashboard

Summary

  • Visual heat‑map of browser version usage across your traffic, highlighting any segment below a chosen relevance threshold.
  • Flags when a specific legacy version drops below a configurable coverage line.

Details

Key Value
Target Audience Site operators and analytics teams
Core Feature Interactive dashboard overlaying feature‑support matrix on real usage data
Tech Stack Elixir/Phoenix backend, D3.js front‑end, integrates with GA/Amplitude
Difficulty High
Monetization Revenue-ready: usage‑based pricing (first 10k visits free, then $0.001 per visit)

Notes

  • Makes the abstract “98% coverage” concrete for each site, a tool HN would love to explore.
  • Sparks conversation about when to drop support for ancient browsers like IE11.

Legacy Browser Compatibility API

Summary

  • API endpoint that returns a JSON matrix of which HTML/CSS/JS features work on any given user‑agent, with suggested graceful‑degradation snippets.
  • Enables server‑side rendering to strip or replace features based on detected coverage.

Details

Key Value
Target Audience Backend developers building content platforms or SaaS that must guarantee minimal rendering on old browsers
Core Feature REST API delivering feature‑support data plus recommended fallback code
Tech Stack Go micro‑service, Docker, cached CanIUse DB, OpenAPI spec
Difficulty High
Monetization Revenue-ready: pay‑per‑request + monthly plan

Notes

  • Solves the “how do I know if my site breaks for 2% of users?” question directly, appealing to HN’s technical audience.
  • Provides a concrete reference point for debates on maintaining legacy browser support.

Read Later