01 January 2012

Creating Good Slides


I've been to lots of conferences, so I've seen lots of good presentations and lots of bad ones. I hope to see more good presentations, and since slides can make or break a presentation, I've put together a few rules for creating good slides.

Each slide should contain less than 10 words. I sort of arbitrarily picked 10 (actually, I arbitrarily picked 20 first, but that seemed way too high), but the point is this: keep the text on the slides to a bare minimum. If I want to read what you have to say, I'll find your blog or a book you wrote. I'm not sure I can emphasize this enough - keep text on your slides to a bare minimum so the audience can listen to you, rather than reading your slides.

Use text that has a high contrast with its background. This is easy enough if your slide uses a solid background. Where I often see issues is on slides that use an image for the background. Often I see dark text on a dark part of the image. This is easy to resolve - just use light text instead, or move the dark text to a light part of the background. Just make your text is readable from the back of the room. If it's not, it's either too small or doesn't contrast enough with its background. Remember that your text is going to look much less readable on a projector in the presentation room than it does on your LCD, so err on the side of more contrast.

Use REALLY BIG fonts. Like I said in the last point, it needs to be readable from the back of the room. This probably means at least 60 points for ALL fonts, and maybe more. Using a REALLY BIG font also helps to ensure you don't put too much text on the slide, as stated previously. Keep it short & simple.

So keep your slides short, use lots of contrast, and use REALLY BIG fonts. Your audience will appreciate it, and you'll get compliments on your slide design, even if you think it's nothing spectacular.

16 December 2011

iFonts 1.5 released with VoiceOver support

Hey, folks - iFonts 1.5 was just released with support for VoiceOver. This version also includes UI improvements on the about screen. If you don't already have an awesome app to display (and email!) all of the fonts included in iOS, get it on the App Store.

14 December 2011

Learn Thai Squiggles 1.1 released!

The best app for learning the Thai alphabet on your iPhone now has two vowels! Master the consonants and start learning the vowels with version 1.1 of Learn Thai Squiggles. Get it on the App Store.

13 October 2011

New fonts in iOS 5

iOS 5 introduces new fonts for iPhone, which now includes Papyrus, Gill Sans, additions to the Helvetica family, and more. Check them out with iFonts.

06 October 2011

Thanks, Steve

I love my job. I love writing apps for the best mobile operating system on the planet.

I have the privilege of doing what I love thanks to Steve Jobs. I write iOS apps for devices he invented. I do this on a MacBook Pro that he invented. I talk with clients on the iPhone he invented. And I really enjoy it.

Thanks, Steve, for making my job fun.

Mac App Store & Xcode

I'm really glad Apple put Xcode in the Mac App Store. I like getting delta updates for such a huge app.

I'd like it even more if Apple created a place in the Mac App Store for registered iOS developers where we could get delta updates for betas from the App Store as soon as they're released, rather than downloading another 2GB installer. The App Store has all the information it needs - you sign in with your Apple ID, which is what identifies you as a developer. Aside from being more convenient for developers, this would take some of the load off Apple's servers, too, right?

And while we're on the subject of being a developer - I'd like to be able to search iTunes any time for developer-only content, like the WWDC videos. Same applies here - I'm already signed in to iTunes with my Apple ID which is also my developer account, so they know I'm a developer. So why can't I just search for developer content?

Someday, maybe. Someday.

11 August 2011

Core Data - Getting more from your errors

Great answer on Stack Overflow about getting more information from your Core Data errors.