Comments on: Goodbye Browsers: What Next? http://www.joelhughes.co.uk/blog/2009/06/goodbye-browsers-what-next/ Wed, 10 Feb 2010 12:06:25 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Joel Hughes’s Blog » Web development is changing to meet mobile needs http://www.joelhughes.co.uk/blog/2009/06/goodbye-browsers-what-next/comment-page-1/#comment-32 Joel Hughes’s Blog » Web development is changing to meet mobile needs Fri, 25 Sep 2009 10:59:45 +0000 http://www.joelhughes.co.uk/blog/?p=169#comment-32 [...] Next time I’m building a new service that needs to be accessible on multiple platforms I think it would make sense to build an API before a website. Until recently I’ve planned projects around browser based distribution, now the browser may become less dominant. [...] [...] Next time I’m building a new service that needs to be accessible on multiple platforms I think it would make sense to build an API before a website. Until recently I’ve planned projects around browser based distribution, now the browser may become less dominant. [...]

]]> By: Flow » Blog Archive » Daily Digest for June 5th - The zeitgeist daily http://www.joelhughes.co.uk/blog/2009/06/goodbye-browsers-what-next/comment-page-1/#comment-20 Flow » Blog Archive » Daily Digest for June 5th - The zeitgeist daily Fri, 05 Jun 2009 05:28:11 +0000 http://www.joelhughes.co.uk/blog/?p=169#comment-20 [...] Goodbye Browsers: What Next? How technical design for web apps is chaging. — 7:57pm via Google [...] [...] Goodbye Browsers: What Next? How technical design for web apps is chaging. — 7:57pm via Google [...]

]]> By: JoelHughes http://www.joelhughes.co.uk/blog/2009/06/goodbye-browsers-what-next/comment-page-1/#comment-19 JoelHughes Thu, 04 Jun 2009 14:31:23 +0000 http://www.joelhughes.co.uk/blog/?p=169#comment-19 More good discussion over at <a href="http://news.ycombinator.com/item?id=639695" target="blank" rel="nofollow">Hacker news</a> More good discussion over at Hacker news

]]> By: JoelHughes http://www.joelhughes.co.uk/blog/2009/06/goodbye-browsers-what-next/comment-page-1/#comment-18 JoelHughes Wed, 03 Jun 2009 21:38:26 +0000 http://www.joelhughes.co.uk/blog/?p=169#comment-18 You're absolutely right about G.Reader and the browser, what I really meant to illustrate was that the standard HTML site may be dying rather than the browser (although I do think being able to deliver content and services into other platforms will become more important). You're absolutely right about G.Reader and the browser, what I really meant to illustrate was that the standard HTML site may be dying rather than the browser (although I do think being able to deliver content and services into other platforms will become more important).

]]> By: madaerodog http://www.joelhughes.co.uk/blog/2009/06/goodbye-browsers-what-next/comment-page-1/#comment-17 madaerodog Wed, 03 Jun 2009 21:01:07 +0000 http://www.joelhughes.co.uk/blog/?p=169#comment-17 Quite a revelation of a post you've got here! <br><br>I've been doing some research for my community <a href="http://harkopen.com" rel="nofollow">http://harkopen.com</a> and I am currently learning about rdf and his benefits, it will be included natively in Drupal 7 from what we've heard and will try to use it to extend the web's power beyond the browser. Quite a revelation of a post you've got here!

I've been doing some research for my community http://harkopen.com and I am currently learning about rdf and his benefits, it will be included natively in Drupal 7 from what we've heard and will try to use it to extend the web's power beyond the browser.

]]> By: David Semeria http://www.joelhughes.co.uk/blog/2009/06/goodbye-browsers-what-next/comment-page-1/#comment-16 David Semeria Wed, 03 Jun 2009 20:59:10 +0000 http://www.joelhughes.co.uk/blog/?p=169#comment-16 But Google Reader runs in the browser!<br><br>The whole point of browser-based development is that you don't need to download a separate client for each application.<br><br>Even if you choose to build your service as an API rather than a website, the content will more than likely be accessed by a browser-based aggregator.<br><br>The browser will be around for a long time yet, although I agree that the need for certain types of content-driven websites is diminishing as people consume more through aggregators. But Google Reader runs in the browser!

The whole point of browser-based development is that you don't need to download a separate client for each application.

Even if you choose to build your service as an API rather than a website, the content will more than likely be accessed by a browser-based aggregator.

The browser will be around for a long time yet, although I agree that the need for certain types of content-driven websites is diminishing as people consume more through aggregators.

]]>