Why Web 2.0 doesn't cut it for mobile devices
I'm lounging around the Blogosphere waiting for "Cold Pizza" to start on ESPN2 and came across this very insightful post from Michael Mace about Web 3.0, explaining why the goldrush towards Web 2.0 leaves mobile devices out in the cold because of the differences in the developmental model. He states that proper application design and architecture for wireless devices needs to differ than desktop and/or web apps, requiring a local cache and local client in the event the devices they run on are out of signal range for a network connection.
Matt McAlister commented on the need to effectively balance the requests from your data in mashups as opposed your site's normal web traffic (public APIs seem to be under the 3.0 space, in contrast to Tim O'Reilly's theory that they should be part of the Web 2.0 movement). But now we're faced with the challenge of applying business models around the Web 2.0 fundamental concepts as a means of generating revenue. Ad-supported mechanisms seem to be the popular solution
Matt McAlister commented on the need to effectively balance the requests from your data in mashups as opposed your site's normal web traffic (public APIs seem to be under the 3.0 space, in contrast to Tim O'Reilly's theory that they should be part of the Web 2.0 movement). But now we're faced with the challenge of applying business models around the Web 2.0 fundamental concepts as a means of generating revenue. Ad-supported mechanisms seem to be the popular solution
0 Comments:
Post a Comment
Links to this post:
Create a Link
<< Home