9 ms·
I get the "apps for utilities" , but "apps for content"? I just cannot see people bothering to download an app for every website they visit and personally i nev
by return0 12y ago
I get the "apps for utilities" , but "apps for content"? I just cannot see people bothering to download an app for every website they visit and personally i never have . Data for this?
- prof_hobart 12y agoIf it's content that I access regularly (BBC News/Guardian/Twitter/Facebook), then I'll have the app. For other content consumption, I'll use the web. What I don't understand is why, for organisations whose primary purpose in life is content, it's even much of a dilemma. Putting together a simple web page or a simple app to serve up identical content different ways should really not be a huge amount of work. If you want your app or site to really stand out from a usability perspective - like Flipboard - then I can understand it. But Flipboard's product is primarily its UI, not its content. For the Beeb and The Guardian, all I want is a reasonably functional app, and I wouldn't be surprised if you could find a free framework for 90% of what you need on Github for that.
- spacemanmatt 12y agoThe mobile web is a poverty zone. If you want content that is convenient, native (or at the very least a well-done HTML5 hybrid implementation) is necessary.