software development

Browser innovation will happen. Google will drive it

I definitely ruffled some feathers with my last blog post, “The web sucks“.

The hardcore web developers are pretty upset. Those who have never developed for the iPhone, or are strong believers in standards and openness, tend to leave comments like, “you suck!” Really mature.

The more intelligent commenters seem to get my point. They do acknowledge that the web platform is innovating very slowly, and has quickly been eclipsed by native mobile apps.

I don’t know what the solution to the browser problem is. Maybe non-standardization isn’t the way to go, it’s just one option I propose.

I don’t think the web will die, but if the web platform loses any market share at all, Google stands to lose the most. That’s why I think they will lead innovation.

1. Google should drop support for IE6 across the board, most notably, in GMail. If they did this, imagine how much market share IE6 would lose, overnight! Even the slowest IT departments out there would no choice but to figure out an upgrade plan.

2. Google Chrome should release some non-standard APIs that make Google web apps really standout. You want to use GMail in all its glory? Then you have to use Chrome. Other browsers may or may not implement the APIs that Chrome creates. Developers may or may not use the Chrome only APIs to enhance their apps.

But people won’t complain about the non standard Chrome SDK because:

  1. It’s Google
  2. Google will open source it
  3. Other browsers will copy it
  4. The apps developed with it will be better than ever

And with that, a new era in browser competition and innovation will be born.

The web sucks. Browsers need to innovate

The web as an application platform stinks, and I think this is even more apparent now as we see incredible iPad apps being released. Why are iPad apps, in their initial versions, so much better than websites that have existed for years?

When I started writing this post last week, it was going to declare the end of the web. I’m not quite ready to call it dead, but it’s on thin ice.

The web is great as a generic platform for consuming flat, static content, but isn’t good for anything rich

  • AJAX is just a band-aid to make a platform that is based around page refreshes feel more interactive.
  • Java and Flash are yet more band-aids to make the web feel fluid. But remember that feeling you get when you hit a page with Java on it? Gross.
  • Web applications don’t have threading, GPU acceleration, drag and drop, copy and paste of rich media, true offline access, or persistence. Are you kidding me? Gmail only recently added inline images (and it’s super buggy).
  • Web based email broke the mailto, one of the most basic commands for creating an email message.
  • Developer tools for native apps are better than web tools. XCode and Interface Builder are phenomenal. So is Visual Studio on the PC. On the web, people still use plain text editors.

People are using apps more because the experience is much better. We will see a decline in web traffic and search in the coming years

  • People use web search today because they don’t know how else to find high quality information. The web is a mess of content with no organization. On an iPhone, I launch the appropriate app.
  • When talking about iAds on April 12, Steve Jobs said, “Search is not where it’s at, people are not searching on a mobile device like they do on the desktop.” I actually think the issue here isn’t desktop vs mobile, but web vs apps.
  • Full six years ago I blogged about people’s over dependence on search. I felt Google’s search results weren’t as good as visiting the specific site with the information needed. Instead of blaming Google, I should have blamed the web as a whole.
  • Many iPad apps are simply a different view on data that is already available on a website. And every single time, the iPad app beats the web experience that has been around for years. NYTimes, Netflix, Zillow, and others.
  • To single one out, try the ABC app on iPad. Much credit to ABC, but I doubt they have the best iPad developers out there. Yet their version one application is awesome, and a much better experience than their website.
  • Thanks to better developer tools, a richer SDK, and simply higher quality standards, developers are making apps that consumers are using to interact with data in a richer way then ever before.

Browsers aren’t innovating. They are just trying to comply with standards and fix bugs and performance

  • Right now browser updates fix bugs and add application features, but can’t enhance the functionality of the web. This is only done by standards boards.
  • Browsers are forced to implement every “standard” that is agreed on, even if it’s not the best decision for the platform.
  • Browsers don’t add functionality outside of standards because developers wouldn’t utilize them. This means they can’t innovate.
  • Browsers don’t even comply with standards well. Developing for the web is a disaster because every browser has its own quirks and issues. They can’t even do one thing right.

The only way the web can survive is to reinvent itself, to refocus. Each browser should focus on innovation, not parity

  • Why do all browsers have to support the same standards? This only limits their innovation, and limits web developers.
  • Browsers should innovate as fast as possible, adding additional functionality without concern about the other browsers out there.
  • Web developers can choose which platform they want to develop for. Does your app run best using Chrome’s non standard SDK? Go for it.
  • Each browser can choose to mimic features that have been added by other browsers if they find they are losing developers or users.
  • Ultimately this will result in:
    1. Greater innovation in browsers and the web platform as a whole.
    2. Each browser will become its own platform, with varying application support.
    3. Users will choose browsers that run the applications they care about. Browsers with poor application support will die.
    4. Developers will no longer worry about running on every browser. The goal will be to create the best experience on one browser.

Developing for the web has always been a tradeoff: gaining a larger user base but sacrificing quality. The web has been improving steadily, but at a much slower pace than it should.

When GMail launched in 2004, it took one step forward and 10 steps backwards from the mail application I was using. Even today, the major features GMail is releasing are simply trying to match the features I’ve had on the desktop for years.

I think this is the tipping point for the web. The modern web had over 10 years to reach parity with desktop applications, and it couldn’t even hit that. Now it faces extinction as innovation in native applications accelerates.


You should follow me on Twitter here.

Blogger is like Windows. Tons of users, zero innovation. 3rd party developers make their products better, then people realize they just want something that works out of the box

yes, you can use all these other services and embed them into blogger, but wow, what a pain in the ass. Even as a technically savvy person, I don’t want to have to deal with youtube, flickr, and other services individually, then manually bring it all together on my blogger. In fact, that is exactly what I used to do (see and frustration in that workflow is what drove me to do something better.

What you are describing with regards to external developers sounds *exactly* like what Microsoft did. Yes, they built a product that gained a ton of market share and created a demand for other services.

Yes, lots of third part developers came to Microsoft’s rescue, building more hardware, more software, and more applications to run on Microsoft’s platform. So Microsoft could just sit back and watch the money come in.

And then what happens? People realize the experience stinks. Who cares if there are 10 word processors out there, I just want one that works. Who cares that I can buy off the shelf video cards and other components. I just want a piece of hardware that works out of the box and doesn’t crash.

Enter, Apple.

Being open is important, and we love having developers make Posterous even better. But ultimately, we want Posterous to be a one stop shop for all web publishing. No matter what your skill level, Posterous will help you publish online more easily.

Focus on the content, focus on your family’s photos, focus on your community and your comments. Don’t focus on the software or all the work it takes to get something online.

One of our users was comparing Posterous with Tumblr and Blogger. They claimed that blogger doesn’t need to innovate anymore, because they have created a market for 3rd party developers to innovate for them.

I think innovation within the product itself is still critical to its long term success. Here’s my response on that blog.