Live data from Hacker News

iOS 7

mattgemmell.com

281–284 of 284 posts

Re: iOS 7

#281
post #238
post #234

Earlier quoted context omitted.

I hate posts like this that lay out some first-order criticism of a design as if the designers did not consider their obvious concerns. It also sounds like you are making judgements based upon screenshots without actually using the software. As far as messages go, it seems that the contrast is appropriate for the bubble at the bottom of the screen. The presumption, I think, is that users will scroll to read previous…

That kind of thinking adds very few to the discussion. I respect Apple and I know they are a reference in terms of UI/UX. This does not mean however that they are immune to making mistakes. Your argument is, from what I understood, that as they are very good they must have thought of it and if they choose to do it anyway then it must be the best way. I do not agree. Even for the message at the bottom of the screen th…

I posted it above but just to re-iterate if iOS 7 ships where background images render the status bar, text, etc, unreadable due to an obvious "white on white" or "black on black" issue, or at least if this isn't somehow addressed otherwise, then I will (figurtively :)) eat my hat.

I'd argue most of my beef with the armchair commentators is they are making what appear to be deep criticisms of iOS 7 without having actually used it, and without taking into account the fact that it's beta 1. They are shipping a new "letterpress" text treatment in UIKit, my guess is that they will apply this treatment to text if it is sitting on top of a similar-colored background, but probably have not worked out the details yet. I could see it being a reasonable technical and design challenge since you may need to apply a treatment to only part of a glyph. I'd ask the poster what their "duh, so obvious" solution is to their "duh, so obvious" observation. (Note: "leave the status bar alone" is not a valid answer here, since the design goal is to have the content in iOS 7 take up the entire screen. If you have a problem with that decision, argue that point, but realize it has nothing to do with status bars anymore. Even if Apple left this pretty glaring flaw in their design, they may have decided to do so because having content take up the entire screen is worth this cost, and the onus is on the critic to explain why it is not worth it, not that they are too stupid to have noticed this edge case.)

Basically if you see something and it's something that 99% of developers would identify as a potential edge case, you can be sure Apple considered it too and at least made an explicit design decision to deal with it or punt for later betas. If they made an explicit design decision, which is assumed, then you should try to understand that decision and then critique that decision and its tradeoffs beyond Comic-Book-Guy-esque "this is so obvious they are so dumb how could they miss my clever edge case I've discovered." Let's say Apple really do see that white on white is an issue, and actually decided to leave it that way and ignore the case altogether. Why would they do this? At least address this question if you are going to critique the design. The OP assumes it was an oversight, not a design decision or technical debt, which is kind of insulting to Apple designers and engineers.

I would prefer if before starting a complaint about text legibility, colors, contrast, and so on, if people would include a disclaimer of if they have actually based their opinions upon viewing the design on an actual device.

Re: iOS 7

#282

Earlier quoted context omitted.

I don't think that's what Gemmell has been saying at all. He has been dismissive of the Windows 8 "No Compromises" approach, but Metro, as found on Windows Phone and the Surface (not Surface Pro), he has always seemed rather positive to me. Some examples: "It’s not quite minimalist, though; it’s more like finding yourself living inside an infographic. The presentation is flat and high-contrast, but there’s little tha…

These are the positive examples?! I'll highlight a few snippets from your quotes and tell me what's positive about them. ... living inside an infographic. but .. little that's familiar [OT: iOS (and its imitator, Android) -- snide for the sake of it] WP leaps to the other extreme, ... different .. for the sake of it.

Yes, but you see that's why I gave you the link, so you could read the words in context and not have to take my word for it that they were intended as positive. If you do read the linked articles, you would see for example that "little that's familiar" is considered a positive, a foil to the over the top skeumorphism of its competitors.

Re: iOS 7

#283
post #280

Earlier quoted context omitted.

> The presumption, I think, is that users will scroll to read previous messages and the contrast will be fine where they are reading. That's a wrong-headed and frankly stupid presumption on Apple's part, if true. You're arguing to make the top half of the messages screen unreadable (or at least more difficult to read) in the name of a gimmicky gradient effect? > If you really think Apple hasn't considered the idea th…

My issue is the OP fails to realize design is about tradeoffs, and points out where the new design sucks and where the old design is better, but shows his hand by not considering why the new design may be better. ("arguably looking better", what does this mean? Why does it look better? Perhaps there is a functional purpose to it that he/she is overlooking?) The new message UI is obviously trying to fade out the older…

Just regarding the message UI...

First off, I don't think they are explicitly trying to fade out older messages. The received message bubbles are gray and don't seem to have a gradient effect going on; it's only the sent ones which are colored (green or blue) and have the gradient. So I think Apple's goal here really was just a gimmicky gradient effect for the colored (sent) messages.

More evidence for that is that the bubbles themselves don't seem to change colors as you scroll; rather they are just sort of a mask for an underlying gradient layer underneath (so you can have one large bubble which fills the screen and is light on top and dark on the bottom).

But even if their intention was to make older messages fade out, it was still severely misguided. It is trivial to discern which messages are older (they are higher in the chain and therefore further from the text input for a new message). Users of iOS have been familiar with this for years (and isn't the new UI supposed to move away from explicit visual cues since the assumption is people are used to it by now?).

Moreover, it actually hurts usability, since users now have to scroll more often to get messages in the readable portion of the screen if they want to read through a conversation.

And, on top of all that, if there is only one sent message in the conversation, there is actually no way to bring it into the readable portion of the screen due to the snap-back! (Further evidence that this was intended to be no more than a visual gimmick.)

Re: iOS 7

#284
post #275

Earlier quoted context omitted.

So no then. In fact you don't actually know what you are talking about at all. Whilst you are more than entitled to your opinions on any given subject, saying something like "Apply[sic] (or Ive) simply does not understand graphic design anymore." isn't at all constructive. It's worse than that actually. Casting an aspersion like that is entirely vapid, and no amount of snide logical twists are going to change that.

It wasn't meant to be constructive. It was meant to be an opinion.

And like assholes, everybody's got one...
Post reply on HN