Reposting a mobilemojitos classic from some 7 years ago, because we need some good humor these days. From Saturday Night Live, Andy Samberg proclaims, "I'm an adult!" and "My Dad's not a phone!"

So you want to launch an Android app but all you know is iOS? Follow these simple tips for the best chance of success:

Having just launched my first Android app (as both the Product Manager/Owner, and Lead Designer), I can offer these tips:

No matter who you get as your QA, Developer, Designer, etc, force everyone on the entire delivery team to switch to Android as their main phone. There is no other way you can understand the subtle differences and advantages the platform has to offer. Get them all set up with number porting or Google Voice redirects so it is the only phone they carry around, and enforce it through the v1 launch at least.

Have each person get a different TYPE of Android phone. There are so many kinds of Android devices that its tough to get the experience right for all. Everyone having a different Android will turn your entire team into a QA and you will catch alot more discrepancies. Go for the most popular phones/tablets.

Put out a call across your company for volunteers that already have Android phones (and might not be on this delivery team) and they can test too. We pay them with gift cards. Or, because of the flexibility of Android, you could run an official beta testers program for anyone out there that is interested. Strava does this well and they call it their "Early Access" program: http://engineering.strava.com/attention-android-users-3-0-early-access-is-available

Do not bother with anything before AndroidOS v4.0 (Ice Cream Sandwich). I came to this conclusion for several reasons:

- The OS was so clunky before then that just about any app had little chance at being good let alone delightful. - The phones are older and hardware is lacking (especially memory) - Ice Cream Sandwich was the first version to have native built-in screenshotting ability (the way that Apple had in since the iPhone1). This seems trivial but screenshots are the best way to communicate what you mean when it comes to those little details that have a big impact on the overall app. - By the time you launch, prior OS version and devices will be even less relevant, given the typical 2-year phone contracts people have. Come October 2013, ICS will have been out for 2 years and people will be getting shiny new (mostly) free Androids.

Handy guide for keeping the OS version numbers and names straight: http://qr.ae/TjHsf

Do not directly port your iPhone app over to Android unless you like ticking off alot of Android users. All graphical assets need to be re-designed, and many flows will need to be as well. But then you get to take advantage of each platform's advantages.

Over-invest in your app icon. It's the personal doormat to your app and people take great pride in looking at a nice icon -- it's almost like a personal gem they keep and cherish (if you do it right). Do not re-use your iOS icon with its nice rounded rectangle look. Design a similar one, but FOR the Android platform. In short, that means transparent background and as unique of a silhouette as possible (jagged edges form your shape). More info at http://developer.android.com/guide/practices/ui_guidelines/icon_design_launcher.html and http://developer.android.com/design/style/iconography.html Seems easy but so many companies get this wrong and unknowingly become the laughing stock of Android users everywhere. (http://media.tumblr.com/d39f4dab5c32f32468def861fb2dfdc3/tumblr_inline_mq41ee9udM1qz4rgp.png)

iPad Mini - One more headache for app designers?

