3 ms·
Solution: Stop building apps for your content. That's what the web is for. If deep-linking is a requirement, it's probably not well-suited to an app.
by tootie 12y ago
Solution: Stop building apps for your content. That's what the web is for. If deep-linking is a requirement, it's probably not well-suited to an app.
- gkop 12y agoUnfortunately, gatekeepers make rich content impossible on the mobile web. For example, when will Apple support WebRTC in mobile Safari? Until then, certain interactive content requires an app, yet we still may want to address this content with these links.
- tootie 12y agoFucking Apple hasn't announced support for HTTP/2 yet either. Considering the biggest bonus is decreased latency which is huge for mobile, they are clearly just pushing developers to apps because that's their business.
- dheera 12y agoI agree with this conceptually. Unfortunately mobile web pages can't run background processes, can't launch AJAX requests to arbitrary domains, speak UDP, do file I/O, and numerous other things, which is why people end up writing apps. Also mobile web browsers still suck, unfortunately. Safari still hasn't gotten its act together with simple stings like scrolling, and is riddled with CSS bugs of sorts if you try to do anything advanced with HTML5 (e.g. pull to refresh, swipe gestures). It's almost like Apple is deliberately refusing.
- untog 12y agoUnfortunately 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.
- mcherm 12y agoApple 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.
- jdmichal 12y agoI'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.
- dheera 12y agoTo 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.
- serve_yay 12y agoBoy, if you think Safari is bad at scrolling you're in for a world of hurt.