Geez Apple just keeps doing terrible on the app developer relations front. I have talked with startup founders time and time again they tell me their iOS apps are more barebones because Apple's policies or permissions prevent them from implementing the same features they can implement on Android
How is 'not publishing unlisted APIs that have been unpublished for years' Apple 'doing terrible things'.
These guys blatantly violated the TOS. There should be no surprise here. If anything what they did was basically a stunt.
> I have talked with startup founders time and time again they tell me their iOS apps are more barebones because Apple's policies or permissions prevent them from implementing the same features they can implement on Android
Apple implements things at the pace they want. That's one of the reasons things in iOS are generally well thought out and it's so hard for a rogue app to destroy battery life or violate your privacy.
Apple chose the trade offs they want to make, andnit seems to be working very well for them.
This is the Safe Browsing API not a cozy relationship with Google but instead use of an API that many browsers use to ensure downloads are not embedded with malware to protect the end user and also to make sure you don't inadvertently go to a phishing site and get owned.
Even more odd is they still have their message about FF not being supported for Inbox up for Nightly. I just switched my User Agent to Chrome and Inbox works fine in FF.
Please, elaborate. I was under the impression that the Intex 1.3 branch was entirely separate from the main trunk and it would take some time to merge it back in.
It would be nice if they allowed the community to form a foundation and transferred the trademark to the foundation that way they don't give the entire community and project a bad name.