10/23/2012 - Today Apple announced what the rumor mills have been all aflutter about, the iPad Mini (along with the iPad4 and MacBookPro 13" which is pretty mobile itself). At 7.9 inches instead of the iPad's 9.7-inch screen, its definately a "phablet" (between a phone and a tablet) that is somewhat more portable. Personally, I don't think it will be a huge seller unless the 'women carrying purses / men carrying murses' or "its cheap and I really want an iPad" segments are much bigger than imagined.

Regardless of how well it does, what does it mean for designers of apps that will now have yet another iOS device? Add one more set of icons, screen backgrounds, layout designs to the already-too-long-of-a-list?

Thankfully, no. The new iPad Mini has the same exact resolution as the iPad2 and 1 at 1024 x 768 pixels. This means there will be no extra set of design assets, although you may want to consider doing a re-layout if you have touch targets (i.e. buttons, icons, fields, or anything you are meant to touch and cause an action) at or below the minimum target guidelines according to the Apple Mobile HIG. This sometimes-recommended enlargement is because everything that you are used to seeing on the regular iPad, will now appear slightly smaller, and be slightly more difficult to tap. If you already have beefy touch targets in your iPad app, you have nothing to do here. Hooray!

iPhone5 - Tall, Dark, and Handsome

Today Tim Cook unveiled the much-awaited iPhone 5. While there are some amazing design improvements in the hardware and software, I'll focus on the one thing that will impact iOS app-designers the most: The bigger screen (and with it, the new resolution).

I am glad that Apple chose to not go the direction of all the other monstrous screens. My new Android HTC One X is great to consume on, but horrible to control--its a two-handed device when I often only have one hand available, and I simply cannot reach my thumb across the screen without dropping the phone (and I do not have small hands). I guess Apple held true to what Jobs said about valuing pocketability and 'one-handedness'. 

To balance those two traits with more screen real estate, they made it taller, by exactly one row of icons (176 pixels). This is not as nice a move for designers as when they went from the 480x320 iPhone 3GS to the 960x640 iPhone 4, exactly doubling the resoultion in both dimensions.  Now, with the iPhone 5 we have 1136x640 which is great for being able to display more content or controls, but not-so-good in that we have to now make another set of assets like background images (if you want to optimize for iPhone 5).

Nokia and Motorola unveil huge new plans, world collectively yawns

On 5 September 2012, Nokia and Motorola had large press events, showing off their upcoming new phones. No one cares, especially since they did not reveal pricing or release dates, and with the iPhone 5 announcement next week.  

Why are people so excited about the new iPhone? Marek Pawlowski puts it best in his MEX article, Nokia, Apple, experience and the near future:

"5 years after the launch of the first iPhone, products from Nokia, Samsung, Sony and LG still reflect a misunderstanding of why Apple’s product appeals. The industry employs the term ‘user experience’ more extensively today than it did then, but it still seems to refer to a collection of technologies, albeit packaged with dumbed down language, and a veneer of design tweaks to tailor for the misinformed notion of user segments.

What the iPhone does better, and the new one will do better still, is provide an experience that most of the time, for most tasks, just works. It doesn’t have the fastest processor, the largest screen or the most capable camera. Instead its style, availability, support, ability to get things done, keep users entertained and do a bit more than they did with their old phone add up to an intangible package which most users will find preferable to most competing products."

Joe Zadeh is Head of Product & Innovation at Airbnb, a community marketplace for people to list, discover, and book unique spaces around the world. He spoke (video available for Intuit insiders) at Intuit's CTOF (Create the Offering Forum) 5/2/2012 on their little-known Network Effects (i.e. more than just 'the more people that host, the more travelers are attracted and the more travelers that come to Airbnb, the more people want to host'). Their entire service helps you get more mobile (via travel) and their iPhone and Android apps are killer in terms of both design and usefulness.

I always wondered why it was called "Airbnb" and just figured it was people that fly to their destination and stay in a BnB (bed and breakfast), but its actually a story about the founders. They lived in San Francisco but they could no longer afford it.  To make the next rent payment, they setup an airbed on the floor of their living room and advertised it to designers coming into town for a huge conference.  They served breakfast too.  So Airbnb really stands for Airbed & Breakfast.

Trust and Safety are A#1 at airbnb - for example: you cannot message someone unless you have a verified phone number.  You are not renting a place from an email address, you are renting from a real person.

  Joe's three steps to make a great product:

Step 1 : Go meet you users.

Step 2 : Remove their Hurdles.

Step 3 : Connect the Dots.

  Met hosts and travellers: Whats the biggest shortage of places to stay in a city in the US? Austin, Texas during South by Southwest.  So they went there and learned. 

Hurdle: It's awkward to exchange money with a stranger after they stay at your house.  "Yes, I had a great time meeting and hosting you here this weekend....now...uhh, could you give me the money?"  They saw this as a big enough that it would prevent adoption.

Connecting Dots: So lets automate payments.  

Hurdle:  Hosts worry that their place will be trashed or items stolen.

Connecting Dots:  Airbnb has a guaranteed $50,000 theft or vandalism coverage now.

Hurdle:  Online reviews are not trusted. Anyone can go on Yelp and berate a restaurant or make it sound much better than it is. And forget about hotels and their reviews on their own sites or on something like tripadvisor--they fall in the same untrusted category.

Connecting Dots:  Each of the reviews on Airbnb is tied to a financial transaction, so you can only flame/praise if you have hosted that person or stayed at the host's place.  This ensures no fake reviews.

Users can help break down your mental walls:  For Airbnb, that meant changing their view that it was only for use during conferences (when places to stay are scarce), or only for sharing a place (you can now list your entire place while you are out of town).

They were thinking that if only the pictures of each listing looked better, more people would book. So in true Lean Startup fashion, they built a concierge MVP (minimum viable product that uses human effort and little to no code) to test the hypothesis: Will hosts want pro photography?

Sending emails to hosts of listings with regular pics, they found that just about everyone replied with a "Yes, Please!" when Airbnb offered to send a professional photographer to their place.

For their second hypothesis, Will they get more business? they used metrics to track pro-photo listings vs. regular-photo listings.  The answer was an astounding YES.

They continued sending emails and offering to pay for pro photography for hosts and business was growing, growing, growing.  Then it stalled and went down/flat.

Joe recommends every team build a dashboard!  It lets you measure and find out why stuff happens.  So they found that the reason for the down/flat trend was because their employee that was in charge of cutting checks to professional photographers was just overwhelmed and getting behind.  They thought, instead of cutting checks manually to pro photographers, who do they know that has an automatic payment system?  Thats right, they already had it in-house, and just applied it to their photography program.

What started as a bad photo, the resolution wound up fixing many hurdles and encouraging their stratospheric growth.

Try things that don't scale!

  Hurdle: Guests want to see complete guest profiles of the Hosts; Hosts don't want to fill them out.

Removed this hurdle by auto-connecting with Facebook: Hence was born Airbnb Social Connections. Try it, its quite amazing!

Build dogfooding into your culture.

Eat your own dogfood to the extreme: One of the co-founders went homeless and only sleeps at places he books on Airbnb. He has been doing this since June of 2010!

Eric Ries, author of The Lean Startup, spoke at Intuit at the 1/23/2012 Delight Forum. If you work at Intuit, watch the video replay (sorry, not available outside our firewall). Here are some takeaways. The mobile product team I work on has implemented some already, others are on the docket. All are amazing and the man speaks the truth. Wired also had a recent article on Eric's talk at Intuit.

Eric defines a startup as “a human institution designed to create something new under conditions of extreme uncertainty.”  That’s pretty much everyone out there, not just those small companies so commonly associated with a startup. As he put it, "who feels like the world is getting more and more stable every day!?"

Nowadays, "we can build anything we can imagine. The question of our time is not can it be built, but should it be built?"

Entrepreneurs are typically obsessed with the length of the runway, but in the wrong way: how much time until we run out of money.  Instead, we should look at it as how many times we can pivot and learn.

Code not to ship products; code to learn.

A software company is really just about transforming ideas into code.  Then measuring data, and learning from it, which influences our next stage of ideas.

Agile and Lean are supposed to drive out the waste from his development process, yet Eric committed the biggest waste of all: building something nobody wants.

3 Learning Milestones:

Establish the baseline - Build an MVP (Minimum Viable Product) and measure customer behavior. (e.g. The Leap of Faith assumption is the % of customers that will sign up for the new trial

Tune the engine - Experiment to improve metrics towards ideal.

Pivot or persevere - Got diminishing returns in your experiments? Time to pivot

  Case studies / real-time coaching:

Problem 1: After swiping a credit card, it takes 2-3 days for it to show up in your bank account, leading to alot of confusion & wondering.

Leap of Faith: Sign-up rate of merchants will double if they know they will get their money sooner.

Eric's take:  "What if we did a split test and just told some people [when they are signing up] that they would get instant settlement?"

The product team: "And...?"

Eric: "And they didn't."

(Audience chuckles but then realizes it's actually pretty smart and cheap)

There are alot of reasons to NOT do this, but Eric addressed each:

Pissing off customers:  Just limit it to a small number of customers.  If they get pissed, we know we were right.  Having pissed off customers is actually one of the best things! It means:

We know to find them 

We got them to try your thing

They actually wanted it

We're in sync with them on what the key features are 

They cared enough to yell at you!

Just do not be deceptive about it.  The product team should commit to taking all phone calls, apologizing to any upset customers, etc.  Make it right for them.

What about letting the cat out of the bag and competitors one-up us?  

If you expose only a small number of people, the odds are astronomically high that a product manager at a competitor is NOT going to be one of them.

Most customers don't care enough to instantly blog about some new feature/product.

On the landing page, there is just a bullet list of features and we are adding one new bullet.  It's almost no change and tough to notice.

OR decide to do it under a separate brand name if the above still is too risky.

"If I went to the competitor's office and I looked at their road map, I bet you a million dollars this is on their roadmap somewhere. They are probably thinking about doing it. They are probably having the same problem that we all have--they've got a million good ideas and they can't figure out how to prioritize them. It's not like knowing that you are doing it gives them any information."

"You are in a battle to out-learn your competition. If you go through the Build-Measure-Learn loop faster than them, it doesn't matter what they know and this is not a big deal. If you are NOT faster than them, you deserve to get beaten."

  Problem 2: More new Mint users than we'd like are not sticking with it.

Measurment of success:

Total and % of offering clicks, engagement

Number who switch banks.

Long term engagement (frequency of use, explore offers)

Eric's take: Just take a small subset of Mint customers, and tell them you can get them a better bank account (even if you can't). Right in the beginning. I think it will actually cause more users to leave than stay (because I hate when someone tells me to switch bank accounts). But lets see...

  Problem 3: Need more invoicers (small businesses that get paid via invoices). When customer gets an invoice, they can click a link and pay with a credit card (3.25%) or bank-to-bank ACH (50cents, yes really its 50cents only).

Measurements of success:

Number of invoicers who sign up (growth)

Net-Promoter Score

Referrals

Eric's take: Value Hypothesis this is not; this is Growth Hypothesis.  He believes in the law of sustainable growth (not publicity stunts) New customers come from one of the 3 engines of growth:

Paid (Revenue earned from past customers invested in getting new customers)

Viral (Customers act of infection, not "word of mouth" but they cannot help but to become infected).  For each customer you sign up, how many additional customers do they get to sign up?

Sticky/Engagement (you are addicted, you can't quit). Word of mouth works in these types of deals.

Use Google AdWords to find out the lifetime value of each customer.

Exciting: pick one engine of growth, then brainstorm on what experiments could prove that this move is worth it.

  Problem 4: Bank Services make offerings that it sells to banks who use it with their customers. But micro-small businesses are the majority and don't want the normal offerings--too big and complex. Will they abandon Excel and paper and pay for our stripped-down offering?

Measures of success:

Active and on-going use - will measure weekly active use.

Small business auto-categorization works - percent new categories after 30 days of use

Make the product better and make sure its actually getting better using cohort analysis:  Did the 100 customers that came to the website after the most recent changes actually use it more (or rate it higher, etc).

Vanity metric: number of users.  But if you spend alot of time adding a feature and you just look at your total number of users, sure it went up.  But really what happened is you made a change in the code with no customer benefit.  Rip it out!

A pivot is a change in strategy without a change in vision.

You cannot "pivot the vision." That is incoherent.  Some Common Myths about The Lean Startup method:

Lean means cheap.  Truth: its not about cost, its about speed.

Its a web/internet/consumer software companies. All companies that face uncertainty

Lean Startups are small bootstrapped startups.  Truth: driven by a compelling vision and rigor about testing each element of this vision.

  More favorite quotes from Eric Ries and Scott Cook:

"In every one of your businesses, I know a scrappy little team in a garage somewhere that is gunning for you and wants you dead!"

"'Are you better at this than you were before?' is all that matters."

[making things more complicated with no benefit] "Thats not a pivot, thats just... DUH!"

Continued from Part 1 of my notes from a BayCHI talk given by Brennan Browne, a UX researcher at AnswerLab. Brennan presented the pros/cons of different techniques used for capturing mobile phone/tablet user research sessions.

Screen Captures (video recording straight off of the device)

Pros: best image quality, portable, cheap

Cons: doesn’t work well with all devices (earlier iPhones can’t use this without jail breaking), doesn’t capture physical interactions w/ device, passwords/sensitive info can’t be hidden

Video (filming the screen)

Tips: 

equipment is expensive so consider demos or rentals

define a hotzone to the user (ex: put a piece of paper down on the table and ask user to keep the device over it)

be aware of room lighting/glare

A. Videographer

Pros: works for any mobile device, can capture physical interactions, flexible and portable

Cons: cost (need to bring an extra person to the session), screen may be difficult to see, may have to ask user to move around, lighting

B. Sled - camera structure that attaches to the device (ex: Noldus)

Pros: fixed, hi-res screen, captures physical interactions, no videographer required, very portable

Cons: won’t work with all devices, limits users ability to switch orientations or use slide out key boards, adds weight to the device, hard for participants to hide passwords or sensitive info

C. Document Camera - looks much like an old overhead projector

Pros: can capture device at any orientation, captures physical interactions, high res camera, no videographer needed, camera itself reminds users where to hold the device, can easily enter passwords/sensitive info by removing device from the recording area

Cons: price (>$7K), screen quality isn’t as good as a screen cap, not well suited for field studies

On a personal note, we’ve tried several of these methods in our iPhone usability studies and I very much prefer Screen Cap over Video. When we used a Noldus camera, we found that users were very hesitant to pick up with the device and interact as they normally would in real life. Instead they’d put the device down on the table and poke at it from afar. When we started running tests using Screen Cap (thanks to iPhone 4S/iPad 2 mirroring), we found that users felt more free to bring the device closer to their face, use gestures outside of “tap”, and rotate into landscape mode. Although we aren’t able to capture the user’s gestures on film, we take notes about interesting/surprising gestures to augment our notes.

Part 1 of my notes from a BayCHI talk given by Brennan Browne, a UX researcher at AnswerLab.

Trend 1 - Trading computer time for tablet time

Why? It’s more fun, easy, convenient.

Computer: in the home office vs. Tablet: comes everywhere

Tablets are portable, not necessarily mobile - possibly because need wifi (not all are 3G enabled)

Over past 6 months, see trend of more people using tablet at work - more employers are handing them out, there are more biz-related apps available

People are afraid of taking iPad outside of home, Starbucks, work, or other places where they feel safe (i.e. not public transit) because they fear theft

Choice of device to use isn’t based on where user is— it’s about what user wants to do. 

Phone: quickly checking something

Tablet: immersive - plan to sit down with for a longer period of time

Computer: for tasks that require more management/multitasking/typing

People prefer typing on everything (i.e. phone, computer) except a tablet

Did see people using bluetooth keyboards primarily if they’re trying to replace their computer with an iPad (although would still often have to turn back to a computer for other reasons)

Whichever device is most convenient at the time will often be the one they choose to use. For example, they might pull their phone out of their pocket while on the couch, rather than getting up to grab a computer from another room.

Trend 2: The tablet and shared experiences

Tablet is commonly shared amongst family members

In the past 3 months more common to have multiple iPads within a house— “I got tired to sharing it so I got everyone in my house one”— much like what happened when computers were growing in popularity

Shared nature can lead to some problems because no built in multiuser support in iPad & very limited in Android. Puts the responsibility for multi-account support on the app developer

Facebook tries to support this (to view this, sign out of the FB iPad app and see ability to create other accounts)

Trend 3: Apps vs Web

Many users are content to use the web on iPad - they expect to be able to access the full version of the website and to have the same level of functionality that they would have from the computer

Example of a bad app: Target (users felt they were being forced to leave the app to view product details on the website which broke their experience - “what’s the point of even using the app?”)

Example of a good app: Zappos (users get full functionality of the website, plus ability to interact with pictures, better shopping cart experience, etc.)

Best Practice: give lightweight help to users during their first use experience, then make help content available (but not in their face) going forward

Best Practice: use universal app instead of having a separate iPhone/iPad app if possible or users might not realize that you have a different version of the app in the App Store

Best Practice: website interrupts that alert you that an app is available is fine unless it impedes the web experience (ex: people were frustrated by Yelp which asks them to download the app each time they visit the website). Using a banner or sending an email may be even more preferable.

People generally update their apps within a month

See lots of people syncing their iPads to computer, but it’s not as common as syncing their smartphone

Did observe some users saving websites to their home screens, but these were generally more tech-savvy users or those who didn’t care for apps

Saw a mix of people who did/didn’t want push notifications. Best Practice: don’t ask users whether they want to accept push notifications until they’ve spent some time within the app and have an idea of how/why notifications might be useful to them

Overall Design Recommendations

1. Design for a “small laptop”, not a “big phone”

Create fast, intuitive, full featured experiences that are fun to use and better than the web

2. Full web

People expect a full website when browsing on the iPad browser, so ensure your site is optimized to deliver a great experience. 

Ex: use HTML5 to customize the keyboard when typing in a datafield

3. Content over context

Location-specific experiences that are king on smartphones may not be as important on tablets because they aren’t necessarily being brought everywhere

Instead, focus on rich content and superb UI (especially taking advantage of video & photo)

4. Shared device

Consider social nature of the device when design log in components, how data is stored, and anything involving transactions/ecommerce

Ex: Amazon app allows users to view recommendations/watch list without signing in, but user is prompted for password when making a purchase

5. Security fears

People have no clue about security on a tablet. In all of their testing, they’ve never seen someone who’s set up a passcode on the iPad. The people who are the most tech savvy are the least afraid of security risks… but non-savvy users are more afraid about persistent log in and entering credit card info and will sometimes go back to a computer when they’re required to input credit card credentials

Tip: reassure users that the privacy/security of your app/website on the iPad are the same as what they’ll find on the computer

In part 2 of this post, I’ll summarize Brennan’s recommendations regarding smartphone/tablet usability testing.

Posted from: TX, USA

At SXSW Interactive 2012, I attended the last-minute session with Kevin Systrom and Mike Krieger, Founders of Instagram.

from http://instagr.am/p/IC84fJzYNZ

Background:

Mike + Kevin + Alexia Tsotsis of TechCrunch

The talk was not even on the schedule, they came in when Caterina Fake (of Flickr and Hunch fame) cancelled last minute.

Announced the Android version will finally be available "soon" (to much applause) and they had a "highly polished prototype" working on their Android. So far, Instagram has been iPhone-only.

They are excited to get to Android because they know that more users = better experience. 

Takeaways on the Instagram session:

They are the fastest growing thing EVER, period.  Faster than Facebook, telephones, iPods, etc.  Since their launch 1.5yrs ago, they now stand at 27M users.

Within a few hours of launching, they had 10,000 users. Clearly they were on to something.

End of day 1, they had 25,000 users!

Being named the iPhone "App of the Year" at the end of 2011 was a surprise (having so many rabid users obviously helped)

Kevin was approached by Best Buy to be featured in their SuperBowl commercial.  The most expensive ad in the world they got for free! 

Kevin appeared in the ad and had to say "I created Instagram...." He was uncomfortable about this and ran it past Mike because he really didn't want to take all the credit. "Dude, its the SuperBowl, do it." --Mike

Kevin's original app was called Burbn and it was an HTML5 mobile web app that let you: Check in to locations, Make plans, earn points, post pictures, and much more.

Mike was one of the first users and very passionate about it. They partnered up and became co-founders.

Saw photos as the one area of Burbn that was widely used. 

Spent a week prototyping a version that focused solely on photos. It was pretty awful so... 

Went back to making Burbn, but as a native iPhone app this time.

Finished it, but felt cluttered and overrun with features, so they never launched it.

Cut everything in the Burbn app except for its photo, comment, and liking capabilities.What remained was Instagram.

QR (Quick Response) Codes have become the norm for connecting the real, physical world with the virtual.  Scan in a code using your smartphone, and it takes you wherever the poster wishes.  But they are so ugly and make you feel like you are staring right into a computer's empty eyes.  So here is a collection of the most stunning QR codes I have seen.

They are courtesy of their creators, namely: Angry Birds (Rovio), C21, LA Tourism Bureau, SET/Help Japan, Louis Vuitton, Yellow Pages, and a plain old regular one so you can see how far the beautification has taken the others.

Why Twitter is Better at Online Identity (I am talking to you Facebook and G+)

This inspiring article on Wired about Christoper Poole's stance on privacy pretty much hits the nail on the head for how I feel. Poole is the guy that started 4chan at age 15, and Canvas, both of which branded him as the godfather of anonimity.  But it could not be further from the truth--he says it's not as much about "who you share with, its about who you share as."  

Siri Could Spell the End of Google's Run

I saw today (thanks Natalya) that Forbes is predicting that in 2 years time, Apple's Siri will mature to a point where almost every task will be done through it, and all searches on mobile will use it. Having worked in the VUI (Voice User Interface) industry a good 10 years ago, I couldn't agree more.  What we had back then (the systems that still run on most "phone trees") was pitiful compared to Siri.

What's that, death to traditional search?  Clearly that will put a huge damper on Google's business. They are fighting back with Android and doing OK, but when I hear that Eric Schmidt is not worried one bit about Siri, I can only see disaster for them.

Even before Siri was available on the iPhone 4S, fully integrated into the OS, I was thinking that Apple's app model was a Google-killer.  Its a bit older (early 2010), but still very much true:

"Google’s insurmountable challenge is that the habits of mobile device users are evolving and moving rapidly away from traditional search. ... The successful Apple app is essentially a tiny search engine in a box. It allows the user to efficiently manage their time by preselecting well-reviewed apps based on their interests. Google search may be able to take users to the same place that an app can, but the route will be longer and more uncertain. An iPhone loaded with two dozen apps carefully selected by the user eliminates Google as the primary middleman between the user’s search and their destination."

--from How Apple Killed the Future of Search 

Droid Bionic Brings Back the Old Cameraphone Days

Remember when putting a phone into a camera seemed stupid? Everyone called it the dumbest combo ever. And for some time, cameras in phones sucked. They sucked bad. No more. Turned out the best part of phones with cameras is that you have it with you everywhere. But what good is always having a great-photo-taking camera everywhere if you can't get capture the action fast enough?

I thought this slide was the most important of the recent iPhone 4S event--time to first shot, and shot-to-shot times really impact the usefulness and experience of your cameraphone! When Droid Bionic users want to take a picture, do they just say to themselves, "whatever, I will get the shot next time" and grab a coffee while they wait for it to start up!?

Kevin Kelly & What Technology Wants

I attended a talk today by Kevin Kelly, the founding editor of Wired Magazine, at the Creative Good Councils Summit in San Francisco. The guy is amazing and kk.org never fails to amaze me.  

Kevin gave us a glimpse of the future which is already begun, through the lens of what we are moving from --> to. Below are my takeaways, much of which directly relate to mobile, or are a supporting function of our mobile future:

Me --> We

Social is the future

"We" does not just include us (people), but also our devices and connected objects

Ownership --> Access

Think Netflix, Zipcar, Spotify. 

Amazon will just charge a fee for access to the reviews, but access to every book in th world will be free. 

The burdens of owning something now outweigh the burden of accesssing something. Just-in-time buying.

Goods --> Experience

iPhone 4S with Siri takes more inputs (voice).

Spectacles (glasses) with overlay.

If there is a camera on your device, its watching you as much as you are watching it.  It can tell and adapt to your feelings.

Better --> Different

Different is actually better than better.

Being different is a bigger challenge and more valuable than ever before.

Because the world is changing so fast now, we are in a "Rugged Landscape" so you cannot just optimize anymore.

You have to get on a different peak, by devolving (going down) what you have.

The innovators Dillemma

Today --> Now

Its instantaneous, think Twitter

If its not in real time, it doesn't count

Webpages are no longer the center, Streams are.  RSS, Twitter, Facebook, News feeds, Netflix streaming, Hulu

Always on.

Consume --> Create

Consumers are not going away, but the surprise is that consumers creating things was the main event.

User-generated content. The fact that we are co-creating with our customers. Kickstart is phenomenal.  Designing, building, marking, supporting is all done by the edges.

Google caters to the alpha-geeks, but adapts for the masses. If you have conflicting business models or cannibilization, that's a good sign you are living on the edge.

The Mac was a complete skunkworx, off the side of the main Apple business: Lisa.

YouTube -- every TV exec in the 1990s told Kevin there is NO WAY anyone will get off the couch and make movies. Categorically wrong.

Fab. People dismiss making of physical goods as a toy/hobby like

Community precedes commerce.

Stability --> Mobility

Explore in all dimensions, not just walking around with a device in our pocket.

Pervasive computing, evasive computing

How much do we want to carry around with us anyway

The tshirt has a chip in it, so do all the washing machines, which can report back fabric breakdown and the network learns.

Curation --> Choice

The real frontier is trying new ways to handle the explosion of choices we now have.

Help manage the choices.

Networks help to expand choices.

Art --> Data

Lots of business were run on hunches, now they run on data

Huge oceans of data are being generated.

The opportunity is for companies that make sense of all that data.

The Quantified Self, a way to self-track everything. Not survelliance.

The database of things is expanding 10X every year.

The main event?  That YOU ARE NOT LATE!  --kk[at]kk[dot]org 

In honor of the man that changed the face of mobile forever (among other things), who passed away last night Wed 5 October 2011, here are some of the most creative memorials to Steve Jobs:

Images are copyright of their respective creators.

The guy did actually put a dent in the universe, using his natural visionary leadership that he somehow was also able to bring to fruition, in the market, so that we could all enjoy it.  He was an inspiration to me and his products continue to inspire my designs each day.  He said it best:

“Most people make the mistake of thinking design is what it looks like....People think it’s this veneer, that the designers are handed this box and told, ‘Make it look good!’ That’s not what we think design is. It’s not just what it looks like and feels like. Design is how it works.”

HP placed its bets on PCs, now mobile is killing them

Great post by Adam Hartung, of The Phoenix Principal on why HP is in trouble. Having worked there in the past, I know it all too well.

"Mr. Apotheker [recently fired HP CEO] and Carol Bartz, recently fired CEO of Yahoo, made similar mistakes.  They relied heavily on their personal past when taking leadership of a struggling enterprise. They looked to their personal success formulas - what had worked for them in the past - when setting their plans for their new companies.  Unfortunately, what worked in the past rarely works in the future, because markets shift. "