Project ideas from Hacker News discussions.

Mercedes-Benz commits to bringing back physical buttons

📝 Discussion Summary (Click to expand)

1.Preference for tactile physical controls

“Mercedes used to mean high, tactile, audible mechanical quality.” — aenis

2. German automakers lag behind Chinese EV competition

“Laudable. But I'd rather read about how they plan to fight Chinese EVs.” — amelius

3. Cost‑driven removal of buttons caused by cheap touchscreen strategy

“The only reason we got touch screens in cars at all is cost‑cutting.” — speedgoose

4. Regulatory pressure from China mandates physical buttons, influencing OEM decisions

“I’m quite suspicious that they do that not because they understood or learned something, but because China requires physical buttons starting next year. And they simply don’t want to lose one of their biggest markets.” — nokeya

5. UI design hijacked by software‑centric “product people” leading to unsafe, non‑intuitive car interfaces > “Engineers should be delegated to the worker‑bee level and you should just get some gear heads and some soccer moms to design to UI.” — bigstrat2003


🚀 Project Ideas

Universal Physical Button OverlayKit

Summary

  • Retrofit existing touchscreen cars with snap‑on tactile button panels, restoring physical feedback without replacing the whole infotainment system.
  • Enables drivers to control climate, volume, and cruise without looking away, addressing the core usability complaint from HN users.

Details

Key Value
Target Audience EV and luxury sedan owners (Tesla Model 3/Y, Mercedes EQ, BMW iX) who miss physical controls
Core Feature Modular 3D‑printed button modules that plug into the dash and connect via CAN to map to any function; configurable via a mobile app
Tech Stack STM32 microcontroller, CAN‑bus library, 3D‑printed ABS housings, React‑Native companion app, Node.js backend for firmware updates
Difficulty Medium
Monetization Revenue-ready: $5 /mo subscription for premium firmware and cloud mapping tools

Notes

  • HN commenters repeatedly lament the loss of “knobs and switches”; a tangible solution would be a direct answer to “bring back physical buttons”.
  • Could spark discussion about standardizing CAN‑based button mappings across OEMs and about safety‑critical UI regulations.

CarUX Feedback Aggregator

Summary

  • Centralized platform that collects and tags user experiences across car infotainment systems, surfacing recurring UI pain points.
  • Provides manufacturers with data‑driven insight to prioritize usability fixes and avoid costly redesigns.

Details

Key Value
Target Audience Auto OEMs, UI/UX design teams, automotive enthusiasts, regulatory bodies
Core Feature Crowdsourced review ingestion, sentiment analysis, heat‑map visualizations of problematic controls, public API for integration
Tech Stack Node.js backend, PostgreSQL, Elasticsearch, React frontend, AWS Lambda for processing
Difficulty Low
Monetization Revenue-ready: $199 /mo tiered SaaS for enterprise access and custom analytics

Notes

  • HN threads often ask “why do manufacturers ignore user feedback?” – this tool would make that feedback impossible to ignore.
  • Potential for community‑driven “feature request” voting that could influence future car UI roadmaps.

Glove‑Ready Touch UI Toolkit

Summary

  • Open‑source library that designs touch interfaces resilient to glove use, large tap targets, and haptic feedback, improving safety for cold‑weather drivers.
  • Offers designers a quick way to retrofit existing touchscreens with accessibility‑first layouts.

Details

Key Value
Target Audience Automotive UI developers, accessory manufacturers, safety consultants
Core Feature Glove‑detection API, auto‑scaling UI components, simulated haptic response, accessibility compliance checker
Tech Stack Unity (C#), Flutter, OpenGL ES, TensorFlow Lite for gesture modeling, MIT‑licensed documentation
Difficulty Medium
Monetization Hobby

Notes

  • Many HN users mention “touch screens don’t work with gloves”; a ready‑made solution would solve that pain directly.
  • Could spark debate on mandatory accessibility standards for vehicle interfaces.

Retro UI Theme Store for Car OS

Summary

  • Marketplace offering vintage‑style UI themes (physical button layouts, analog gauges) that can be installed on modern car infotainment systems via OTA updates.
  • Lets drivers personalize their dash while restoring tactile aesthetics that many miss.

Details

Key Value
Target Audience Car owners of Tesla, VW, Mercedes, and other modern EVs who want a nostalgic interface
Core Feature Downloadable theme packs with custom button graphics, voice‑controlled knob emulation, one‑click OTA installation
Tech Stack WebGL preview, React Native for OTA deployment, JSON schema for theme definition, Pay‑per‑theme pricing
Difficulty High
Monetization Revenue-ready: $9.99 per theme or $29.99 annual subscription for unlimited access

Notes

  • HN discussions about “bring back physical buttons” would likely adopt these themes as a stop‑gap solution.
  • Opens conversation about licensing of UI assets and the role of nostalgia in modern automotive design.

Automotive UX Research Simulator

Summary

  • Cloud‑based simulation environment that lets designers test infotainment prototypes under realistic driving conditions, scoring distraction and cognitive load.
  • Generates quantitative safety metrics before any physical prototyping.

Details

Key Value
Target Audience Automotive designers, safety engineers, academic researchers
Core Feature Scenario builder with vehicle dynamics, eye‑tracking model, distraction scoring, export to Unity or Unreal
Tech Stack Unity, AWS Batch, TensorFlow, WebGL UI, REST API for result retrieval
Difficulty High
Monetization Revenue-ready: $0.01 per simulated minute of usage (pay‑as‑you‑go)

Notes

  • HN participants often argue “touch screens are dangerous”; this tool would provide hard data to back those claims.
  • Could become a standard reference for regulatory bodies evaluating new car UI submissions.

Read Later