A major theme is the physical difficulty of coding on a smartphone. Commenters discuss the pain of typing on touchscreens, the inability to view side-by-side diffs effectively on small screens, and the general clumsiness of managing terminal windows without a physical keyboard. Many users argue that while the setup is technically possible, the lack of screen real estate and input precision makes it impractical for serious engineering work.
← Back to Stop Doom Scrolling, Start Doom Coding: Build via the terminal from your phone
The debate over "doom coding" on smartphones reveals a sharp divide between those who view touchscreen development as ergonomic torture and those who see conversational AI as a revolutionary bridge across the mobile input gap. While critics lament the loss of physical keyboards and the impossibility of viewing complex code diffs on a cramped screen, enthusiasts argue that AI agents make mobile tinkering viable by replacing precise syntax with high-level prompting. For some, specialized tools like Neovim and Blink Shell transform transit time into a productive flow, though others warn that replacing necessary mental rest with constant "vibe coding" risks both physical strain and professional burnout. This shift suggests that while the smartphone remains a sub-optimal environment for traditional engineering, it is becoming an increasingly powerful canvas for rapid, "thumb-driven" prototyping.
69 comments tagged with this topic