Salesforce is taking a rather unusual stance in an effort to avoid this problem. Starting with an update to its Salesforce1 app later this year, the company will offer support for its app only to those using certain Google Nexus or Samsung Galaxy devices.
The company declined to go into detail on its reasoning, but confirmed in a support document that it is looking to maximize its development resources.
Archive for Android
The iPhone is “faster; smoother. Android freezes up” and has to be restarted too often, the source said. The problem with the Android is particularly noticeable when viewing live feed from an unmanned aerial system such as Instant Eye, the source said.
In the release, Microsoft noted that its patent-licensing revenue was down 26% from a year ago. And it’s because of Android.
Android phones are still selling just fine, but the market is dominated by cheap handsets being sold in developing countries like China and India.
“The mix of devices in that market has shifted to the low end,” said Chris Suh, Microsoft’s head of investor relations.
Android offers a bevy of excellent features that iOS doesn’t—and frankly, probably never will—but it’s a matter of what I’m willing to trade off. Android’s customization is refreshing, but what iOS lacks in tinkering it makes up for in usability. Every feature Apple implements is seriously considered for the effect it has on the user, an attention I didn’t feel with Android.
That’s a very good question. We’ve been speculating about this for a long time, and what we’ve managed to figure out is that it’s a combination of a couple of factors:
- Just more code – applications for Android are written in Java, which is simply a more verbose language
- Emulators are slower – Android emulators are just slower than iOS simulators.
- Fragmentation – more devices to test against, more potential vendor-specific bugs
- XML layouting – on Android, layouts are primarily written manually in XML, so WYSIWYG techniques are used less than on iOS.
Nope. Mobile web and mobile in-app behaviour are not binary. When users are in the facebook app, they spend a tremendous amount of time accessing the mobile web through facebook’s own in-app browser. The same for twitter and others. We enter social apps for discovery and then access the mobile web while still in-app. It is a mistake to conflate time spent on the mobile web with time spent in a traditional browser.
“In this attack, victims’ fingerprint data directly fall into attacker’s hand. For the rest of the victim’s life, the attacker can keep using the fingerprint data to do other malicious things,”
This is the fundamental difference between Android and iPhone. When there’s a bug on iOS, Apple patches it and can push an update to all iPhone users as soon as it’s ready, no questions asked
Source: Goodbye, Android | Motherboard
“We were finding Android in general to be a slower platform to move on. There’s more time spent dealing with fragmentation bugs. There’s more time spent dealing with testing and debugging, and we would rather spend that time building new functionality.”
Meanwhile, Pebble keeps announcing new features that work pretty well with Android. The Pebble Time has a microphone you can use on Android–or a single app on iOS. It’s not hard to see which way the wind is blowing. Google, the owner of the Android platform, is working to enable features that support smartwatches from various vendors. Meanwhile, on iOS, what smartwatch strategy do you think the platform owner is focused on?
I’m sure Pebble Time will work, more or less, with iPhones. But it’ll be second-rate functionality compared to Pebble for Android. Meanwhile, here comes the Apple Watch: A product designed to work seamlessly with iOS. Which is going to offer a better experience?