Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Tim Cook at D11: Apple to Open Up APIs in the Future, but No Chat Heads
- Thread starter MacRumors
- Start date
- Sort by reaction score
THANK YOU. Those chat heads are annoying in Facebook and I can't imagine how annoying they'd be in the entire interface. How would you use the home screen if there are bubbles all over it?
You must build your own phones? Every company makes the choices for you and then you choose if you want what they offer...
No different with Apple, not sure where the surprise is coming from.
How about...the fact jailbreaking doesn't do this to you?
Have you ever tried an open version of iOS, or do you just like propaganda?
Please just let other browsers use their own code base on your OS!!! Stop being a monopoly of browsers in your OS!!! I just want Chrome, its 10x better then Safari. Same goes for e-mail, let me choose my own e-mail client on your phone and let me set it as the default!! Not to mention let me get rid of newstand haha.
Yep - think thats the word I was looking for.
Tim will find out how I feel about that if he allows FB through the door.
Im about sick of FB and what its turned into, it onyl has one way to go......
My impression is that Tim Cook is what he's always been, Tim Cook. I don't think you could point out any company that has a brighter CEO right now than Apple does. What he said about wearable watches is of course absolutely true; one criterion for "good" is that "anybody who is not a total geek or professionally interested would wear one", and with that criterion there's nothing "good" out there.
Of course you do. Unless you buy products of some other company, then you pay _them_ to make choices for you.
You are really trying very hard to find fault here, aren't you? This interview was about a person with deep knowledge about "all things digital" passing on some of his knowledge to the public. It wasn't about Apple announcing its product strategy.
As usual, iGrip trying to see things in the worst possible light. Fact is that Apple knows better how to make a good product than 99.999999% of its customers, and most customers are very happy both about Apple making choices for them, and with the choices that Apple makes.
Last edited:
Facebook Home for iPhone
Facebook Home related app is coming to iOS with a new teaser
http://www.youtube.com/watch?v=50Bu99DPHAY
Facebook Home related app is coming to iOS with a new teaser
http://www.youtube.com/watch?v=50Bu99DPHAY
Everytime you buy a product you have paid the company making it to make choices. Engineering is about making choices. So if you buy an Apple product, you do pay Apple to make choices for you.
Swype is one of my favorite features of Android. It makes typing so much more efficient. Widgets on the other hand aren't really a game changer, but they are a nice addition.
I hate Chrome. It calls home every five seconds.
Further it is not better than Safari with maybe one exception, there are more extensions available.
----------
Apple opens up more API's every time it releases a major update. Last time it added over a hundred APIs.
If Apple does allow swype, it will probably be as a system-wide update via IOS.
...
I liked the idea of chat heads but they are far too invasive. I would much rather have messages show up in a drop down with the ability to reply right from the drop down (compose messages straight in notification centre without having to open any other app for e-mail, messaging, Facebook, twitter etc)
I liked the idea of chat heads but they are far too invasive. I would much rather have messages show up in a drop down with the ability to reply right from the drop down (compose messages straight in notification centre without having to open any other app for e-mail, messaging, Facebook, twitter etc)
"The customer pays us to make choices on their behalf."
And there, in one sentence, you have the difference between Apple and Google/Android. Yes, it's good for some people...but for those that WANT choices, it's the thing that drives them away from iOS.
And there, in one sentence, you have the difference between Apple and Google/Android. Yes, it's good for some people...but for those that WANT choices, it's the thing that drives them away from iOS.
If you don't care about Tim Cook at D11, then why are you at an article titled "Tim Cook at D11: Apple to Open Up APIs in the Future, but No Chat Heads"?
Also, I didn't know saying that offering an opinion (when asked) on current wearable technology meant you were trying to be like Steve Jobs. If that were the case, there are surely a ton of people trying to be exactly like Steve, right?
It's funny right? The speculators have so little to go off that benign statements like "more APIs" becomes a headline...when the new API count is always just part of every WWDC "by the numbers" opening.
So in other words, we have people here that don't watch any WWDC events going on and on about apple "finally" opening up to developers....when this is what happens each and every year.
In fact, Apple released more than 1700 new APIs (gizmodo) last year, 1500 in 2011 (allthingsD), and 1500 in 2010 (wired).....and this was just for iOS.
In short, as usual, the headline gleamers continue to know nothing about what Apple delivers to its developer community.
Oh, FFS.
Yes, you absolutely do. To not acknowledge that choices Apple makes for the product, hence are for you (the customer), is profoundly asinine. Apple chooses "for me" to use aluminum and glass in my MBP rather than plastic. I have no choice in the matter other than to not buy a MBP altogether. Choices made by Apple are choices made "for me", by extension. I don't see it as a bad thing, either. If I don't like it, I don't buy it.
Yes, you absolutely do. To not acknowledge that choices Apple makes for the product, hence are for you (the customer), is profoundly asinine. Apple chooses "for me" to use aluminum and glass in my MBP rather than plastic. I have no choice in the matter other than to not buy a MBP altogether. Choices made by Apple are choices made "for me", by extension. I don't see it as a bad thing, either. If I don't like it, I don't buy it.
The browser code base rule has more to do with the security implications of allowing apps that execute arbitrary downloadable code than a simple " no web browser" clause, which is why things like Opera Mini are allowed. It's probably an avenue they just aren't willing to open up in general, but I guess it's possible they could allow some very specific process for approving these kinds of apps, but why? I don't think enough people care about the rendering engine that displays a site- and you can already make a browser that adds any number of features to the "chrome" surrounding the render window (iCab, Atomic Web, etc).
I'm still not sure why people complain so much about a default mail client- 99% of the time I read mail by going to the Mail icon and tapping on it. The only other time would be if you're sending mail from another app, but that's just using the system wide mail compose API in front of the app you're already in. I guess you'd still have to configure Mail so it would have accounts to send to, but I'm not seeing the major functionality loss here.
If anything, Apple could enhance the multitasking API for certain apps to allow receiving data over a longer period of time, but again they'd have to find some kind of way to keep rogue apps from draining the battery indefinitely.
