Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

For me it is a bad and unnecessary rework. Exactly the kind where they break a functional design that was refined for multiple years. And they break it just for a product management/ marketing reason to have 'something new'.

Both on desktop and mobile there are a lot of useful info lost and at the same time, low density and a lot of empty space. But in addition there is no coherence.

For me, the mobile experience is illustrative. Look at the screenshot examples there: https://twitter.com/greatgib42/status/1275703359283122183?s=...

If you had no knowledge, you could think that after was in fact before.

Issues that I can see:

- No part of the readme/description visible anymore.

- Stupidly lost space, like nothing anymore in the top bar to use additional line.

- stars count was smart before by being on the button itself. Now one big empty button and a separate counter.

- for commit, issues, project... Everything was directly visible before. Now, a horizontal scroll is needed. I hate having to horizontally scroll on mobile web. (But maybe it is just me)



For a fun test, I showed my GF the 2 screenshots. I tried to avoid involuntary giving any clue, and asked her which one, she was thinking was the old interface and the new one. She is not a geek, not in tech, and does not know Github.

But, you can bet it, her guess was that the NEW interface was the oldest one, and that the OLD one was the recent rework...

That is an interesting test to rule out the fact that we are "adverse" to changes.


I'm not sure why that rules out the idea that people are averse to design changes. For one thing, it's just one piece of anecdata. For another, just because someone thinks Design A looks newer doesn't mean that they wouldn't prefer to keep using Design B if they were already used to it. Anyway, even if we accept that people are generally averse to changes, that doesn't imply that all criticism of a redesign should be dismissed as aversion to change.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: