3 ms·

My thoughts: - Passport looks really cool. I also can't help but think this app is a further hint to an iPhone 5 "NFC" feature - Really impressed by maps. I

My thoughts: - Passport looks really cool. I also can't help but think this app is a further hint to an iPhone 5 "NFC" feature - Really impressed by maps. I hope it works as good as it looks. I'm currently using MotionX GPS Drive for turn by turn directions and I can't wait to get rid of it - Do Not Disturb: THANK YOU. Turning on Airplane mode at night was a bad substitute for this much-needed feature - Siri enhancements are nice, but would have loved to see API integration. I understand why they aren't doing this (yet), though. iOS would need, at the very least, some kind of Andriod-like "intents" system to make it work. Even better would be a standardized way to "teach" Siri about things (think RDF). This seems like one of those things they won't release until they really make sure it's done correctly, as otherwise the disparity between how Siri works natively and what it understands via API integration would be laughable. - Also with respect to Siri, I'd like to see Apple improve the voice synthesis. Don't get me wrong, it's pretty good, but it also isn't state of the art. The voice could be made smoother and better able to communicate Siri's "mood" (if and when Siri is synthesized to have one). Even without a "mood", her voice could stand to be less monotone. I would also like to be able to purchase different voices. - Guided Access (specifically the "one app mode") is going to be huge for enterprise as well as education. I've been on more than a few iPhone "enterprise feasibility" projects where the fatal bullet was lack of the company's ability to lock out the home screen - Facebook integration is nice (and predictable). I really look forward to the contacts and calendar integration more than anything - I thought they might announce third party apps for Apple TV, but I bet they're going to wait until the new TV product announcement for that And if anyone at Apple is reading, here's my obligatory wish-list: - Siri API integration and expandability (duh) - A "guest code" if you have a password lock. I shouldn't be worried about prying eyes if someone borrows my phone. I should just tell them to enter "1234" on the lock screen and it should open up to some kind of "guest account" with none of my personal data, push notifications, browser history, emails, etc. - Better support for external displays in the iTunes and Maps apps. If I am driving, I'd like my car's display to show me the artist and song information at minimum. I won't switch to Map's turn by turn unless it integrates with my external display. If it does, I'd like it to overlay new artist and song information briefly when I change tracks

cleo_ 14y ago
Instead of a "guest code," they really need to implement real multi-user environments. While somewhat nonsensical on a phone, it's greatly needed on family iPads. Then the iPhone could pick up a guest account for "free."
diminish 14y ago
"Flyover and turn-by-turn navigation will be available only on iPhone 4S and iPad 2 or later" Welcome to iOS fragmentation.
- chrisdroukas 14y ago
  That's not how fragmentation works.
- gks 14y ago
  Fragmentation at the API level is the real problem. Not at lack of "built-in features." An app written for iOS 6 can run on the iPhone 4S, iPhone 4, and iPhone 3GS (not to mention the iPad 2 and 3, and the newest iPod Touches). An app written for ICS can only run on those 7% of devices running ICS. This is how fragmentation works. The only fragmentation happening on iOS is for the original iPhone, iPhone 3G, iPad 1, and the old iPod Touches. The only one that I don't quite grasp is the original iPad. Running on the same processor as the iPhone 4 and is much faster than the iPhone 3GS. Color me somewhat confused by this one.
  - diminish 14y ago
    First, APIs are simply features exposed for developers' use. A map function not supported on a device, means the API isn't supported neither, and if your 3rd party development needs this API, it needs this function, namely access to this feature. Second, you are confining yourself to fragmentation from a developer perspective, and fragmentation matters for other purposes too. Third, your Android example is flawed; to just shuffler your argument; a function developed for Android 2.3 can run on 2.3 and later versions. And you only need ICS, in case you need a new "built-in feature" available in ICS. Alas, an ios6 app benefiting from new maps, won't work in a substantial proportion of ios devices. Fourth, the other side of fragmentation is diversity; and you may write a corporate app, for a pen based samsung galaxy note, with a giant screen and give it to your sales users.

cleo_ 14y ago

Instead of a "guest code," they really need to implement real multi-user environments. While somewhat nonsensical on a phone, it's greatly needed on family iPads. Then the iPhone could pick up a guest account for "free."

diminish 14y ago

"Flyover and turn-by-turn navigation will be available only on iPhone 4S and iPad 2 or later" Welcome to iOS fragmentation.

chrisdroukas 14y ago
That's not how fragmentation works.
gks 14y ago
Fragmentation at the API level is the real problem. Not at lack of "built-in features." An app written for iOS 6 can run on the iPhone 4S, iPhone 4, and iPhone 3GS (not to mention the iPad 2 and 3, and the newest iPod Touches). An app written for ICS can only run on those 7% of devices running ICS. This is how fragmentation works. The only fragmentation happening on iOS is for the original iPhone, iPhone 3G, iPad 1, and the old iPod Touches. The only one that I don't quite grasp is the original iPad. Running on the same processor as the iPhone 4 and is much faster than the iPhone 3GS. Color me somewhat confused by this one.
- diminish 14y ago
  First, APIs are simply features exposed for developers' use. A map function not supported on a device, means the API isn't supported neither, and if your 3rd party development needs this API, it needs this function, namely access to this feature. Second, you are confining yourself to fragmentation from a developer perspective, and fragmentation matters for other purposes too. Third, your Android example is flawed; to just shuffler your argument; a function developed for Android 2.3 can run on 2.3 and later versions. And you only need ICS, in case you need a new "built-in feature" available in ICS. Alas, an ios6 app benefiting from new maps, won't work in a substantial proportion of ios devices. Fourth, the other side of fragmentation is diversity; and you may write a corporate app, for a pen based samsung galaxy note, with a giant screen and give it to your sales users.