- The user isn’t the product being sold. The user is the customer.
- Startups become big by empowering their customers with great products and services that allow them to do things that were previously difficult or impossible.
- A company is a group of people with a shared goal.
- Everyone deserves a chance to make progress on meaningful work.
- Stay hungry. Stay foolish.
- You aren’t Steve Jobs, so don’t be a jerk.
- Meetings are toxic, but necessary. Manage them in a constructive way.
- Everything is a conversation.
- Everyone must bring something to the table. There is no room for “ideas guys”.
- Businesses make money.
Steve Jobs sold the idea that the computer, formerly just a business machine, is a tool for artists and dreamers. In doing so, he captured the imagination of the world.
He didn’t personally invent the computer, or (as ReadWriteWeb points out) anything; but he understood that if computers were to become integral to our lives, they needed to be more than commodity objects. Apple remains the only company that really successfully considers the emotional design of a product.
To put it another way, Steve Jobs humanized computers, and his legacy is that they are more emotionally accessible, they’re better designed, and they empower anyone who creates in a way that they might not otherwise have done. And he did it in a way that made a product launch feel like a life-changing event.
As Om Malik says, our Elvis is dead. He will be sorely missed.
Ebooks don’t cut it: everyone wants an app
NB (May 20, 2010): A lot of my suggestions for web-based apps are part of the Google Chrome Web App Store. In fact, the .crx file used there is a zip file with very similar characteristics to epub. (I assume, as Chromium is open source, that .crx files are also open source – so the web app store is not limited to Google.) This post can be reread as an argument for building for the Web App Store.
At Intersection: Publishing in London the other week, there was a lot of discussion from publishers looking at mobile apps as their mobile publishing solution. Rather than creating ebooks, there seemed to be a general feeling that dedicated applications presented more of an opportunity for richer content, while closing the door to pirates and ensuring that publications remained a paid commodity.
The piracy argument is kind of spurious: although app stores tend to be locked down, this presents a false security blanket for publishers. It only takes one person to crack a store for piracy to be generally possible; technology only ever becomes less secure over time. A cynical person might suggest that the piracy argument is largely spread by the people who own the app stores or provide related services. The people who will suffer are authors and publishers.
Why apps rock
However, there’s definitely an argument for using apps – not just for publishers, but for anyone who wants to create dynamic content. Anyone who’s ever owned an iPhone will tell you that native applications can still provide a smoother, more consistent experience than a web app, without the hassle of remembering website addresses or waiting for pages to load. Tweetie is a million miles better than Twitter’s mobile website – something they themselves acknowledged when they acquired the iPhone application last month.
Above, mobile Twitter is on the left; Tweetie is on the right.
- The app doesn’t need to load its interface from the web; only the underlying data is downloaded, meaning the app can appear instantaneously, loads data faster, and provides a better user experience.
- The mobile web app needs to sit within the browser chrome (URL and search boxes, browser buttons on the bottom, and in my case, a debug toolbar). The app, on the other hand, has a full-screen UI dedicated to Twitter.
Why the web rocks
The mobile landscape right now is a bit like the personal computing landscape circa 1985. There are a bunch of different platforms to code for:
- Apple iPhone and iPad
- Windows Phone
- WebOS (now more important in the wake of HP’s acquisition)
However, each of these platforms have one thing in common: they support the web.
HTML5 and ePub: a new platform for apps
As you’re probably aware already, the upcoming HTML5 standard revises the web platform to become far more suitable for apps. Improvements include:
- Methods for offline and cached usage (so interfaces can load immediately)
- Built-in databases and storage (so web pages can natively store their own data)
- A paintable canvas element and WebGL 3D graphics functionality (so web pages can display interfaces more like real applications; the 3D shooter Quake II has already been ported to native HTML)
- Native video and audio support (no Flash required)
- Websockets (a more efficient way to connect to Internet data from web pages)
- Built-in support for advanced functionality like geolocation
This is a big deal. Compliant browsers like Firefox, Safari, Chrome and even the upcoming Microsoft Internet Explorer 9 will be able to run applications that look and feel like native software but are powered by web standards. Between those browser engines, that’s most of the mobile platforms covered: those that don’t have an HTML5 browser built in by default should have one available to download. What’s more, both Firefox’s Gecko HTML rendering engine and the WebKit engine that powers both Chrome and Safari are open source, so anyone can pick them up and build software around them.
So sites on the wider web can be more like applications. That’s fantastic news in itself, but what about the app store model? A lot of people depend on that for revenue, and there’s no reason why that should be incompatible with using web standards.
Luckily, it turns out that ePub – the ebook standard – is really just a bunch of XHTML 1.1 pages drawn together in a specialized way and bundled up in a modified zip file. There are already established best practices for buying and selling ebooks.
If the ePub standard was updated to allow HTML5, it would evolve into a format for self-contained, multi-platform apps that could be sold in the same way as ebooks, music, videos, or apps in something like the iTunes App Store. Except app publishers would only need to build once to support many different kinds of mobile platform, thereby reducing the barrier to entry and allowing their budgets to be concentrated on building just one really awesome piece of software instead of spread across multiple devices.
This would be in a lot of peoples’ interests: app publishers, device manufacturers, browser vendors and consumers alike. There’s a lot of money tied up in a venture like this. The only question is, will the International Digital Publishing Forum, which controls the ePub standard, be foresighted enough to see this opportunity?
Update: Steve Jobs weighs in
Apple’s CEO has written a little about why HTML5 is the future of mobile apps (albeit in the context of his platform’s refusal to support Flash):
HTML5, the new web standard that has been adopted by Apple, Google and many others, lets web developers create advanced graphics, typography, animations and transitions without relying on third party browser plug-ins (like Flash). HTML5 is completely open and controlled by a standards committee, of which Apple is a member.
[…] Flash was created during the PC era – for PCs and mice. Flash is a successful business for Adobe, and we can understand why they want to push it beyond PCs. But the mobile era is about low power devices, touch interfaces and open web standards – all areas where Flash falls short.
[…] New open standards created in the mobile era, such as HTML5, will win on mobile devices (and PCs too). Perhaps Adobe should focus more on creating great HTML5 tools for the future, and less on criticizing Apple for leaving the past behind.
Make no mistake: HTML5 is the platform to bet on.