News for hackers. Stuff that matters.
Re:The failed promise of deep links by untog on Tuesday April 07, 2015 @12:32PM (#9335192)
Unfortunately mobile web pages can't run background processes, can't launch AJAX requests to arbitrary domains, speak UDP, do file I/O

Background processes, cross-domain AJAX and file I/O actually are possible now, at least to certain extents. It's getting a lot better, but as you say, Apple drag their feet at every opportunity.

Re:The failed promise of deep links by mcherm on Tuesday April 07, 2015 @01:22PM (#9335579)
Apple gets a 30% cut of all money made on apps, and they don't get this cut for web pages. No wonder they're dragging their feet.
Re:The failed promise of deep links by jdmichal on Tuesday April 07, 2015 @05:48PM (#9337393)
I'm far from an Apple fan, but this statement is so intellectually lazy I have to counter it. The honest fact is that 30% of zero is zero. If having a webpage would be an option, it's overwhelmingly likely that the webpage would be free to access. And if an app is simply a more enabled replacement for the webpage, then the app is also overwhelmingly likely to be free.
Re:The failed promise of deep links by dheera on Wednesday April 08, 2015 @09:01AM (#9340415)
To some extent, sure, but not enough. With an app I can open a TCP connection to any address and fake any referrer I want, and I can use a WebView to open any page regardless of the X-Frame-Options header which iframes cannot do. Hence, I have to write an app instead of a webpage for a lot of these requirements.

Also, HTML5 location tracking is severely broken on iOS. In most cases the user ends up inadvertently blocking permissions for Safari rather than on a per-website basis. The result then is that all future websites get blocked from location access automatically, without even prompting the user.

If HTML5 apps are to take off, the web browser needs to be treated as a basic component of the OS and automatically given full access to location tracking and sensors; it should then be the web browsers' responsibility to ask and confirm with each website and manage those permissions (perhaps even seamlessly integrated with the OS permission system itself).

IMHO the restrictions on HTML5 apps like cross-domain requests and iframes are quite silly. At least there should be a one-click way to "trust" websites in the same way you'd install an app.