Should I download iOS6 for my iPhone4?
glipho.com
glipho.com
And B, upgrade a non-essential machine first. The only thing you gain by upgrading willy-nilly is Internet e-peen points, and after a while you realize those aren't worth losing a day or week or month or year's worth of work (hello rsync -E) to being the first mouse. Yes, this isn't as exciting. As for me, I like my systems very very boring.
> Developers will move over their apps. Any major bugs will be found and shook out.
Wasn't this why the iOS6 beta versions were released months before the final release? Now that iOS6 is officially released, Apple is encouraging all users to update and there are quite many average Joes and Janes who don't read the tech press and these warnings. These users are the ones that face the most confusion if something is missing or changed (YouTube, Maps).
Since I installed the update as soon it was available, I don't have first-hand experience of when users are prompted to update. Based on previous experience and some update guides[1], the prompt will appear automatically when connecting to iTunes.
[1] http://ipad.about.com/od/iPad_Guide/ss/How-To-Upgrade-To-iOS...
Bits of the system feel faster, but I can say that Music got a massive speed improvement. I have a playlist of over 5k songs that I like to listen to shuffled. On iOS 5.1, opening that playlist for the first time would take two or three seconds and hitting the "Shuffle all" button at the top of the list to start playing would take take another few seconds.
In iOS 6, they're both extremely fast. Combine that with the ability to use iCloud tabs and I'm quite happy.
Based on what? The problem in the first place is that this is an insanely hard problem that is in the centre of Google's core competencies (data gathering, search, data munching; all on a ridiculously massive scale). Apple makes hardware and an operating system and some apps for it. Where in that set of core competencies does it indicate they have what it takes to tackle this and yield the quality google has (who have poured a rather large fortune into it (they bought the satellites for google maps so they could reshoot to avoid clouds), the have paid for high tech trucks to run down every road in an increasingly large collection of cities. And then massive human QA teams)
This isn't what apple does and it was massive hubris on their part to think they could tackle this and come anywhere near the level of google maps, or their usual standard of excellence. I remain extremely dubious that there is any "quick" fix to their problem. It's not like the screwed up an algorithm and this is a bug, this is a massive problem that they've barely started to tackle.
If Apple does realize what it's going to take to compete at this and doubles down on it, it's still going to take a year or two for them to catch up. And that's an if. So Apple Maps/iOS5 combo is a write off. Probably iOS6 too. You want good mapping the next few years, stick with google. Maybe after that Apple will have something worth looking at, just as likely maybe not.
2) During the beta phase maps improved rapidly. It was not usable a few months ago. Now it is.
So it's not all bad and there already has been massive progress. I think in one year no one will care about this issue anymore. Google Maps will always be better, but the difference will become small enough that no one cares.
Yes, the Apple maps have a few rough spots. But google isn't perfect either. From what I've seen so far I prefer the new Apple maps.
1) It's been a black eye for Apple and users are complaining
2) Apple has a lot of money to throw at the problem
The real question is whether it will get better enough, fast enough.
There's certainly a limit to how much Apple will throw (they're not going to empty out their nest-egg to fix this), and throwing money at a problem doesn't always work so well.
In particular, public-transit and in general any "non-car" data is something their maps simply don't seem to even start addressing. This isn't entirely surprising as their data provider, tomtom, is a car-nav company, but it's a huge hole, and one Apple seems to have completely missed.
One of the reasons Google's public-transit directions took so many years to get good is because teasing the necessary data out of the many different regional agencies/companies that have it is a pain-staking and slow process.
The very poor coverage in many countries is presumably because Apple's existing data providers do not have good coverage of them, so Apple probably needs to contract with region-specific providers, integrate their data (which may not be simple) with the Apple maps infrastructure etc.
All of this is doable, but it takes time, maybe years. They really needed to do a lot of this, or at least a convincing chunk of it, before the big release, not "sometime in the future."
Certainly Apple has reasons to make their own maps, but by releasing such core functionality in a form that's very clearly not ready for prime time, they've damaged their (extremely valuable) reputation as "the company that does things right."
PS: and as for iPad 2 I'm not sure about battery life, I rarely discharge it from 100 to 0 in one session.
I updated my 3rd gen iPad to iOS6 immediately when the update came out since I wanted to check out if the increase in JavaScript performance is noticeable (it is).
However, here's why I regret updating: I've been using the iPad as a second screen on my desk to watch YouTube. After the update, I find that the YouTube icon is missing from its usual place on the home screen. After a quick app store and Google search I find out the truth: Not only there isn't an official iPad-optimized YouTube app anymore, but also that it has the disappointing release date of "in the coming months" [1].
I know the actual reason for the missing YouTube app has something to do with the licensing deals between Google and Apple, but as a generally happy Apple customer my perception is that this "update" makes my life harder.
[1] http://youtube-global.blogspot.com/2012/09/introducing-new-y...
On my iPod touch http://YouTube.com redirects to http://m.YouTube.com goes full screen.
It also features a link to a YouTube app 'free in the App Store" :-)
It works better than the app every did.
The YouTube mobile site doesn't have the apple-mobile-web-app-capable meta tag and thus displays the address bar even if placed as a shortcut on the home screen.
This brings out another issue: The accuracy of search results in the App Store. When searching for "youtube" (sorted by relevance), these apps are listed before "Jasmine - YouTube Client":
- Video Downloader Super Lite
- SoundHound
- SloPro - 60fps Slow Motion Video
- Trololo Sounds (yes, really)
Also being an Android user, I'm used to going through quite a lot of noise when finding the right app though. Let's hope the situation will improve in both stores soon.
This is also the first time (in recent history) that hardcore Apple fans are finding themselves responding to critics by saying, "Yes, that's a valid point, but..." rather than "No, you're wrong because..." Chink in the armor.
http://googlemobile.blogspot.com/2009/07/google-latitude-now...
> We worked closely with Apple to bring Latitude to the iPhone in a way Apple thought would be best for iPhone users. After we developed a Latitude application for the iPhone, Apple requested we release Latitude as a web application in order to avoid confusion with Maps on the iPhone, which uses Google to serve maps tiles.
It took almost two years for Apple to cave.
On the flip side, there's one GOOD feature in nyc rarely remarked on: Having switched to vector-based maps means you can now pretty reliably pan and zoom the map even when you have no signal because you're in the subway.
It's an issue of trust. What problems might I run into in the future, when I am in a position where I cannot fall-back on the Safari version of Google Maps? Low/no signal conditions where I am trying to navigate unknown areas are times when I can't have something that is good enough, most of the time. That's why I downgraded to 5.1.1. Google Maps hasn't let me down yet, and there's no reason why I need to upgrade to iOS 6. The new features are only nice-to-haves.
Just go ahead and upgrade; you'll end up wanting some iOS6 feature / app eventually, might as well get it out of the way now.
I agree with the spirit of your post, but while it's not another antennagate, the "iOS6 maps suck" meme is definitely in the mainstream media consciousness[1]
[1]Google news search "ios6"
I for one like the new privacy settings.
Passbook could be really interesting, but I think it'll be well over a year, before people in my country consider taking advantage of it.