Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The problem with iOS 7 and iOS 8: bad design
- Thread starter El Tuga
- Start date
- Sort by reaction score
Hah! Have you looked at the icons on any android phone? Different shapes, sizes, design cues. Yeah, Apple should copy that....right.
I wonder how many on this thread believe in ANY form of evolution, not sticking to archaic things of the past.
As posted before:
Basically current iO7 as we know it only came out because Jony wanted to make a statement after managing to have Forstall fired. So instead of maturing some thoughts about a new design, he simply removed the patterns and colours from the navigation bars and toolbars, the borders from the buttons, all background patterns and that’s pretty much it. Everything is white with lots of text (some of it content text, some of it labels, and some of it "buttons"). And now he could say he designed Apple's latest iOS.
So he rushed out iOS 7...what he didn’t realize or care is that several basic design guidelines (that were so well implemented since iOS was launched) were broken. 1. Buttons should not look similar to text or labels (they should invite touch), especially in a touch device as there is no precision device like a mouse. Moreover, you should not have to chose the colour of a button based on its function, which of course hampers creativity and app aesthetics 2. Content should not be confused with tools/commands, which is how it resulted from having the content/backgrounds the same colour as toolbards/navbars 3. The newsstand icon, is it a bad joke? 4. most of the other icons and colors looks silly, etc, etc, etc...
The only nice design feature in iOS 7/8 is the translucency. But now we now why it was not added before: because it's slooooooowwww.
So, they got rid of the people who made iOS the best thing that ever happened to apple (it should be enough to say that the iPhone represents 80% of apple's revenue) just to get them out of the way...again Steve would have never allowed any of that crap. He would always put the quality of the product first.
Last edited:
People are still crying over icons and design?
----------
Simple solution get an android phone or jailbreak and stop whining.
We just hope that Apple gets back on track...because Android is EVEN worse than iOS 7/8.
Did you forget that Forstall refused to apologize for the disaster that was Apple Maps? And before anyone says it wasn't so bad, remember that the CEO had to publicly apologize for Apple Maps! Instead of blaming Ives for pushing Forstall out, put the majority of the blame on Forstall.
Since you want to bring up Jobs, he would have killed Forstall for embarrassing Apple. That or told us how we are mapping it wrong.
I like iOS 7/8 and really don't care why it happened as to motives and politics. It's a phone o/s not my life support system and it does what i need it to do. All companies evolve and change.
I don't have any trouble understanding what to press and where to press.
ios 6 was definitely more intuitive for me. I find the lack of buttons because of the flat design a problem, the ios 7/8 icons are very faint for my eyes, Accessibility features like button shapes, reduce transparency helps a little.
I also don't like the animations in ios 7 , here's an interesting video wrt the animations/transitions ( https://www.youtube.com/watch?v=5Ti0KdXrgSE ) it shows how ios 3 was more responsive.
I also don't like the animations in ios 7 , here's an interesting video wrt the animations/transitions ( https://www.youtube.com/watch?v=5Ti0KdXrgSE ) it shows how ios 3 was more responsive.
The whole maps thing seemed like an excuse to get Forstall out of the way. It was obvious that the problem was not the quality of the software, which was ok (vector graphics for the first time looked great, as did the fly-by feature). The problem was the quality of data collection, in most part sub contracted to other companies, and anyway obviously not the responsibility of Forstall. That is why Forstall refused to take the blame for maps, and very rightfully so.
In fact the way Apple dealt with that issue, in my opinion sucked. Data collection for a worldwide mapping service is such a huge task, it is only natural that it takes some time to get it right. It took google years and years.
The real joke there was the lame Cook letter, that only gave ammunition for the competition and the bad press thirsty for blood.
If you want to blame the guy for anything, blame him for having created the amazing iOS that supported Apple's unbelievable growth (iPhone represents 80% of Apple's current revenue).
Last edited:
One of the issues you bring up is touch buttons, but this can be easily added in the accessibility menu. There is an option for 'button shapes' that go around the blue text.
----------
That's a consequence of being in charge, you're responsible.
Not his responsibility? IIRC, he was the head of iOS development. Quality lands at his desk and anyone using the app would have known months in advance that it was not ready and would prove to be an embarrassment. And it was. So much so that the CEO had to issue a public apology. You can try to twist that any way you want, but the fact is Apple had to publicly apologize for Maps.
As for the fly by feature looking "great", I'm going to call baloney again. I used it when Maps was still in beta and it only marginally improved when released. Yes, it's worlds better now, but we aren't talking about now. Furthermore, Apple still hasn't produced and probably won't produce an alternative to Google Streetview. Lets see, what's more usable when driving, a helicopter view of a building or the actual street view.
Apple Maps was bad when released. You can try to spin that any way you want. It needed at least another year before becoming decent. Apple made a mistake releasing it so early and you can't blame Ive for that.
Button shapes for accessibility purposes is quite a ways off from what actual buttons are.
Not sure what the difference is. They are both buttons with an action attached, just one has a shape and one doesn't.
In one case it's a thought through design that fits in and adds to the UI, and in the other case it's a rushed job just to add something that resembles a shape and really doesn't complement or fit in with the UI and was added last minute just to address basic accessibility because they essentially completely overlooked it with the oversimplified new design. There's certainly a difference.
This !
The button design pre iOS 7 looked like well, buttons. In iOS 7/8 it just resembles a shape.
The iphone 6 was apples biggest launch ever IOS 8. I'm in fact blaming Timmy for that. How dare he provide a phone and operating system that people want? Sheesh. What is apple coming to?
----------
That video reminds me of people who start their car in below zero weather and as they are cranking the vehicle already moving the tranny into drive.
Seriously I didn't see the video poster try to load nin.com into safari. That really would have been a test if IOS 3 was more responsive.
The thing is, it's not so much about being more responsive or performing better, it's likely more of just a different design--the current design (as of iOS 7) simply doesn't allow for interactions to register until whatever animations/actions that are coded are completed. I don't think it's some limitation as much as it is a design decision, whatever the reason might be behind it, and whether or not a lot of people might not agree with it.
I just don't understand this change. I miss the old "real" buttons. Maybe this didn't fit in with Apple's resolution scaling (whatever the iPhone 6 Plus is not very good at)?
----------
I know exactly how you feel. Would it shock you that early iOS 8 betas actually improved the app switching? App switching is much more enjoyable when you don't have to wait for the app to stop moving to select what you want. It made switching apps much less of a chore. Unfortunately, this improvement was removed.
I could care about responsiveness, I want speed. It's like inventing a metric how many seconds it takes to start a car and then base how good a car is on that metric.
----------
Car analogies...well, what if after turning the steering wheel a little to the left as you drive to adjust for what the road is like whatever you did with the steering wheel for the next second wouldn't register and only after that would it start registering what you do next. So if you had to move a little left and then back straight or a bit to the right, who in their right mind would think its OK that the car simply wouldn't do anything as they turn the steering wheel back to the right until a second later when it would start responding. No one would buy a car like that. You can bet that responsiveness is important and pretty high up there, even above speed.
The animation when you unlock the phone doesn't bother me so much because the phone is doing something, perhaps that is a design decision , maybe they didn't want the animation broken.
What I dislike more is when you go into settings and swipe up and it doesn't respond, so this is a lost action and you have to do it again, there are no animations going on there.
From the video it seems iOS 3 either remembers the action or is ready sooner.