> Seriously, for a device so thin in features and actual stuff to do, performance is disappointing. Really? Have you checked well written apps and what they can do? > The Google Chrome browser scrolling is horrific at times with a HUGE delay. How is that an iOS's "performance problem"? Use Safari. It's not like iOS doesn't offer the best scrolling experience compared to Android/Chrome.
It's iOS' performance problem because Chrome is forced to use a UIWebView instead of the Nitro engine: https://developer.chrome.com/multidevice/ios/overview .
Pushing iOS
81–90 of 90 posts
Re: Pushing iOS
#82Isn't that basically what Xerox Star did in 1981? http://www.digibarn.com/collections/screenshots/xerox-star-8...
Or -- the horror -- MS Windows 1.0 in 1985: http://fulupik.chez.com/perso4/Images/infor_win101tile2.gif
Re: Pushing iOS
#83Re: Pushing iOS
#84Re: Pushing iOS
#85Earlier quoted context omitted.
> - Weather info. Before heading out for the day I can see instantly if I might need a jacket or umbrella later. Yes, otherwise it takes all 2 secs to do that.
So where you live, the weather never changes during the day? I don't use weather widgets, but "looking outside" is hardly an effective way of seeing if you need an umbrella, especially now in the Spring.
No, I mean it takes all 2 seconds to open the weather app and check.
Re: Pushing iOS
#86Earlier quoted context omitted.
It's iOS' performance problem because Chrome is forced to use a UIWebView instead of the Nitro engine: https://developer.chrome.com/multidevice/ios/overview .
It would be wonderful if Apple virtualized the UIWebView process so it could safely use nitro. Not only would it help Chrome (not that I bet Apple cares :), but also a huge number of applications. And, if apps were fully virtualized, it could possibly open up new, interesting possibilities that have been heretofore deemed unsafe.
Re: Pushing iOS
#87This guy needs a windows phone, can we get him a windows phone?
Re: Pushing iOS
#88Earlier quoted context omitted.
Different strokes, I guess - I dread using my work Android phone's keyboard (or any of the 3rd party ones I've tried) whereas iOS's hit detection/autocorrection mostly feels like an extension of my brain/fingers.
As someone who switched recently, I find both the Samsung Keyboard on the Note 3 and the Google keyboard are light years ahead of the iOS keyboard even before considering the ability to use handwriting recognition in place of typing.
Re: Pushing iOS
#89Earlier quoted context omitted.
People leaving for keyboard reasons are generally, and I hate the term, 'power users'. For 90% of the iOS customer base the keyboard works perfectly well, I'm not the biggest lover of it but I think it's reasonably solid for what it is and what it does.
I don't think this is necessarily true. Yes, people leaving for keyboard-feature reasons are power users. But there are other keyboard reasons. For example, iOS7 totally broke the keyboard so that fast touch-typists just can't type on it any more. This doesn't matter on something small like a phone, but on an iPad it is super-frustrating. Apple fixed it somewhat in recent updates but it's still broken in a few basic…
Re: Pushing iOS
#90Earlier quoted context omitted.
It's iOS' performance problem because Chrome is forced to use a UIWebView instead of the Nitro engine: https://developer.chrome.com/multidevice/ios/overview .
It would be wonderful if Apple virtualized the UIWebView process so it could safely use nitro. Not only would it help Chrome (not that I bet Apple cares :), but also a huge number of applications. And, if apps were fully virtualized, it could possibly open up new, interesting possibilities that have been heretofore deemed unsafe.
Jailbreakers have had this for a while now with Nitrous, a tweak which unlocks the Nitro engine to all apps.