My first answer was No, because I don’t even want to try. I make enough typo with the mechanical keyboards I’m used to, I don’t even want to start thinking about how I’d type on a phone :D
But the most interesting answer I could make is: Why? (implied: Why would I want to code on a phone?)
A phone is a nice device on the go. So the question is why would I have to code something on the go? The most likely answer is: because something needs to be done right now.
And now is the interesting part:
- if it doesn’t really require to be done right now, then chances are that if you wait to do it from your usual setup, with your usual tools, the code quality will either be better, and/or you’ll achieve the task faster. So why do it with a sub-optimal setup?
- if you know you might get a request that might force you to jump into a code-related activity asap, then there’s a long history: it’s called being on-call. And in such case, I except my on-call teammates to be a few minutes away from their laptop. If it’s really urgent, it’s because it’s related to prod. And nobody wants to use a trimmed-down experience when you need to investigate and fix production issues. When I’m on-call, I always make sure my laptop is a few meters away, battery charged and a reliable internet connection is available. And when I’m not on-call, or the issue isn’t prod related... then it can wait ;D
I might miss a valid use-case, but the truth is: I don’t see the problem we solve with such tools.