Live data from Hacker News

Pushing iOS

jaymachalani.com

81–90 of 90 posts

Re: Pushing iOS

#81
post #79
post #36

> 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 .

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

#82
So these proposed blocks are non-overlapping app windows, neatly tiled within the icon grid.

Isn'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

#84
I stopped reading after the venn diagram showed that the windows phone was good for experience and customisation, are you joking?

Re: Pushing iOS

#85
post #39

Earlier 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.

>So where you live, the weather never changes during the day?

No, I mean it takes all 2 seconds to open the weather app and check.

Re: Pushing iOS

#86
post #79

Earlier 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.

But virtualized would be slower for everybody, right?

Re: Pushing iOS

#87

This guy needs a windows phone, can we get him a windows phone?

I think he forgot the most important rule of all in the Kingdom of Apple, which is that Apple makes the rules. Apple isn't interested in hearing advice, so if you have your own ideas and want to make them happen, the Kingdom of Apple is not for you.

Re: Pushing iOS

#88

Earlier 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.

Like I said, though, "different strokes" ;) I've used an Android Phone with Google Keyboard and Swype as my daily driver for months at a time this year and was insanely relieved to use the iOS keyboard again. I found its predictions and the accuracy of the keyboard itself far more accurate, and the screen responsiveness in another league...

Re: Pushing iOS

#89
post #69

Earlier 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…

This is pretty heavily anecdotal but my parents (late 50s) haven't had any issues with the iOS 7 keyboard. As they say, it Just Works. I think it's heavily dependent on user expectations.

Re: Pushing iOS

#90
post #79

Earlier 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.

It does indeed help a large number of apps (though more and more are going full native since the Facebook app drama).

Jailbreakers have had this for a while now with Nitrous, a tweak which unlocks the Nitro engine to all apps.

Post reply on HN