51–60 of 99 posts
I am not an iPhone user. Can someone explain "Do Not Disturb"? I think I am missing something, I thought that was what the switch was on the side of the old iphones?
The native iOS 6 Maps are just short of wretched. No transit directions, unhelpful default views, a dramatically weaker points of interest database, weaker scrolling performance, and a busier UI that doesn't add anything of great use. It's a rather big turd in an otherwise delicious punchbowl, and it is going to become a real-world talking point about iPhones starting today.
I was actually thrilled that for transit directions in NYC, Maps just gave me a button to the Embark app, which won the MTA App Quest for best subway navigation in the city. It has a better interface than Google Maps for transit, anyway. It's obviously an extra step to go to another app, but if the experience is better in the long run, I'm willing to go with it. Google Maps has been annoying on iOS for a while -- eve…
Earlier quoted context omitted.
Yes it's biased, she's deeply opinionated, yes she's an opinioneer, etc... But she's still got a piece of the truth in hand: Maps are important, they're only becoming moreso, and Apple is extremely unlikely to sit on their ass now that they've launched their own stack. (especially once their customer satisfaction numbers start plopping, which they will)
Now that is a much more palatable and understandable angle. I completely agree that it makes sense for Apple to take it in house. I completely sympathize that is a monumental (literally, World-sized) problem to tackle and that for a first-release, this is probably admirable of Apple. I guess I still don't buy that Apple Maps are going to become the ubiquitous success that WebKit is. There's one of two implications at…
(I say this as somebody that was shocked that Apple didn't build Safari 1.0 on top of Mozilla/Gecko. KHTML?!)
The native iOS 6 Maps are just short of wretched. No transit directions, unhelpful default views, a dramatically weaker points of interest database, weaker scrolling performance, and a busier UI that doesn't add anything of great use. It's a rather big turd in an otherwise delicious punchbowl, and it is going to become a real-world talking point about iPhones starting today.
Apple needs to take their massive $$$ warchest and spend an inordinate amount of money on getting maps back up in shape. Each of those $'s is worth it. It's an absolutely crucial feature and it needs to be not just good enough, it needs to be really good and better than most. My fear is now Apple is becoming more bean counter and less passion, strong-opinion driven. To let Maps out in this shape is a troubling misste…
http://www.theregister.co.uk/2012/09/18/amazon_google_map_bm...
Navteq's maps are way better than TomTom's. One of my friends had a TomTom GPS a few years ago and it was terrible, like once taking us around in circles for a restaurant and showing it was three miles away, when we could see it across the street a few hundred feet away. He had such bad experiences with it that he would borrow our Garmins and finally switched to Garmin a year ago. I just assumed that TomTom was Europe based so had much better coverage there and pretty horrible maps in the US.
http://www.pcpro.co.uk/features/375415/how-satnav-maps-are-m...
If I were Google, I would release a very polished maps app for iOS for $10 with ads, but they might be just content with some people picking Android phones just because the builtin maps experience and turn by turn voice directions is really good.
Earlier quoted context omitted.
Now that is a much more palatable and understandable angle. I completely agree that it makes sense for Apple to take it in house. I completely sympathize that is a monumental (literally, World-sized) problem to tackle and that for a first-release, this is probably admirable of Apple. I guess I still don't buy that Apple Maps are going to become the ubiquitous success that WebKit is. There's one of two implications at…
I don't think her point is that it's going to get used in lots of other projects but that it will grow to be a big success, and one that people will look back on and say "Apple was right to set off on this weird-seeming path back then." We'll see, of course. (I say this as somebody that was shocked that Apple didn't build Safari 1.0 on top of Mozilla/Gecko. KHTML?!)
But we all know that, right? Maybe this was just a response to "iOS Maps sux. Apple sux." type comments? I'm not sure. It's hard for me to believe how polar peoples' opinions still are on iOS and Android to have to have these silly conversations.
Earlier quoted context omitted.
Yes it's biased, she's deeply opinionated, yes she's an opinioneer, etc... But she's still got a piece of the truth in hand: Maps are important, they're only becoming moreso, and Apple is extremely unlikely to sit on their ass now that they've launched their own stack. (especially once their customer satisfaction numbers start plopping, which they will)
Now that is a much more palatable and understandable angle. I completely agree that it makes sense for Apple to take it in house. I completely sympathize that is a monumental (literally, World-sized) problem to tackle and that for a first-release, this is probably admirable of Apple. I guess I still don't buy that Apple Maps are going to become the ubiquitous success that WebKit is. There's one of two implications at…
-- They can generate statistics on who's searching for what, when, and where from and sell that off or give it away free to venue operators.
-- They can link custom Apps and content to a venue. (Welcome to the Museum! Tap here to download a free tour guide.") They can link .passbook offers directly on-map. ("Tap here for a discount on entry, today only!")
-- They can sell off preferential search results, preferential ratings, or retargeted advertising like Google and Yelp do.
-- They can do the opposite of that and proclaim that their maps and venue listings are of unimpeachable quality without gamed results
-- They can create a meta-venue datatype through Apple Connect that allows authorized entities to quickly whip up appealing micro-sites for their venues "Drop your menu .PDF here"
-- They can do anything they want with in-venue navigation, which is going to be massive now that the interior mapping tools are coming onto the market
With all this done:
-- They can API-ize this and create mini-sites or mini-apps wrapped in Yelp-y context that replace the entire idea of how you interact with a venue. For instance: "Thai Bistro" is now an App that tells you exactly what's going on with your favorite joint without consulting twitter, facebook, a webpage, and a mapping service.
In short, with this map platform they can now own the total experience of -leaving the house-. Google is years ahead of them on this, and it's unlikely Google's willing to share their advances with their frenemy.
Maps are foundational to representing the state of the civilization around you. It's the Webkit for Real World Experiences.
I am not an iPhone user. Can someone explain "Do Not Disturb"? I think I am missing something, I thought that was what the switch was on the side of the old iphones?
The switch on the side of the phone was just a "silencer," without any fine-grained control. "Do Not Disturb" is a more intelligent kind of silencer -- it silences emails, texts, and any sort of app notifications, but you can let it selectively allow phone calls through (either "Everybody," "All my contacts," or just your "Favorites"), and it has a feature to allow repeated calls through (if someone calls you, then c…
Please tell me that Android has a similar feature?
Glad to see Apple finally address this issue!
Previous discussion: https://news.ycombinator.com/item?id=4339609
Edit: the problem with color profile on SSD drive with FileVault enabled[1] seems fixed also.