undefined | Better HN

0 pointshalapro5mo ago0 comments

The worst part here is that the style works decently on mobile but they shoehorned it onto a 25-year-old UI and shipped it.

0 comments

9 comments · 2 top-level

grishka5mo ago· 7 in thread

Because they absolutely can't have disparate visual styles in their product lines, practicality be damned ¯\_(ツ)_/¯

rwmj5mo ago

At least it's not GNOME, where they shoehorned an unusable mobile-style interface on the whole thing and they don't even have a mobile version.

Y_Y5mo ago

To be fair, there is sorta kinda a mobile version: Phosh.

https://en.wikipedia.org/wiki/Phosh

And amusingly Ubuntu uses Qt for its phone clone of Gnome.

https://en.wikipedia.org/wiki/Ubuntu_Touch

1 more reply

the_other5mo ago

Allegedly the next gen MBPs will have a touch screen. I think Apple have pushed a touch-enabled macOS UI out a year ahead of the hardware: maybe to iron out issues; maybe 'cos they could... I worry that we're stuck with this shit for a few more years, 'til the touch screen goes the way of the touch bar.

grishka5mo ago

These rumors about touchscreen MacBooks have been going around for at least 10 years. At this point I don't believe any of it. Especially with how they sell keyboards for iPads.

Klaster_15mo ago

"Consistency".

yakshaving_jgt5mo ago

Consistency is the absolute fucking worst design principle.

3 more replies

vincnetas5mo ago

yeah, but somehow consistency was not a concern when picking icons for menu items. as pointed out by some previous discussions on this matter.

i also hate this "consistency" idea. was working on mobile app for android/ios. and a requirement was for apps to look identical on both platforms. whyyyyy. sure for designer it looks nice, but as a user who uses either ios OR android im used to conventions of particular platform. why throw that all away just to look identical an both platforms.

hliyan5mo ago

I'm fond of saying that most problems in the software world are due to one thing trying to do two things, or two things trying to do the same thing. In this case, it feels like the former: getting the same implementation to cater to both desktop and mobile is obviously the most efficient solution from a development perspective, but not an end user (and ultimately business) perspective.

j / k navigate · click thread line to collapse