IdeaWell

Project ideas from Hacker News discussions.

Just the Browser

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Here are the 3 most prevalent themes from the Hacker News discussion:

1. Frustration with Excessive and Unnecessary UI/UX "Innovation"

Many users feel that modern interfaces have become overly complex and chaotic, prioritizing novelty over usability and stability. They express a longing for the "solved" standards of the past, where interfaces were predictable and reliable.

"I grew up on DOS, and my first browser was IE3... I remember Firefox being revolutionary for simply having tabs... Are those days permanently gone? The days when actual UI/UX innovation was a thing?" — publicdebates "I feel like wishing for UI innovation is using the Monkey's paw. My web experience feels far too innovative and not enough consistent. I go to the Internet to read and do business not explore the labyrinth of concepts UI designers feel I should want." — robviren "Some stuff has been solved. A massive number of annoyances in my daily life are due to people un-solving problems with more or less standardized solutions due to perverse economic incentives." — gary_0

2. The "Anti-AI" Backlash in Browsers

A significant portion of the discussion focuses on resistance to generative AI features being forced into browsers (e.g., Copilot, LLMs). Users view these additions as intrusive, resource-heavy bloat that detracts from the core function of a web browser.

"publicdebates: > aims to remove: Most AI features, Copilot, Shopping features, ..." — publicdebates "It was chrome, downloading a multi GB file without any sort of UI hints that it was doing so. A generative AI file." — brody_hamer "Why would it be funny though? Am I missing something?" — publicdebates (referring to the AI model files, implying a lack of transparency)

3. The Stagnation of Fundamental Computing Standards (The QWERTY Debate)

The conversation frequently circles back to whether we are stuck in a "rut" with established technologies like the QWERTY keyboard layout. While some argue we need to break free from legacy standards to innovate, others defend "good enough" solutions that provide stability.

"For instance, the QWERTY keyboard layout exists to prevent typewriter keys from jamming, but we're stuck with it because it's the 'standardized solution'..." — bigfishrunning "Sometimes good enough is just good enough" — jaapz "These days QWERTY keyboards are optimal because programs, programming languages and text formats are optimized for QWERTY keyboards." — account42

🚀 Project Ideas

Browser UI Customizer

Summary

  • A browser extension or standalone tool that lets users restore and customize "old-school" UI elements (like thicker scrollbars, standard form controls, and predictable keyboard shortcuts) across websites.
  • Provides a consistent, stable, and predictable interface layer, overriding the "creative" and often inconsistent UI choices made by modern web applications.

Details

Key Value
Target Audience Power users and developers frustrated by constant UI changes and poor UX on modern web apps.
Core Feature Injects a standardized CSS and JS layer to enforce familiar UI paradigms (e.g., classic scrollbars, form elements, keyboard navigation) on any visited site.
Tech Stack WebExtension API (JavaScript, CSS). Could be packaged as a desktop app using Electron/Tauri for system-wide application of settings (where possible).
Difficulty Medium
Monetization Hobby (Open Source)

Notes

  • HN commenters would love this because it directly addresses the frustration with "un-solving" solved problems. As gary_0 said, "I don't want a car with an 'innovative' way of steering." This tool restores the "steering wheel."
  • Potential for discussion on web standards vs. application-specific design, and the accessibility benefits of consistent UI controls.

Local-First Tab Manager

Summary

  • A dedicated, lightweight desktop application that manages browser tabs for research and workflows, decoupling them from the browser's ephemeral session state.
  • Allows users to organize tabs into projects, annotate why a tab is open, and visualize non-linear research paths, solving the "labyrinth of concepts" browser tab problem.

Details

Key Value
Target Audience Researchers, students, and anyone who keeps dozens of tabs open for context, leading to browser bloat and "front end exhaustion."
Core Feature Manages tab sessions as persistent, shareable projects. Includes visualizations of tab relationships and "why I left this open" annotations.
Tech Stack Rust or Go (for speed and low resource usage), Tauri or native OS UI frameworks (Swift/WinUI) for a responsive interface.
Difficulty High
Monetization Revenue-ready: Freemium model with a paid tier for cloud sync and unlimited projects.

Notes

  • HN commenters expressed a desire for better tab management beyond simple grouping. basch noted, "Contextualizing why I am leaving something open vs closing it is information ONLY stored in my head."
  • This separates the "document structure" of the web from the "browsing experience," allowing for true innovation in workflow management without needing browser vendor support.

Ergonomic Keyboard Layout Enforcer

Summary

  • A background service and driver that remaps standard QWERTY keyboards to ergonomic layouts (e.g., Dvorak, Colemak, or custom ortholinear mappings) at the system level, bypassing OS limitations.
  • Specifically targets the "local maxima" problem of hardware keyboards, making it easier for users to try alternative layouts without buying specialized hardware.

Details

Key Value
Target Audience Developers and typists suffering from RSI or seeking higher WPM, but unwilling to buy expensive custom hardware.
Core Feature Low-latency, system-wide key remapping with easy toggling and profile management. Includes a visual overlay for learning.
Tech Stack C++ (for driver-level hooks on Windows), Swift (macOS), and Linux kernel modules (evdev). UI in a lightweight framework like Flutter.
Difficulty High
Monetization Revenue-ready: One-time purchase or "Pay What You Want" for the software.

Notes

  • Directly addresses the bigfishrunning point about being "stuck in a rut" with QWERTY. While hardware innovation is stifled, software can lower the barrier to entry for layout experimentation.
  • cons0le noted that custom layouts are for enthusiasts; this tool aims to democratize that experience for the mainstream user.

Standardized Rich Textarea

Summary

  • A drop-in JavaScript library (and eventually a browser-native proposal) that provides a robust, standardized rich text editor component for the web.
  • Solves the fragmentation issue where every site reinvents the wheel (often poorly) for text input, providing a consistent experience for writing and formatting text across the web.

Details

Key Value
Target Audience Web developers and site builders who want to offer text input without the bloat and inconsistency of existing solutions.
Core Feature A semantic HTML-based editor that outputs clean, standardized HTML. Includes built-in support for tables, lists, and basic formatting without heavy dependencies.
Tech Stack Vanilla JavaScript, Web Components. Could be contributed to browser engines (like Chromium) as a native HTML element (e.g., <rich-textarea>).
Difficulty Medium (Library) / High (Browser Native)
Monetization Hobby (Open Source Standard)

Notes

  • HN users lamented the lack of standardized controls. wvbdmp asked, "what's stopping browsers from shipping these standard controls?" This project aims to fill that gap.
  • It addresses the frustration with "inventing or depend[ing] on large amounts of JS to get anything decent," aiming to make the web more usable and accessible by default.

Read Later