News: 1593076510

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

GitHub redesign goes mobile-friendly – to chagrin of devs who shockingly do a lot of work on proper computers

(2020/06/25)


GitHub has redesigned its web repository layout for an "improved mobile web experience", but developers were quick to find flaws in the new approach.

GitHub [1]said that its new design has three key features. First, a responsive layout to improve usability on mobile web browsers. Second, a repository sidebar for surfacing "more content". Third, the ability to show and hide releases, packages and environments in the repository sidebar.

The team promises that this will be the foundation for future improvements to accessibility along with a dark mode option.

Much usage of GitHub does not require visiting the site. Integration with IDEs and code editors is strong, or you can use the GitHub Desktop application, or direct Git commands. Many important open-source repositories have a bare-bones web UI, like [2]this one for LibreOffice. Performance is good and developers have all they need for managing code.

Sites like GitHub and rival GitLab, however, have ambitions beyond hosting code. They are constantly adding DevOps features, like GitHub's [3]Workflow Templates , designed to make it easy to get started with Actions, GitHub's mechanism for automating code build and deployment. There is also the matter of collaboration with team members who are not developers, but may need to engage with issues and discussions that are part of a project.

[4]

The new GitHub design on an iPhone

The new design does look better on an iPhone, but developers with big screens are not so impressed. "The single worst change is that you can't see the latest commit status from the repo screen. Instead, you get the commit hash, and have to click a tiny ellipsis button to get the commit message and the status indicator," said [5]one developer on Hacker News, winning a response from GitHub CEO Nat Friedman, who said: "This is something we should definitely fix."

There is also a suspicion that GitHub is going for prettiness over information density, though Friedman said: "I don't think there is a principle of lowering information density at work here. I think it's just a design that we will keep iterating. We are pro information density at GitHub."

Too much white space is a common complaint. "Large patches of white really hurt to look at for any real amount of time," said another developer, though Friedman confirmed that dark mode is on the way. Another issue is the width of the layout. "They place content at extreme ends of the screen, completely stretched out like a rubber band," said one.

Some feel that the redesign was rushed without any real consultation. It was an optional preview for a short time, but "you just rolled it out for a couple of weeks basically to see if there were any showstopper bugs before you went live," [6]complained a user. Another challenged, "In what ways do you consider the new design to be better?"

It is not all negative, though. "It's a positive improvement. Better information layout, and the code is still front and center," [7]said another commenter.

The introduction of the new design highlights an oddity about the [8]Microsoft-owned source code management and developer collaboration service, which is that its own development is more top-down than collaborative. "Where do I post feature requests for GitHub?" [9]asked a user in November 2018. GitHub then introduced a [10]feedback form , where requests go into the black hole of "We read and evaluate all feedback carefully, but we may not be able to respond to every submission."

Microsoft at least has its UserVoice forums where users can both submit feedback and vote on feedback from others – like [11]this one for Office 365 or [12]this for Azure.

Strange to say, but GitHub could do with a little more collaboration. ®

Sponsored: [13]Security Features of Connect for Anthos



[1] https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/

[2] https://cgit.freedesktop.org/libreoffice/core/

[3] https://github.blog/2020-06-22-promote-consistency-across-your-organization-with-workflow-templates/

[4] https://regmedia.co.uk/2020/06/24/iphone.jpg

[5] https://news.ycombinator.com/item?id=23620401

[6] https://news.ycombinator.com/item?id=23622372

[7] https://news.ycombinator.com/item?id=23617780

[8] https://www.theregister.com/2018/06/04/microsoft_buys_github/

[9] https://github.community/t/where-do-i-post-feature-requests-for-github/1501

[10] https://support.github.com/contact/feedback

[11] https://office365.uservoice.com/

[12] https://docs.microsoft.com/en-us/archive/blogs/o365guy/submit-product-feedback-or-feature-requests-to-microsofts-virtual-suggestion-boxes

[13] https://go.theregister.com/tl/1956/-8474/security-features-of-connect-for-anthos?td=wptl1956

Why do PC users have to be subject to an "improved mobile web experience" ?

Pascal Monett

You want to improve the mobile web experience ? Great idea, as long as you do it for people using a phone.

I do believe it is possible to make the distinction between a phone user and a PC user, and orient the browser to the proper site. Given that the guys coding the UI are very likely not doing so on their phones, I would have thought that they would see an interest in keeping those things separate.

Re: I do believe it is possible to make the distinction between a phone user and a PC user,

Anonymous Coward

The prior website did detect mobiles from their user agent string. It wasn't great if, for example, you turned your phone horizontal the single column would get stretched in an ugly way. The redesign is in fact responsive and in that regard, an improvement. The responsive ideals are let down by having a fixed maximum width so you do not benefit from a large monitor.

Qui bono?

Mike 137

"I think it's just a design that we will keep iterating."

I have two questions:

[1] you "think" you'll keep iterating - are you not sure?

[2] Why keep iterating? Most developers want familiar non-intrusive tools so they can get on with concentrating on their development, not constantly running up a learning curve for the tools.

To me, this sounds like nonsense akin to the infamous "ribbon".

Re: Qui bono?

wolfetone

" Most developers want familiar non-intrusive tools so they can get on with concentrating on their development, not constantly running up a learning curve for the tools. "

I find it odd that those developers then develop interfaces and software that keep moving the goal posts in terms of usability for Joe Bloggs and his dog.

Releases?

autisticatheist

If all your releases on a repo are marked as pre-releases, there is no Releases link!

You have to add "/releases" to the repo URL manually.

Massive fuckup. Please revert.

Re: Releases?

Def

Do you work for Google by any chance?

I'll tell you what you want...

Anonymous Custard

Some feel that the redesign was rushed without any real consultation.

And therein lies the rub. Once again looks like they're just trying to be "trendy" and catering for an audience that basically doesn't exist (those who code and suchlike on a phone or similar sized screen). Was nothing learned from the whole Windows 8 debacle?

We know what we want, and it doesn't line up so well with what you somehow think we want. Ask us and we'll tell you - not the other way about.

Anyone would think they were Microsoft! Oh, wait a moment...

Re: I'll tell you what you want...

Steve Davies 3

It would be interesting to know what percentage of GitHub users actually code from a phone or tablet.

Could it be that MS in their infinite wisdom (or at the behest of from Marketing MBA) are solving a problem that really does not exist?

It wouldn't be the first time that MS has done this. It is almost as it the words 'if it ain't broke don't fix it' are not allowed inside Planet Redmond.

It is the wisdom of crocodiles, that shed tears when they would devour.
-- Francis Bacon