Earlier quoted context omitted.
Okay, and why does that mean it needs access to my complete filesystem rather than just a little namespaced, security-controlled chunk of filesystem allocated by the OS to it?
Historically, on Android, there has been very little space in the data area for each individual app. An app that cached to that would have been unusable on my Nexus One for example, where I constantly had to delete apps whenever I wanted to install a new one, and I had very few - something like 10 or 15. The best place for the user has been to cache to the SD card, or the internal storage partition setup to look like…
No, I'm not going to download your bullshit app
81–90 of 222 posts
Re: No, I'm not going to download your bullshit app
#82Earlier quoted context omitted.
I don't see why that makes the case for native apps more compelling.
It helps the consumer because if it's a good app, it allows you to better focus on that one task you're after. Reading the news, for example. I haven't had any of the problems he discusses with the NYTimes app, for example. For the organization, the benefits of longer engagement are pretty obvious as well. He's right about a lot of bad developers (and clueless execs) producing really crappy apps. He's wrong if he thi…
Want swipe page turns ? That can be done in web. Scrolling? Zooming? Etc etc can all be done with a website.
Apps have there place, but I don't think news readers are it.
Re: No, I'm not going to download your bullshit app
#83Also note that Apple was against Flash mainly because it contradicts with this walled garden approach. Web+Flash (or HTML5 today) was the standard and free way of building almost all of the "apps" in the PC era. Native may have a performance gain in the short term (which becomes irrelevant in the long term as Moore's law dictates) but our loss of time and standardization in the development of an open and accessible (mobile) web lasts longer.
Re: No, I'm not going to download your bullshit app
#84I agree for the most part with this article. I think the major problem is that apps are being developed that offer absolutely no advantage over viewing the website in a browser - in fact many offer disadvantages. This is what happens when a market crowded with some shockingly bad app developers is combined with ignorant executive mandates that companies must have apps simply to be able to say that they have them.
They're popular with people who take the subway. Think about it, you're sitting there for half an hour with no service. An app that pre-downloads all of a newspaper's stories is handy and easy to use.
Re: No, I'm not going to download your bullshit app
#85I find the default iOS popup advertising an app the worst part, by large the app offers extra functionality over the web. the popup disrupts the experience and I also have the same feelings of rage on random site for some random stupid bullshit app. The compass in the iPhone for example, does device allow a web server query the phones heading through browser? Offline modes and caching are features not really possible…
As of April 2011, the article claims various degrees of support from mobile Chrome, Safari, Opera and Firefox.
There's also plenty of work on application caching and offline support (though, to be fair, that's a very hard problem): http://www.html5rocks.com/en/features/offline
Re: No, I'm not going to download your bullshit app
#86I wrote an app which uses rss feeds and smart preloading of data when it is not yet visible. Making it blazingly fast. I don't want to wait for we website to load.
Re: No, I'm not going to download your bullshit app
#87And most apps require permissions that have very little to do with the purpose of the app. Here's what the BBC news reader for Android wants: THIS APPLICATION HAS ACCESS TO THE FOLLOWING: HARDWARE CONTROLS CHANGE YOUR AUDIO SETTINGS Allows the app to modify global audio settings such as volume and which speaker is used for output. NETWORK COMMUNICATION FULL NETWORK ACCESS Allows the app to create network sockets and…
I'm not an expert on Android permissions, but those seem reasonable to me. What permissions do you have a problem with, and what should they replace it with, or do you think is totally unnecessary?
Re: No, I'm not going to download your bullshit app
#88This doesn't solve the problem of URIs or of different layout/content/etc. for web vs e-book, but it does solve the data-container-as-app problem.
Re: No, I'm not going to download your bullshit app
#89Re: No, I'm not going to download your bullshit app
#90Earlier quoted context omitted.
Historically, on Android, there has been very little space in the data area for each individual app. An app that cached to that would have been unusable on my Nexus One for example, where I constantly had to delete apps whenever I wanted to install a new one, and I had very few - something like 10 or 15. The best place for the user has been to cache to the SD card, or the internal storage partition setup to look like…
One issue with these permissions is that I don't have a clue what they mean. Does the list of permissions I posted give that app the right to read all my personal data and upload it to one of their servers? Can it delete all my contacts or pictures? Can it make phone calls on my behalf or record my phone calls and upload the audio file to a server?
Pictures are stored on the SD card, so the app could read all your pictures, upload them, then delete them. Newer devices have more internal storage, so hopefully applications will gradually move away from using this permission. Apparently, the next version of Android will introduce a new permission for reading the SD card too -- at present, any application may read from the SD card.
"Read[ing] all my personal data" depends on what you count as personal data -- security-sensitive info should not be on the SD card (things like phone number (although the phone state and identity permission gives access to this), contacts, account details), but anything that is on the SD card may be read by any application. That means pictures and music, at least.
I wonder if it might be useful to always list all of the common permissions, to make it easier to see which ones an application doesn't have. I've installed enough Android apps to have a reasonable idea of what's available (and by extension, what any given app can't do) but it's reasonable to assume I'm in a small minority.