Interesting that they decided not to do a responsive design. Instead, it serves up different HTML if you send a phone user-agent. I've been trying to decide if this is a good idea for my own project.
GitHub's on your phone
11–20 of 86 posts
Re: GitHub's on your phone
#12Displaying code on a narrow window is difficult, but I'm not convinced that this is the right solution. I'd prefer to be able to zoom out.
Re: GitHub's on your phone
#13Interesting that they decided not to do a responsive design. Instead, it serves up different HTML if you send a phone user-agent. I've been trying to decide if this is a good idea for my own project.
Responsive feels great with huge/big/medium displays. With tiny ones I would go with a specific layout (like github did).
Re: GitHub's on your phone
#14Interesting that they decided not to do a responsive design. Instead, it serves up different HTML if you send a phone user-agent. I've been trying to decide if this is a good idea for my own project.
I'm not that experience with responsive design, but recently I wondered that myself and, for what I saw, I concluded that is too much effort to make it responsive in that level. Responsive feels great with huge/big/medium displays. With tiny ones I would go with a specific layout (like github did).
Re: GitHub's on your phone
#15Re: GitHub's on your phone
#16Re: GitHub's on your phone
#17Interesting that they decided not to do a responsive design. Instead, it serves up different HTML if you send a phone user-agent. I've been trying to decide if this is a good idea for my own project.
For us, it made sense. Our desktop site is pretty large. Check the graph in the blog post- the mobile pages are about 1/10th the size of the desktop CSS and JavaScript. By avoiding a responsive design, we can make things load disproportionately faster for our use case. On top of that, it's isolated so we're less likely to break views by adding features later. Pretty fun.
Re: GitHub's on your phone
#18Re: GitHub's on your phone
#19Re: GitHub's on your phone
#20Earlier quoted context omitted.
For us, it made sense. Our desktop site is pretty large. Check the graph in the blog post- the mobile pages are about 1/10th the size of the desktop CSS and JavaScript. By avoiding a responsive design, we can make things load disproportionately faster for our use case. On top of that, it's isolated so we're less likely to break views by adding features later. Pretty fun.
Zach, what was the reasoning behind using such large text for the code view? Will there be a zoom in/out option? Or a text size preference?
We tend to avoid user preferences. If it ends up being a problem, we'll lower the text size at some point.