There are mant factors, and you listed several good ones, but I think the most important one you missed is ergonomics. Rarely is coding something you do for ju

There are mant factors, and you listed several good ones, but I think the most important one you missed is ergonomics. Rarely is coding something you do for just 20 minutes or even for just 2 hours. The smallest projects are measured in days of work, the largest in person-years. As a programmer, your body needs to engage with your workstation for most of that time. If you try to do that entirly on a small, portable device with on-screen input, you’ll quickly discover how poorly your body can sustain the necessary postures. That’s not to say that mobile coding tools aren’t useful. Punching in some extra lines on the couch or on the train or in the bathroom at a boring Holiday party is a great opportunity to exploit, but it will always be a secondary mode. And because it’s secondary, tooling will be slow to keep up with what’s available on primary workstations. Will we reach a point where you can punch together a whole useful program on a mobile device? Sure, but they’ll usually be smaller and simpler programs and will probably beneifit from visual programming languages that operate on large-grain components. More like automation scripting than systems-level programminng. Apple’s new Siri Shortcuts are an example for personal/consumer scripting. You could see similar tools succeeding for Enterprise Reporting, DevOps, etc. TLDR; it is and will be a specific niche for a number of reasons, not the least of which are the ergonomic concerns.