Ars Technica has an interesting article about how “Android is open—except for all the good parts”, which they’ve been making proprietary.
It’s a warning to developers who integrate with proprietary Google APIs — maps APIs, cloud messaging, location APIs, in-app purchasing, “Play Games” API. When they embrace Google’s great APIs, it makes it more difficult to port to Kindle Fire and other Android derivatives.
My overall feeling is that Google gives users more freedom with Android than Apple gives users with iPhone/iOS. (Sidenote: In spite of that, I like iOS slightly better).
Closing the good parts doesn’t mean there’s no competition — there’s still iPhone and Windows Phone.
Do you ever read the fine print when you install an application, and it presents you with an end-user-license-agreement?
Recently, I installed the Fidelity iPhone app, and here’s a few surprising parts of their service agreement:
By using the Services, I consent to the transmission by electronic means…. I acknowledge that Fidelity cannot assure the security or privacy of electronic transmission of such information. Any transmission may also be subject to other agreements that you have with your mobile service or access device provider. Accordingly, I must assess whether my use of the Services is adequately secure to meet my particular needs.
While all information accessible through the Services has been obtained from sources believed to be reliable, I understand that Fidelity will not be responsible whatsoever for the accuracy, timeliness, completeness, or use of any information received by it or received by me from Fidelity or any Provider through the Services and that Fidelity does not make any warranty concerning such information.
I don’t think most of us are capable of assessing whether our use of a third-party service is adequately secure — it’s difficult for security professionals to decide such things.