Drawing Inspiration

Today I pulled out a blank sheet of paper and a pencil and started designing a user experience.  Some people might say I'm putting the cart before the horse here, thinking about UI and process flow before I've created a data model or class diagrams.  To those naysayers, I say: nay!  How do you like that?!  

This process is not only an extremely useful lead-in to those other design exercises, but it's also a perfect opportunity to refine our requirements.  Plus, sitting down and imagining what users will actually see (and touch) when they use the app is a great way to get motivated. 

So let's look at what I've got here.

The Name Game

Naming stuff is hard.  If you're like me, you can't start an RPG until you've stared at the "name" input on the character creator for at least an hour.  We've got to call this app something.  I managed to name two actual humans, so how bad can this be?  

Today, we're going to talk naming strategies and App Store Optimization -- how to tailor your name to get the most out of App Store search results.

Whatever Scopes Your Boat

Before you can build something, you have to know what you're going to build.  This is obvious and hardly bears saying out loud, but it doesn't mean I've never fired up an editor and started coding with only the vaguest semblance of a plan.

For this app, and specially for this blog, I want to be a lot more deliberate.  We're going to follow the software development life cycle, and that means defining our scope by doing some requirements gathering.

These boats appear to be floating.  And come to think of it, probably are.

Inception

I'm going to build an app.  Specifically, an iOS app.  This process will be my way of reacquainting myself with iOS programming and learning Swift, setting me up to teach mobile development for Notre Dame this spring.  So I'm going to build an app, and if you want, you can follow me as I go.

If I look half as cool as this kid by the time I'm done, I've won

I've spent the last four years teaching Android; iPhone development has been an afterthought.  At some point I dabbled in Objective-C and even published to the App Store, but still, it's been a while since I worked with iOS.  Since then, Apple has released three major versions of their operating system, introduced heterogeneous screen sizes, and created an entirely new programming language for developers to use.  I guess there's a watch now, too.  

I'm going to have to speak at least somewhat convincingly about iPhone development in four months.  It's time to get back in the game and get ready to teach.  So how do I decide what to build?