Mobile

• http://www.internetlivestats.com/internet-users/
• 44 million in the first internet bubble
• 3 billion now
• where is that growth coming from?

• China near the bottom!
• So much potential growth in the areas that are already surpassing US in raw numbers

• Mobile can be where you are
• Often is where you are
• Delivered to you, not your house, not your work

• Location
• Time (now)
• Movement
• Mode

• $14 Billion in revenue, mostly from Yellowpages and Newspapers
• Where's that money going?
• Not just mobile ad, but Internet advertising in general

• phones are cheaper, easier to keep on your person
• essential for communicating

• location and timeliness

• Trend is obviously toward mobile, but not majority yet: shoot there
• Keep a fresh outlook, and go 100% toward what you believe
• Bigger companies need to "invest": be sure where a technology will end up before the do something about it.
• Small companies can try things out, ditch what doesn't work (risky!)

• 2:30 Privacy
• You may not agree with this statement, but you need to be doing stuff bigger companies are uncomfortable with
• Web Architecture helps you here: no one has to approve your idea (you can fail without a net or ceiling)
• Another example is iPod: evaluate what buttons you need, get rid of the rest, use technology to support your idea

• OS sites on top of hardware
• Libraries are used by any higher level for common functionality
• Services similar to libraries, but they "run" on their own, can contact external services
• UI Widgets are things like buttons, drop downs
• Apps written to use libraries and services
• Browsers special apps that essentially can download and run other (web) apps

• Directly control UI, make use of phone's specific services
• OTOH, must directly control UI, make use of the specific services for each phone you want to support
• Marketplace for downloads

• Rotation
• Compass
• Gyroscope
• Services (contacts)

• Still have to test across devices
• Constraints are changing, technology like "canvas" allows arbitrary drawings
• Performance trade-off: must rely on browser's ability to render efficiently, can't update it for your app.

• The mobile web is still the web
• Uses all the same technologies, in the same ways
• Mobile browser still a browser, with DOM, JS, etc.

• Much less variance between CSS, javascript support
• Means you can push HTML5 to its limits
• Geolocation
• Screen size, multitouch, finger "presses"

• Write HTML5, Javascript, framework will render it for you
• Use javascript to call platform specific abilities

• If you're a new project/company, mobile is your edge
• So focus on your edge, build mobile first
• Alternative is to make your desktop app, then simplify it for mobile

• Just because you can display the desktop version doesn't mean you should
• Even if you reflow the content, the usage case of mobile may be so

different you don't want to share HTML

• Focus
• Simplicity
• Beauty

• Focus on searching now and near
• remove elements you're less likely to do, such as write a review or read

random reviews

• Need some story around desktop
• New platform to learn
• Limits experience

• Now you have to test all desktop browsers, too?
• Not many folks experienced with mobile development
• Are you editing photos? Writing code? Maybe you just can't do that on a small screen (though I'd still try designing for a tablet)

• Make it so easy to use, people start using it by accident