Avoid anything that requires reading more than a few paragraphs and (heaven forbid) any kind of "wizard".
On first-run, I have an assistant (Mac developer euphemism for wizard) in my app (wonderwarp.com/shovebox) and I haven't quite decided if that's a good idea. On one hand, I introduce a couple concepts, illustrate the fact that it's a menubar app, and let them configure a couple things that really ought to be configured up-front. But I think even at 4 screens, it's far too long and cumbersome.
Your empty/no content screens can have tastefully-inserted instructions on how to get started (e.g. see the arrow thingy that appears in the time-tracking app On The Job).
Brief, to-the-point screencasts and visual guides to specific features are great!
On first-run, I have an assistant (Mac developer euphemism for wizard) in my app (wonderwarp.com/shovebox) and I haven't quite decided if that's a good idea. On one hand, I introduce a couple concepts, illustrate the fact that it's a menubar app, and let them configure a couple things that really ought to be configured up-front. But I think even at 4 screens, it's far too long and cumbersome.
Your empty/no content screens can have tastefully-inserted instructions on how to get started (e.g. see the arrow thingy that appears in the time-tracking app On The Job).
Brief, to-the-point screencasts and visual guides to specific features are great!