IdeaWell

Project ideas from Hacker News discussions.

IBM didn't want Microsoft to use the Tab key to move between dialog fields

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. IBM’s legacy ofusing Tab for field navigation
"Tab also has typamatic capability that allows you to move the cursor quickly from field to field." – ch_123

2. Enter key overloading creates user confusion
"The overloading of return to either send a message or add a newline has become really annoying since chat apps (and then now AI) have become popular." – bs​impson

3. IBM’s internal CUA politics and patent reasoning
"I would guess that using the tab key in this way was part of a patent they were pursuing and Microsoft's use would show this to be 'obvious' and thus not patentable." – rbanffy

4. Modern key‑binding inconsistencies (Enter / Shift‑Enter, CapsLock)
"Shift+Enter will usually enter a newline in a message without triggering send... No guarantees on specific applications, just my own experience with this." – track​er1

🚀 Project Ideas

TabSwitcher Pro

Summary

  • Eliminates tab‑key ambiguity by letting any application map Tab/Shift+Tab to explicit “next field / previous field” actions, regardless of OS defaults.
  • Users can define custom key sequences, avoiding surprises across different apps.

Details

Key Value
Target Audience Power users, accessibility advocates, developers of internal tools who need predictable field navigation
Core Feature System‑wide key remapper with per‑app profiles; visual overlay shows current field focus and next‑field shortcut
Tech Stack Windows: AutoHotkey + PowerShell; macOS: Keyboard Maestro + SwiftUI; Electron UI for settings; JSON profile storage
Difficulty Low
Monetization Hobby

Notes

  • Directly addresses “tab key hijacked by navigation vs insertion” pain point voiced in comments.
  • Potential for community‑driven rule sharing and discussion on HN.

EnterContext SaaS

Summary

  • Provides context‑aware virtual keyboards for web forms that automatically switch between “add newline” and “submit” modes based on modifier key usage.
  • Removes guesswork for users filling multi‑line text fields or validation‑heavy forms.

Details| Key | Value |

|-----|-------| | Target Audience | SaaS founders, HR platforms, e‑commerce checkout designers, and any web app with complex form interactions | | Core Feature | Embeddable widget that overlays a smart keyboard, detecting Shift/Enter and offering a toggle; integrates via simple API | | Tech Stack | Node.js backend, React front‑end, WebAssembly for low‑latency key handling, RESTful API for configuration | | Difficulty | High | | Monetization | Revenue-ready: Tiered pricing $0.01 per active form submission, up to $199/mo for enterprise |

Notes

  • Mirrors user frustration “Enter to advance / Ctrl+Enter to submit” – EnterContext makes the behavior explicit and configurable.
  • Could generate discussion on UI best practices and monetization of form‑UX utilities.

FieldFocus Overlay

Summary- Shows an always‑on‑top translucent overlay that highlights the active form field and indicates the action of the Enter key (newline vs submit) with subtle icons.

  • Eliminates the mental context of “do I need Shift?” by visual cue.

Details

Key Value
Target Audience End‑users of web portals, coding interview platforms, and any site with multi‑field inputs
Core Feature Lightweight browser extension that draws a field outline and a small tooltip when Enter is pressed, suggesting the intended action; optional sound cue
Tech Stack JavaScript (Vanilla), CSS transitions, Chrome/Edge/Firefox extension APIs, optional Web Worker for analytics
Difficulty Low
Monetization Hobby

Notes

  • Directly tackles “mental context of whether you need to hold shift before you press return” from commenters.
  • Minimal friction encourages adoption and can be discussed as a UI experiment on HN.

Read Later