This is a guest post by Ryan Spoon (@ryanspoon), a principal at Polaris Ventures. Read more about Ryan on his blog at ryanspoon.com.
As an investor, I’ve seen hundreds of mobile application pitches. And as a consumer, I’ve downloaded hundreds more – some out of curiosity and others in the hope that I’ll find something so useful and exciting that I’ll make room for it on my iPhone’s home screen.
From both perspectives, I am rarely excited by download numbers. What gets my attention is engagement: how frequently an application is used and how engaged those users are. This ultimately is the barometer for an application’s utility and/or strength of community. And if either of those two factors are strong, growth will certainly come. Just ask Instagram, Evernote, LogMeIn and others.
Creating great mobile experiences requires dedication to building product specifically for mobile. It sounds obvious, but it’s so often overlooked. Mobile users have different needs, desires and environments; and as the application creator, you have different opportunities to create utility and engagement. With that in mind – and with the help of my former eBay colleague and Dogpatch Labs resident, Rob Abbott (founder of EGG HAUS and Critiq), we’ve put together 7 design guidelines to consider when building for mobile.
Just like the presentations on leveraging Facebook (both on-Facebook.com and off-Facebook) and Twitter, success comes from building meaningful experiences that are honest to the native environments.
Facebook has just 
My set ritual before going to bed each night is as follows — turn out the lights, plug in my iPhone, take off my glasses and attempt vainly to nod off. Step two in that process can be a bit of a crapshoot in the dark, but the folks at 
