Alt Editor
Role
Product Design, Interaction Design
Team
PD 1, FE 1, BE 1
Timeline
2022–2023
Platform
Web Application
Link
01 / OVERVIEW
THE
CONTEXT
Alt Editor is a web-based subtitle editor designed to serve two distinct user groups with a single interface. It aims to innovate the traditionally slow subtitling process with three goals:
- AI Automation: Automate subtitle creation.
- Beginner Accessibility: Enable obstacle-free completion of the first subtitle.
- Power User Efficiency: Provide keyboard-centric fast editing workflows.
The core challenge was guiding novices while not hindering experts within a single interface.
02 / CHALLENGE
PROBLEM &
CONSTRAINTS
Traditional subtitling is slow and complex, requiring transcription, timecode adjustment, and verification. I had to satisfy two conflicting user needs:
Beginners
- Struggle with workflow
- High entry barrier
- Prefer mouse interaction
Power Users
- High repetition fatigue
- Resort to workarounds if unsupported
- Prefer keyboard interaction
Additionally, I had to resolve browser/OS reserved key conflicts while serving both groups in one product.
Single Interface, Dual Flow
03 / PROCESS
KEY
DECISIONS
Analyzed competitors (Subtitle Edit, Vrew) and professional workflows. Established the principle: "Separate flows by behavior, but keep a single interface."
1. Beginner Flow (Mouse-centric)
- Intuitive Layout: Core actions (timeline, merge/split) fixed at top/near timeline.
- Click-Only Completion: Designed to complete "Navigate → Select → Edit → Export" with mouse only.
- Onboarding: Overlay and short guide video to show clear starting point.
2. Power User Flow (Keyboard-centric)
- Alt Shortcuts: Designed Alt-based set to avoid browser/system conflicts.
- Two-Hand Pattern: Distributed keys for seamless Typing ↔ Play/Pause ↔ Timecode adjustment.
- Learning: Persistent shortcut hint bar to induce natural learning.
3. Web Constraints & Visibility
- Simplified State: Visible selection, modification status, and export readiness at a glance.
- Combined Solution: Alt mapping + Context Menu + Real-time Chatbot.
- Progressive Disclosure: Core features first, advanced features revealed by proficiency.
4. Resolution & Adaptability
Although mobile support was excluded, I conducted user research to ensure usability on small laptops (e.g., 13-inch screens) and designed the interface accordingly.


Web Constraint Solutions
04 / OUTCOME
IMPACT &
RESULTS
Achieved ~3,000 cumulative users. The editor structure and shortcut system became the foundation for the SUBUP Workspace translator editor.
Impact & Limitations
- Organizational Impact: Unified flow, Alt shortcuts, and state visibility designs reused as reference.
- Limitation: Improved expert speed, but failed to data-validate beginner completion rate.
- Regret: Deprioritized beginner error recovery (Undo/Redo) and save funnel optimization to solve browser constraints.
Key Learnings
- Constraints First: Map browser/OS reserved keys early for consistent design.
- Observability = Outcome: Prepare logs/event maps before features to track real-time funnels.
- Separate Mechanisms: Beginners need guardrails (modals, chatbot); Experts need efficiency (shortcuts, menus).