Originally Posted by mdriftmeyer
The entire NeXT Services that are part of OS X and iOS but not remotely as well extended and exposed as it is in NeXTSTEP/Openstep should be available in iOS 7 and OS X 10.9.
Within DropBox on either platform should be a much richer and deeper public api that allows for a much richer experience of services. On iOS it has to be as unobtrusive as possible. In OS X it must be much more clearly exposed and leveraged across OS X and Apple must show within its own app suites how they are leveraging it to its fullest.
This is my common refrain for iOS.. it needs to get back to object level services, where the objects truly polymorphic... The beauty of nextstep was the consistency of how object handling by the receiving (messaged) service/app was, even with dramatically different sent objects. That is robustness at it's core.
I find something so simple like 'I need to call/facetime jeff 7am tomorrow" and Jeff is in my contact list, with a phone number, and Siri will schedule it, but the calendar app doesn't understand 'call jeff' is a 'phone number' and that when I go to my calendar, I should be able to click on the 'object' and message it directly into dialing the number in the phone app. (analogous: 'meet jeff at his office:' automagically when I click on the object, it starts the maps app.
This robustness/rich-API is necessary at the core, and then drive it out to the core capabilities of iOS, for both the iPad, the iPhone, and eventually, the iTV(ish solution). The underlying power of the system should 'guide/option' what you intend for each object, ala Siri, asking "What phone number should I call, Home, office, or facetime?" but also it should make it pervasive across all apps (I grab a 'movie' object from rotten tomatoes, and should be able to 'message' that to anything... calendar, iTunes, netflix, thepiratebay;-), whatever....)