Yeah, I'm backseat driving and I'm sure they know what they're doing. I would think a good mobile workflow would be one that emphasizes the discussion portion with issues, but also has a custom interface for PR review. I'm not convinced a lot of that can't be done on the phone, it would just take some innovation, and it would help if they got something out and then iterated. Eventually I bet it could work with some intuitive gestures, etc.
It would be interesting to see if, say, GitLab wanted to challenge GitHub in this arena and get a headstart. Of course, it's harder for the smaller company to go multi-platform. It's certainly why our tiny team hasn't worked on a native app even though a lot of our traffic is mobile.
Despite my blowhardedness, this is probably the right choice. The mobile web is getting better and better. Has GitHub ever talked publicly about their reasoning for these choices?
As much as I really push for not needing a native solution for apps that can work well on the mobile browser, I've always felt the need to rely on a third party native GitHub client. Couldn't find any that were completely free and had everything that I needed, so I built GitPoint :)
This article was really the only mention I've heard about their mobile website but haven't heard anything about their reasoning either. Definitely curious as well.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yeah, I'm backseat driving and I'm sure they know what they're doing. I would think a good mobile workflow would be one that emphasizes the discussion portion with issues, but also has a custom interface for PR review. I'm not convinced a lot of that can't be done on the phone, it would just take some innovation, and it would help if they got something out and then iterated. Eventually I bet it could work with some intuitive gestures, etc.
It would be interesting to see if, say, GitLab wanted to challenge GitHub in this arena and get a headstart. Of course, it's harder for the smaller company to go multi-platform. It's certainly why our tiny team hasn't worked on a native app even though a lot of our traffic is mobile.
GitHub did have a mobile app. They decided to discontinue the development in favour for a mobile website.
Despite my blowhardedness, this is probably the right choice. The mobile web is getting better and better. Has GitHub ever talked publicly about their reasoning for these choices?
As much as I really push for not needing a native solution for apps that can work well on the mobile browser, I've always felt the need to rely on a third party native GitHub client. Couldn't find any that were completely free and had everything that I needed, so I built GitPoint :)
This article was really the only mention I've heard about their mobile website but haven't heard anything about their reasoning either. Definitely curious as well.