Re: The Browser Is Dead

Nah, I don't see it.

First off, the browser represented a whole new channel: online.  Completely new.  The mobile play is an adjunct and complements the bigger screen experience with global positioning (and portability).

So, to your question, Chris, yeah, keep on truckin' and the valuable reflection is "how can I make use of the unique features of mobile devices to solve my users' real problem/need/desire?" (and the most lucrative ones are the needs that the user doesn't realize they have, yet).

The bar is raising in terms of the mobile device experience, so the other subtle shift is keeping up with rising User Interaction (UX) expectations.  The devices are catching-up in overall capability and are becoming "thicker" (i.e. caching more, processing more).  As we're conceiving of solutions, we'd be smart to keep pace and push more processing up to the devices, in proportion to their increasing capability.

- John

--- In [email protected], Chris Morris <chrismo@...> wrote:
>
> A while ago at one of the DFW PragProg meetings, Dave threw out the
> conversation starter, "The Browser Is Dead." IIRC, he said he thought it to
> be dead in the same way the landline phone is dead - everyone still has one,
> but it's on its way out or somesuch. Having specific apps to deal with
> different data (e.g. map data) seemed to be a better way. (Insert massive
> memory disclaimers here: I may not only have not remembered Dave's points
> correctly, but may have in fact dreamed the conversation in a Spring Creek
> cobbler induced sugar coma).
> 
> Today, along with an announcement about BaseCamp mobile being developed as a
> web site without specific phone apps, DHH tweeted this: RT @dhh: Taking your
> web app mobile just for iOS in 2011 is like taking your business to the web
> just for IE4 in 2001.
> 
> I myself find the issue an interesting one - the browser hosting apps vs. a
> desktop hosting apps vs. a phone OS hosting apps - it all seems very blurry
> to me. But is there any point in debating approaches here, or is it simply a
> matter of determining your specific needs and not worrying about it? (e.g.
> Need for Speed for Android needs C library support and trying to do that as
> a browser app makes no sense).
> 
> 
> 
> 
> -- 
> Chris
> http://improvingenterprises.com
> http://clabs.org
>