So much effort was poured into just redesigning, repackaging basic apps on the surface. I think some of them look and exhibit functional behavior straightforwardly worse than before:
- Smaller fonts and less obvious icons on the weather app
- Less info on the world clock without the digital time text, which helps grasp the time at a glance especially when you're looking at several zones.
- Smaller direction character font on the compass (why would anyone do that? It's like 40% of what it used to be and is only a single char!)
- Less contrast across the entire interface with all white text; harder to discern differences.
... and at best a neutral change across the others. I haven't yet installed it myself, but the screenshots look disappointing. I am not dismissing the idea of removing skeumorphisms, but this particular implementation/execution seems like a step in the direction of less refined for Apple.
I have seen very few screenshots so far that made me say "oh that's so much better, wow". Several did make me say "Gosh, why would you reduce the font size there?!?! Why would you make the icon much less obvious?"
Just to note that I am not trying to be negative - I am certain with this much solid engineering talent, there will be features we'll love.
I hope I'm proven wrong once the OS is officially out and we're hooked in the following few weeks.
- Weather app: Some fonts are smaller, some are larger, but you get a great looking animation that shows the current weather. In my opinion the app is much prettier than before, and more useful since you can see, for example, whether you need to bring a raincoat immediately.
- About less contrast: You can turn on bolder fonts in the interface.
I really, really like iOS 7. Especially on the iPhone, somehow on iPad I had more of a meh reaction, and I installed it there first. But going back to my iPhone with iOS 6 made me realize how dated that OS looks and feels.
Forgetting the looks, all the little new features and improvements are great, like all the new Safari stuff, command center and the improved app switcher. Apple says there are 200 new features and I definitely believe them.
Design doesn't exist in a vacuum, if you showed iOS6 and iOS7 to someone who had never seen it before, they would surmise age by comparing to other designs they have seen.
In the same way you would see something that you've never seen before and go "that's so 80s".
Considering that Apple didn't originate the flat trend, and that the web has been going flat (or flatter) for a while now, I don't think it would take a genius to figure out which is which.
I'm not sure the web is embracing flat, it's more like designers get bored and feel the urge to do something. They have to justify their paycheck and raison d'etre.
It's like the fashion industry, what is out of fashion comes back in because somebody says so and the catwalk is then flooded with retro fashion.
People use this tired old argument on us too - "what? Why is IT building the website again? Don't we already have one? Welp, guess they have to justify their paychecks somehow...", it's tiresome, reductionist, grossly ignorant, and textbook HN: everyone is useless except me.
Fashion isn't a simple cause and effect - it isn't designers dictating taste to an unwilling public. The influence is circular - design influences public aesthetic influences more design. The fashion industry steals plenty of ideas right off the streets, it's far, far from a one-way relationship. "Fashion" is just an endless cycle of the public influencing products and vice versa. Sometimes it will retread familiar territory, other times it'll do something new.
And thank god we have it. I for one am glad we're rid of animated GIFs and fluorescent green text, or do you think that evolution is also bored designers justifying their paychecks?
But nah, none of the above can be true, everyone's a useless parasite except the vaunted Hackers, hallowed be their names!
For me it's the removal of textures like wood and leather. And the fact that almost all the icons are more futuristic rather than illustrations of real life objects, see Game Center, Photos, Reminders.
I agree, the humanist touches and concordantly superior identifiability in the one OS clearly identify it as the modern iteration compared with the cold, chilly 70s-style pseudo-futurism of the other.
The official weather app actually looks remarkably similar to the current Yahoo! Weather app, and seems to share the same icons.
Before it was 100% obvious what the icons meant at a glance -- a big yellow unmistakable sun, clear full clouds, etc.
The new ones are just outlines, you almost can't tell the white and yellow lines apart, you have to "decipher" them with your eyes to figure out the weather for the next few days. A huge step backwards in clarity.
The Weather app had been powered by Yahoo! previously so they could have partnered with them after the release of their app to do the default app and update it for iOS7.
Worth pointing out that screenshots have not really told the story, ever since iOS 7 was released to developers this spring. There's an overall lightness and fun feeling that's only really apparent in actual usage. Subjective, obviously, but I've been using it for months now, and when I pick up an iOS 6 device it feels ancient.
I'm still a bit agape at what they seem to have done to the in-app back button. I mean, it's always been maybe the worst thing about the iOS UI, a wart thrown into a convenient corner of the screen where it's easy for unsophisticated users to forget about or miss entirely. Obviously, it's just the outer symptom of a real, hard-to-handle problem - the different layers of 'back' or 'escape' in a full-screen mobile OS - but what have they done with it? Is it still a button, or just an indication that you can swipe left-to-right across the screen to go back? If it is still a button, then why in tarnation have they made it (possibly) harder to notice and (certainly) to identify as a button? Maybe the free-standing left arrow makes it harder to miss the 'go back' meaning compared to the cutesy border of the old button, but it looks like one step forward, one back at best.
It has to do with the way UIViewController titles now work. When you tap something that pushes a new view controller onto the stack, the current title animates left and _becomes_ the new back button. The animation is not only pretty, it makes it really obvious where you are going, and how to get back.
Not only that, but by default, swipinging the view controller off to the right I.e. Physically reversing the animation that brought in in, also functions to go back, so the 'button' is more of a signpost of what you will go back to than something that must be used as a button.
The reviews don't mention this because frankly a lot of them are superficial - or they are focused on justifying a number or a thumbs up or down rating that they have assigned, rather than helping people to understand anything.
Safari was in need of an overhaul - Chrome, Atomic, and other browsers were so much better that I pretty much stopped using Safari.
From what I saw in this review, the new Safari offers much more functionality than the prior version, devoting substantially more pixels to content and offering the iCloud Keychain feature.
I do agree though that the functionality hasn't improved significantly for most of the other apps. I'd be way more excited if the Control Center offered customization. My two most frequent settings (Cellular on/off, Location Services on/off) aren't in Control Center so it doesn't really give me much.
I was going to complain about AirDrop being proprietary, but this is very disappointing. What is wrong with Apple?
> It’s important to note that while AirDrop in iOS 7 and AirDrop in OS X share the same name and underlying technology (both work by transmitting files over a peer-to-peer Wi-Fi connection), they aren’t actually compatible with one another. You can AirDrop things from iOS to iOS and from OS X to OS X, but not from iOS to OS X or vice versa. All the reports I can find say that this situation doesn’t change with Mavericks.
I know. I can't ever imagine a time when I wanted to share something with an iPhone next to me (my friends are usually faraway, or if we're hanging out then we're not using our phones).
But several times a day I wish I could beam a photo, a Notes text file, etc., from my iPhone to my Macbook Air. In the end I'm just constantly e-mailing links/photos/etc. to myself, which never ceases to seem ridiculous in 2013.
The problem is that most people want to use clouds services that are flexible and can interface with lots of things besides just Apple stuff. Native apps can interconnect with iCloud via APIs, but what about all the other services we use that are not native apps. Just look at IFTTT for example. No cloud is an island.
The issue is that things work totally differently. AirDrop for the Mac works via multi-association wifi, which takes a decent amount of power. That is less noticeable on a device with a large battery, and Apple designed the UI in such a way that it only turns on when sharing is occurring.
On iOS it still uses multi-association wifi for the actual sharing, but it uses Bluetooth LE for the discovery. That allows it to be active at all times, which is very important given that on iOS most of the time AirDrop will be initiated while the app receiving the drop is completely inactive. The problem is that if Apple were to move Mavericks over to Blue LE discovery it would impact backward compatibility with existing AirDrop to Macs running older OSes, and it would have issues since some Macs that support AirDrop don't have Bluetooth LE compatible hardware. Not to mention you would have a lot more (and more confusing) use cases to deal with in the UI.
I expect them to move Mac OS over to iOS compatible AirDrop eventually, but it is not just a simple oversight. It is going to have to be a transition that has some thought put into it.
On iOS it still uses multi-association wifi for the actual sharing, but it uses Bluetooth LE for the discovery. That allows it to be active at all times, which is very important given that on iOS most of the time AirDrop will be initiated while the app receiving the drop is completely inactive.
Just tested this, and my iPad doesn't show up until I open the "control panel". Still it'll save battery by using only bluetooth for the initial scan.
It's important to ask yourself what you would do if you could AirDrop from your iOS device to an OS X device. Even though under the covers iOS and OS X work on files, iOS is sandboxed where OS X isn't, i.e. if you can't get to it via USB, you couldn't get to it via AirDrop anyway.
With that said, it would be useful to have some of the iTunes/iPhoto functionality for wireless(AirDrop) a la carte file transfer, but most people will just use iTunes wifi sync to get this effect.
> It's important to ask yourself what you would do if you could AirDrop from your iOS device to an OS X device
Quickly send photos I just took to put in email, IMs or on web forums. I used to do that constantly before I had an iPhone using Bluetooth, it was super-handy. Now I have to take a pointless long-cut through the internet with something like Dropbox. Royal pain when you're somewhere with spotty upstream internet.
> Quickly send photos I just took to put in email, IMs or on web forums.
All the photos you just took are available via Photostream on all your other devices, assuming you have WiFi, which presumably you'd need for Dropbox. If you don't like firing up iPhoto or Aperture to see your photo stream on the desktop, there are "apps for that".
If you don't want an app, here's how to put a shortcut to your latest photos right on your dock:
My iCloud account is already at data capacity (with a paid addon at that) with my iPhone and iPad backups. It's also a huge pain waiting for a million photos to sync when I want just this one. I'm also not happy with the privacy aspects of Photostream if I've taken private photos.
I mean, it works. But it's not elegant nor efficient. The Dropbox method sucks too. I often don't have Wifi (or it's hotel/airport wifi where you're limited to 1 device), and then I wish I was back on my dumbphone...
So the shared photo streams are effectively free photo album storage you can keep private or share with friends.
It also doesn't wait for a million photos to sync. It syncs the most recent one(s) you just took. It's hard to imagine more elegant or efficient than "it just happens without you doing anything".
It sounds like you're not very familiar with how Photostream really works. That's not unusual, a lot of my people I know complain about things that it turns out Photostream supports because Apple never really pushed or promoted it.
> I often don't have Wifi (or it's hotel/airport wifi where you're limited to 1 device), and then I wish I was back on my dumbphone...
You're in luck; iOS has a switch to turn off 3G data and become a dumb phone.
If you're in the mood for the dumb phone style manual management instead of an automatic photo stream , there are several really great apps for popping single photos over or sharing the clipboard. I personally use a clipboard app that I can "copy" a photo on the iOS device and on my Mac just "paste" it somewhere. That one works over ad-hoc WiFi so doesn't need a WiFi base. Others work over bluetooth.
I stand corrected on the Photo stream data thing. My experience with it is not that it syncs the recent ones first. My experience is they pop in randomly, then it stalls for half an hour for no reason. Maybe it's gotten better recently.
It's still ridiculous that the answer to "I want to send this thing between these two devices in front of me" is "I have to send every photo I take to a server owned by a company somewhere".
Clearly Apple agrees, or they wouldn't have created AirDrop in the first place!
> I personally use a clipboard app that I can "copy" a photo on the iOS device and on my Mac just "paste" it somewhere. That one works over ad-hoc WiFi so doesn't need a WiFi base. Others work over bluetooth.
He said he wanted to send a photo to his Mac, not all his other devices, Apple and whoever else has acces to Apple's servers. AirDrop would have seemed like the logical solution.
Even though iOS is sandboxed, has no files and no folders, lets not forget
AirDrop on Mac doesn't do folders either. It almost
looks like attachments: you drag (send) a file to the receiver. iOS handles mail attachments fine. I think this is something apple will implement later via software updates. Like for example obvious but long awaited OS X features like iBooks, Maps, Messages and Finder tabs. We're are wondering why they just didn't include it from the start, maybe they need a reason to sell OS X 10.10.
This seems like a possible win for Apple, and I hope they implement it. I just wanted to point out that OSX to iOS AirDrop is not as trivial as many people make it sound. There are edge cases, such as "what if the user doesn't have an app that supports this file?". It's different than email, because the file can't be saved in anyone's sandbox.
Realistically it could be done a la DropBox - i.e., another app (lets call it AirDrop) that receives these files and can launch the App associated with the file. Users could send the file through AirDrop.app by sending that file to AirDrop.
I'm not a fan of iOS 7 design-wise, but my biggest gripe is the battery. It's bad. Really, really bad. I think it's a combination of an actual decrease in battery life and iOS 7's terrible monitoring of it.
It's not uncommon for my phone to shut down after it's hit 8% remaining battery. Or I'll be watching a video with 45% left, and the next second it'll cut me down to 25%. There have been a few instances where I've gone from ~25% to completely empty in a flash, leaving me with a dead phone much earlier than I'd anticipated. So now I really can't leave my place for more than maybe 4/5 hours without my charger.
I've been using iOS7 on my daily driver since the first beta release and never had any problems whatsoever with battery life. In previous betas I've noticed this problem, not this time though, and certainly nothing close to what you were describing
So you're running pre-release iOS, and expect it to work flawlessly?
I made the same mistake with iOS5beta and it was a nightmare. Power usage was the least of my issues. WHen iOS5 finally came out, I noticed most of my issues had disappeared (the rest got resolved by 5.1).
tl;dr: The use of iOS betas for your daily driver are inadvisable.
Yes, and 'kyro' made comments talking about a trend that could have only been experienced during the beta. Having this many data points on battery life in a few hours would be a pretty neat trick, and a much more damning situation.
However, this review has tested it and found a drastic effect on the iPhone 5's battery life running the released version so it's not limited to betas.
I'm curious, how did you determine that the problem is iOS 7, as opposed to your hardware – or, perhaps, the need for your hardware's power management needing to be reset/recalibrated?
I only ask because I recall reading some complaints during the beta cycle that were resolved in some way without changing the specific version of the pre-release they were running.
It was a very clear change for me. I'm usually at work from 7 to 5. On iOS 6, my iPhone 5 had no problem making it through with moderate use. There were no jumps in percentages. I could use the phone for an entire hour with <10% remaining.
Once I downloaded the beta, I found myself with a dead phone at noon, having to fully recharge it at least once just to have a usable phone by the end of the work day. And I think I've only seen it actually hit <5% all of two times. It'll power down way before it gets that low.
I guess what I'm suggesting is that maybe the act of applying the beta to your phone put your power management hardware in a state that necessitates recalibration or reset.
For example:
"The issue with the battery drain on iPhone 4S was big and we saw the battery drain down in hours. However if you clean install first and then restore data, the issue doesn’t seem to occur."
Make sure to disable all the new location related shit. There are a dozen new things in there that will rape your GPS for all it's worth. Also, the second I installed the Starbucks app it re-activated Passbook and the whole GPS system for that to automatically start itself when you walk into a Starbucks. No thanks. Disabled all of it and my battery has been much better.
I was wondering because I've been having battery issues on the 4S using the beta but when I switched to the GM seed I noticed a change. Might have just been my mind playing tricks on me, it's really tough to measure.
Battery life is down across the board compared to iOS 6.
This worries me. If it's because of the background downloading then at least it has a benefit (and is disable-able), but if it's the extra GPU cycles for the UI then that's a real shame.
The Dutch tech site Tweakers.net also found this in their tests [1].
They found that battery life was degraded mostly in standby mode (with iOS7 losing 12% of battery after 16 hours of standby time, compared to 7% on iOS 6.1.4).
With a more active usage pattern, they found the differences were smaller: their iPhone 5 running iOS 7 lasted 16 hours, compared to 17 hours on iOS 6.1.4.
This would suggest the increased consumption is more likely to come from background stuff than from visual UI effects.
Anecdotally, my phone's been ending the day at 30-40% on iOS7 when I usually ended at 10-20% on iOS6. I'm guessing I had a particular app that Apple's now handling differently.
I've had a similar experience with my iPhone 5 as well. It was significantly worse during the beginning of the beta builds, however now it seems to be better than iOS6 (for me).
I'm guessing it's something similar to you – a wonky app draining my battery that is handled better on 7.
I have been using the betas and the GM, and I noticed a decrease of battery life. I have my phone (iPhone 5) tuned to the best battery saving settings, and still the battery drains faster than it did when it was on iOS 6.
I've been using all the betas on a 4S - aside from early-betas, it's been no more demanding on my battery than iOS6 had been. It hasn't been a factor for me.
Might it be be that a constant loop of activity is not a good model for battery performance in actual use ?
I've heard someone suggest that perhaps background sync actually might help battery life in some situations since it is done in batches. this would mean that users are spending less time looking at a power hungry screen that's just showing a loading spinner, assuming that some of this saved time is spent not using the phone at all, there might be a gain.
edit: To expand, although I am unfamiliar with everything that could be/has been done to maximize battery life:
Is it possible that "tweaks" are made in ways that are more relevant to actual usage patterns? (And perhaps ways that sacrifice battery life in the for speed in other areas, in the hopes of maintaining the baseline or improving battery life overall while still improving perceived performance)
What might these kind of changes be?
I'm not trying to be an apologist, genuinely curious about how what sort of optimizations might be made, and trying to make sense of the difference between what Ars is seeing and the anecdotal evidence.
I am not sure if the version they have been using is the GM seed version of IOS7 or not, but I notice in XCode there are still a lot of tracing going on. Even with that, I find the battery life on my iPhone 5 to be quite decent. I would think it will improve once debug stuff is turned off in release version.
This is the 1st review I've seen come to that conclusion and having used it since June I haven't noticed any reduction in battery life. I wouldn't get too worried.
I would totally expect it to be extra GPU cycles. To support all those animations and transitions, they are certain to be executing many more screen redraws.
It happens to most OS updates. Wait 24 hours for things to settle down, then measure again. On Android, some app may go crazy after update, you have to reinstall it to get out of bad state. I have seen it too many times. Not sure how to troubleshoot the same issue on iOS though.
iOS6 also had some battery life issues in the beginning. I'm guessing this will get tuned with subsequent bug fixes, especially as real-world usage data comes in.
I like iOS 7, but I'm a little worried about how app designers will do with the new look.
When you compare the apps currently out that have been updated, you can see a lot of companies are struggling with flat design. Something that seems simple, is actually very complex to pull off, but when done right, can be fantastic.
I think it will be a while before the ecosystem fully recovers and most of the best apps around have figured out how to execute flat design well.
iOS versions have generally had a massively forward adoption rate. I read that 80% of iPhones were on the most modern OS. It looks to me like the lack of support for the 3GS will create a split in adoption of the OS, which will trickle down and create an even larger gap in the purchasing of new iOS devices. I think this split will occur due to the stability of the 3G iPhones.
This is concerning to me due to my company having iOS releases for the enterprise. This means that our customers are purchasing iOS devices just for our app. This also means that we have to be backwards compatible with yet another version of the OS. In code, this is where Macros come in.
I am reminded of the days of Microsoft vs Apple where Microsoft had better backwards compatibility. I think that the use of these devices in the business world will echo the days past and the cheaper device, Android, will be the go to business device.
> "It looks to me like the lack of support for the 3GS will create a split in adoption of the OS"
Sure, but having seen the 3GS usage numbers on my own app (which, granted, is hardly a gold standard of representative demographics), I think this will be a rounding error. Despite Apple selling the devices until relatively recently, there are actually very few out in the wild. A developer can now effectively develop for iPhone 4 as their baseline.
Granted, you might have uniqueness in your demographic that will skew 3GS usage higher than the general population.
> "This also means that we have to be backwards compatible with yet another version of the OS. In code, this is where Macros come in."
Ah, but you can't use macros, since a single binary will have to work on all devices - there aren't multiple binaries built with multiple flags. What you will have is a lot of runtime checks against either the OS version or specific featuresets.
Be prepared to write a whole lot of if ([obj respondsToSelector@selector(...)])
The worst part about this isn't just supporting new features - that part's easy since you can simply test for the presence of necessary bits, mostly with respondsToSelector. The worst part are the undocumented behavior changes in UI components that will break between iOS6 and 7. For example, it looks like there are large implementation changes in UITableView and UITableViewCells. This means you must necessarily test against the version string and branch from that. Annoying at best, code-quality-destroyer at worst.
Why is lack of support for the 3GS any different than iOS 6's lack of support for the 3G? The 3GS came out in _2009_. I'm surprised it supports iOS 6; the 3G can't even run iOS 5.
I can see a lot of effort went into interactions and some screens. Then I'm left with the impression they just winged it on the rest [1].
The redesign of the messages app limited itself to removing the graphics. The app still shows messages as bubbles, it's just bland now. I can think on a couple better design solutions for chat threads by looking at other apps and Adium themes.
The Newsstand is another example of redesign-WTF. It still has bad usability and small thumbnails, it just replaced the background with some random grey background.
Noteworthy are also those icons on the home screen. There's no consistency between them, as pointed by multiple designers already [1][2]. I can't believe Apple is pushing these as final.
Overall, it looks like a rushed job, not something I would expect from Apple. I see no compelling reason to update.
This sounds like update-specific problems. Have you tried rebooting the OS, and if that doesn't resolve, reinstalling (restoring from the backup you should have taken prior to update - you did take a backup, right?)
Yeah, I know: it's the old Windows support mantra (3R): reboot, reformat, reinstall [1]. But it has clearly helped me before in resolving iOS issues.
I... don't like it. So far anyway. I'm trying to keep an open mind since I don't have much of a choice anyway.
I don't like that buttons turned into labels. I don't like that my screens now look more cluttered without clear delineations between UI elements. It looks a bit like a toy now as well. It also feels a bit more sluggish on my 4s.
Looks pretty and useless. I've been using iOS since iPhones came out, I'm seriously thinking about moving to android. Google has a good deal on Nexus 4.
I really dislike rendering active buttons as pure text. Moving away from skeumorphism does not mean removing every visual cue that differentiates active from inactive items. All the more so on mobile devices where "hover" cues are not accessible. Google is also guilty of this.
I like the cleaner UI design and new fontset a lot. However, the background blur is distracting and counterproductive for the overall clean look. Maybe they just tried to much to top / set themselves apart from the Metro UI somehow?
The new alert banner is enormous! It clearly seems to have been designed with the iPhone 5+ in mind. At least the new ringtones and chimes are sort of lovely and not corny like the "Classic" ones.
And now we are starting to see Apple fall behind its competitors on central features, like e.g wi-fi calling. This feature is essential for the phones primary function, calling, in low-coverage areas. All competing mobile OSs already support wi-fi calling so this is disappointing.
I find this funny. IOS 7 is the same as IOS 6 except for a few re-arrangements of features and a new look. I feel like Mugato from Zoolander.. Am I taking crazy pills? Their all the same! Ios 6, 7.. iphone c.. s.. it's really the same thing with tiny changes. And everyone is reviewing them like they are new phones or new OS.
> "I find this funny. IOS 7 is the same as IOS 6 except for a few re-arrangements of features and a new look."
As someone who's spent the last 2 months porting code from iOS6 to iOS7, I disagree. The API changes (documented or otherwise...) are large enough that this really was more of a port than it was a simple update.
It may look like simple rearrangement (I disagree with that assessment, but whatever), but under the hood a great deal has changed.
Interesting, we had very few issues with API changes moving to iOS 7 (mainly dealing with the status bar, especially double-height, which in some places still needs an OS-specific check). All our work has been in getting the iOS 7-style UI looking right and working well. And we have code in our app dating back to iOS 3.
Depends on how stock your UI is. The app I work on is very heavily customized (e.g., lots of subclasses of UIButton, UITableViewCell, etc etc), and iOS7 broke a lot due to underlying implementation changes. We're also pretty graphically intense, so iOS7 also likewise broke a lot of optimizations.
Quick examples:
- The entire way iOS handles text rendering has changed (makes sense, CoreText), so methods that calculate text rendering now return different results than they did before. More crucially, text measurements can now return non-round numbers, so if you're using the results without rounding them off, you will get pixel alignment problems galore. Previous versions of iOS rounded off results before returning them to you (though this is not guaranteed via documentation, or even addressed).
- Text rendering has also changed, so even if you're not using the system fonts, the exact same font will render with subtly different widths and heights. In densely packed UIs this can be problematic.
- UITableViewCell's underlying implementation has changed. More specifically, backgroundView is now by default a plain white view, where it was nil before. If you have table views that are transparent, surprise, they are now all white. There are also some subtle differences that can cause trouble if you've heavily customized UITableView - I suspect personally that UITableView now has a UICollectionView (or UICollectionView-esque) based implementation (it seemed entirely separate before), since some of the behavior now aligns.
Interesting. We do a lot of custom drawing as well (like I said, our app dates back to iOS 3, so we even have a messy custom transition animation layer that wouldn't have been necessary with newer OSes) but it sounds like we've sidestepped some of the issues you've run into just by chance.
For instance, we already had custom text metrics code since our app's font is italic, and that code already rounded to non-retina boundaries. And I think nearly all our tableviews already had custom backgroundViews.
Our biggest incompatibility was a progress HUD popup that subclassed UIAlertView, and that drawing broke completely in iOS 7 (it just turned into a little blurry white bar in the middle of the screen.
- You wouldn't expect Apple to change core apps like Phone dramatically. It's a very mature feature that isn't going anywhere and is practically identical on every smartphone. You get a numpad, you get your contacts list, your voicemail, etc. All of which has been given a new coat of paint, but fundamentally hasn't changed much.
- You see deeper changes in the built-in apps that aren't quite as mature/core. There is for example a large change in UX in iOS to move away from hard, distracting transitions towards more subtle transitions that imply information hierarchy. For example if you tap on a date in a calendar, instead of hard-wiping you to another piece of UI altogether to show you appointments, it dynamically expands the day-view from the date itself. If you tap on an album in Photos it will dynamically expand that album to fill the screen with additional photos. All of this goes towards better educating the user on information hierarchy and is much, much less jarring than before. As a third party dev that's been working with Apple on iOS7 prep, I know for a fact that they're pushing this new UX hard - you will see more 3rd party apps go towards this model in the coming months. You see some uses of this in first-party apps, but users will notice most when 3rd parties start adopting this.
- Many of the most substantial changes are under the hood and aren't being (visibly or ostentatiously) used in the stock apps, mostly because there really isn't a place for them. They will, however, power a new generation of apps in the coming months - things like a new backgrounding model will let apps do more while not in use, and also in some types of apps greatly reduce the loading/refresh time when you return to them. Or even more subtle things like dynamics, which will make scrolling feel very different in apps.
In short, users will feel some of these changes immediately, but ultimately the deep changes in iOS won't be felt until third party dev adoption is there.
They don't know anything about it. But a lot of new APIs were made available to developers that will make great apps easier to make. I think that's better for users than a new OS toy.
iOS 7 changes the backgrounding model, which has been a giant point of contention since the app store was introduced, and also has a brand new facelift. It was also one of the main differentiators aside from data sharing between apps between iOS and android. It is not a trivial update technologically or a small update from a marketing and direction standpoint.
It is also the first major OS update under Ive and Cook's direction.
The phones are a minor update, as to be expected like every S release.
> The phones are a minor update, as to be expected like every S release.
There have been two S releases prior to the 5S/5C release. The 3G->3GS was a bigger change to the phone than the iPhone->3G update. And the 4->4S update was a bigger change to the phone internals than the 3GS->4 update, though the display stayed the same.
Really, all the S releases have been major phone updates, and of the non-S releases only the 4S->5 update was.
I disagree. Having owned all those phones; I felt the 3GS->4 was a much bigger update to the iPhone compared to 3G->3GS. The 4 introduced the retina display which was far more noticeable than the 3G to 3GS performance increase.
poolpool. I get what your saying, but exactly what are you saying? Data sharing between apps between IOS and Android?
Ive and Cook are just riding on concept from Jobs, there is nothing new here. If any other hardware vendor put out phones with this level of "same old" they would be burned for it. In the future people will look back at this Apple craze and laugh. Apple put out the iphone 5, with a new case and blogs are reviewing it! Are you kidding me? IOS 7 is the same damn OS as 6! Airdrop is nothing new feature wise. Almost every other feature has been out on other OSes for a long time. Apple struck gold in 2007.. and they been re-regurgitating since. Scared to wipe the slate because there will never be another Steve and they will never hit another winner like the initial iphone. But it's tired now. IOS 7 was supposed to be something different, and bottom line it's the same OS that consumes more battery and more resources. Whatever additional battery life they added to the iphone 5s hardware is cancelled out by the new requirements.
"Let's see where Microsoft is vs where Apple is in 3 years. Apple has 0 innovation going on. OS X and IOS are stale as anything. They are riding on earlier success and eventually will fizzle out."
That's not really fair. Some would say some fanboys think no matter what other companies do it is right away awful. MS did try the flat look.. looks like at least that caught on a little.
I don't know who you mean by "we", but generally users expect something new with a new OS, new hardware, or basically anything with the word "new" in front of it. Apple didn't announce IOS 7 by calling it the next IOS, they called it the new IOS.
iPhones have existed for more than six years with largely the same UI style. While it may be mostly a reskin, iOS 7 is a dramatic departure from the circa-2007 style.
Ars is known to every major release of iOS and OS X in this fashion, just as Anandtech reviews the new hardware in great detail.
- Smaller fonts and less obvious icons on the weather app
- Less info on the world clock without the digital time text, which helps grasp the time at a glance especially when you're looking at several zones.
- Smaller direction character font on the compass (why would anyone do that? It's like 40% of what it used to be and is only a single char!)
- Less contrast across the entire interface with all white text; harder to discern differences.
... and at best a neutral change across the others. I haven't yet installed it myself, but the screenshots look disappointing. I am not dismissing the idea of removing skeumorphisms, but this particular implementation/execution seems like a step in the direction of less refined for Apple.
I have seen very few screenshots so far that made me say "oh that's so much better, wow". Several did make me say "Gosh, why would you reduce the font size there?!?! Why would you make the icon much less obvious?"
Just to note that I am not trying to be negative - I am certain with this much solid engineering talent, there will be features we'll love.
I hope I'm proven wrong once the OS is officially out and we're hooked in the following few weeks.