8 ms·
Human Interface Guidelines
- yvsong 9y agoWhat's the major diff?
- jgh 9y agoThe scrolling in the guide is terrible. Can that not be a guideline?
- eridius 9y agoScrolling looks fine to me (using Safari).
- hhsnopek 9y agoThis says it all to me, Apple tends to themselves rather than the group. One thing that should be concerning for the majority. I was hoping for Apple to switch it up this year with start of their new backend for Safari, rather I don't expect it to turn out as I have wished.
- coherentpony 9y ago> This says it all to me, Apple tends to themselves rather than the group. One thing that should be concerning for the majority. > > I was hoping for Apple to switch it up this year with start of their new backend for Safari, rather I don't expect it to turn out as I have wished. Works fine in Chrome.
- 1123581321 9y agoI use an Android phone and scrolling seems normal in every browser I have installed. What are you seeing?
- coldtea 9y ago>This says it all to me, Apple tends to themselves rather than the group. One thing that should be concerning for the majority. What's "the group"? This is a guideline page aimed at OS X/iOS targeting developers, not the general public. Besides, the scrolling works fine in Chrome (where I read it) on OS X. Maybe you're jumping to conclusions much if this (which others don't even see) "tells it all" to you?
- flukus 9y agoThere are 4 different elements that scroll independently using a single scrollbar: https://developer.apple.com/macos/human-interface-guidelines/overview/themes/ https://developer.apple.com/macos/human-interface-guidelines...
- wruza 9y agoI only see main content (1) and sidebar (2) that tries to retain current section details on screen. Opera. Where are 3 and 4?
- flukus 9y agoThe "Developer" heading and the "Human Interface Guidelines" heading. The first disappears, the second scrolls and then becomes fixed.
- draw_down 9y agoHmm?
- mirimir 9y agoThat is very cool! (In Firefox on Debian.)
- madeofpalk 9y agoHeh. Ironically they're not using their (non-standard) display: -webkit-sticky; for the sticky sidebar.
- ovao 9y agoIs that a problem?
- flukus 9y agoIf you consider UI elements moving around dynamically to be a problem, which I'm guessing these guidelines do. Also if you consider scrolling like an epileptic having a fit to be a problem.
- mlindner 9y agoScrolling is fine for me. Chrome on a Mac.
- vortico 9y agoI'm getting 401 Authorization Required
- kps 9y agoI'm getting a certificate error.
- HNSucksAss 9y agoApple has no credibility to offer UI guidelines at this point. This is a company that increasingly relies on Easter eggs and peek-a-poo UI instead of legitimate design. Their applications are rife with invisible controls that only appear if you accidentally roll over them; what are we supposed to do, sweep the cursor over every pixel on the screen, looking for hidden goodies? One of the worst Apple UI affronts is the secret, alternate menus that appear if you press modifier keys while a drop-down menu is open. So every menu is potentially... trying to remember my statistics here, 2^3 + 1 menus? Then there's "force touch," another shitty, lazy gimmick. So now you're supposed to press and hold and then press HARDER on every on-screen widget... once again to see if there are hidden goodies. And need we even address the embarrassing "touch strip" on the new laptops? The lack of a real Delete key on EVERY Apple laptop? The lack of a headphone jack on Apple's best-selling MUSIC PLAYERS, in an era when Apple's future profits will (by Tim Cook's own admission) be increasingly based on the consumption of services like Apple Music? Nobody should be taking user-experience advice from these inbred hypocrites.
- lacampbell 9y agoTagentially related: why is it web apps in iphone safari are still less responsive when run in fullscreen mode? It's very noticeable.
- bla2 9y agoThe first thing in the macOS guide covers how apps should behave in fullscreen mode. Most people I know only use fullscreen mode accidentally; family has had problems figuring out how to get out of fullscreen mode after accidentally entering it.
- philwelch 9y agoYou know, you just can't win sometimes. Before Mac OS X introduced full-screen mode, people complained that the "maximize button" didn't seem to work correctly. If you actually follow that link, the first part of how apps should behave in full screen mode is: --- Enable full-screen windows only when it makes sense. Full-screen mode is useful when a user wants to be immersed in a task. Not all apps require this level of immersion, however. For example, some utility apps like Calculator work better with smaller windows that reside onscreen alongside other apps. When porting an iOS app to macOS, don’t assume the app should support full-screen mode in macOS.
- PhasmaFelis 9y agoOS X's fullscreen mode baffles me. A few versions ago it switch from just, y'know, fullscreening the app, to forcing fullscreened apps onto a completely different, dedicated desktop for no discernable reason, breaking Cmd-Tab and making it impossible to float another window over the fullscreened one (e.g. if I want to take notes on its content, but without extraneous GUI chrome). Does anyone know what use case the forced desktop switch is supposed to improve? (And the maximize button still doesn't work correctly, because maximize is not the same thing as fullscreen.)
- chrisoverzero 9y agoThe fullscreen button works correctly, because fullscreen is not the same thing as maximize.
- PhasmaFelis 9y agoI'm not sure what your point is. Forcing a window to a dedicated desktop is neither fullscreen nor maximize.
- ProfessorLayton 9y agoI haven't played with the latest beta, but I'd like to talk about this particular guideline that has been irking me more and more with recent iOS iterations: https://developer.apple.com/ios/human-interface-guidelines/interaction/feedback/ https://developer.apple.com/ios/human-interface-guidelines/i... iOS: - Randomly asks me to verify my iCloud password without me initiating anything. It is neither subtle or informs me why it is asking. - 3D Touch is still inconsistently implemented with varying degrees of feedback. A quick example is that you can "peek" into a music album, but not a photo album. 3D Touch in MacOS uses haptic feedback for a hard press irrespective of an underlying action, but not iOS. Apple Music: - No feedback whatsoever when music pauses for various reasons like low signal, bluetooth disconnect, or general playback error. - With a low cell signal, many times it will just outright refuse to play a song already in my library. How do I know this? If I activate airplane mode, it will play music without a problem. No feedback, just a poor experience. Sometimes I really wish Apple would heed their own advice. I'm hoping this is fixed in iOS 11
- astrange 9y agoPlease file a bug whenever you see this. If you're using betas there's an app called Feedback Assistant to do this, otherwise it can be a lot of work to actually get the sysdiagnose logs.
- memco 9y agoTried to file a bug through the online bug reporter for a few things recently only to be unable to submit. The thing just sits there with a loading indicator indefinitely and the bugs just sit in draft mode.
- miles_matthias 9y agoAll great points. For me, connecting to wifi networks has been a huge pain with iOS 10. In settings, I'll see a checkmark next to the wifi network name, but no wifi signal icon in the status bar or connectivity. Stays like that for 2-3 minutes before actually connecting.
- Waterluvian 9y ago
- surajx 9y agoAnd I thought it was some neural pathway...
- macco 9y agoLove the marketing guide, that seems more like a legal document than a marketing guide. Don't do this, don't do that.