There I sat, in my home office, two minutes after midnight, white 16GB iPad mini in my shopping cart on the Apple Online Store. One click away from preordering a new Apple product for the first time in years.

But then I decided I would miss the hipsters in the Marina too much. So I went to bed.

Yes, that means I’ll be in line again this coming Friday. Call me crazy, but at this point it’s just too entertaining. I am hoping there won’t be rain, however. That’s always a bummer.

I’ve written before about Apple launches and the benefits of getting in line rather than waiting for FedEx. Allow me a moment to offer my thoughts on this particular iPad mini launch.

Preorders of the white version sold out in about twenty minutes, while the black ones weren’t sold out until over 35 hours later. What happened?

An educated guess:

• Apple usually manufactures far more black units than white, as black is far more popular.
• Preorders at midnight are usually dominated by developers and other tech nerds, who even moreso than the general public go with black over white for their devices. (They think black makes them cool, but the rest of us know it just makes them nerds. They also think that white is for girls, which is not only sexist, it’s stupid.)
• Developers and other tech nerds, the bulk of the preorder-at-midnight crowd, don’t view the mini as a potential primary iPad. They’re mostly thinking that this mini will just be a “testing device,” something to play around with and use for experimental purposes.
• Because of this, many decided, “What the heck? All my iOS devices are black. Let me try the white one this time.” (Anecdotal evidence from my developer friends, and even Marco Arment, has shown this to be true. I considered black for the same reason, but then I came to my senses.)

Thus, I believe Apple didn’t plan on enough white to meet demand. I’m hoping a week will be enough time to correct this mistake in judgement. I don’t want to show up on Friday only to be told they won’t have any white ones for in-person sale.

Regarding the lines, let me save some time for all the Apple haters out there ready to pounce on any opportunity to demonstrate that this new mini will be a flop. The lines won’t be very long on Friday. And that won’t be any indication of the mini’s future.

Why? Well, I almost preordered myself, as I mentioned at the beginning of this post. And I’m mister “Always wait in line.” If I was considering not waiting in line, you’d better believe that a lot of other usual line-waiters were, too.

And why would so many of us consider sitting this one out?

• We were just in line for the iPhone a few weeks ago.
• It’s November, which makes it a much colder (and possibly wetter) line waiting experience. Those few weeks make a big difference in much of the Northern Hemisphere.
• Only the WiFi models will be available. WiFi will probably be more popular than LTE, but that’s still millions of people who will wait a few more weeks to get 4G.
• Many will consider this just a testing device, as I mentioned before, so they won’t necessarily think they need to have one immediately. They’ll drop by the store a few weeks later and pick one up. Or just wait out the few weeks for home delivery. (Once they have one, however, they’ll end up liking and using it far more than they thought.)
• The core audience for this device is not the early-adopting tech nerd crowd. Like the iPod mini, this is the iPad for everyone else. It will sell accordingly, over the span of the quarter, to people who shop like normal people.

Oh, and a large portion of the United States is likely to be recovering from one of the nastiest storms in recent memory. Flood damage could very well leave millions of potential customers with decidely more important things with which to be concerned. (Best wishes to my friends and family on the East Coast this week. Stay above water.)

I’m planning on getting to the store just a few hours before opening. Even if the hipsters prove me wrong and show up earlier, iPad transactions go a lot faster than iPhone transactions, without all that contract nonsense. The line will move very quickly.

Make no mistake, though. The mini will be a huge hit. My guess is that sometime next year the mini will be the top-selling iPad. Just as the iPod mini was. It will become the primary iPad for most people, the way the 13-inch MacBook Pro is the go-to laptop for most people. Once it goes Retina, the mini may even become my primary iPad. Depends on whether that processor remains a step or two behind its big brother.

Smaller and lighter usually wins in the tech marketplace. Why do you think Apple is so seemingly irrationally obsessed with thinness?

I was really happy that I was able to learn enough Objective-C to make my own app, put it on the App Store, and see other people getting use out of it. The response has been great so far, and I’m planning lots of new improvements already.

But I’d be lying if I didn’t admit there was one thing, visually, about the app that was bugging me. And that was the default Apple keypad.

Not that I don’t think Apple’s keypad is a great design. It looks good and it functions perfectly. But because I had chosen to use Futura throughout the app, the default keypad’s use of Helvetica just didn’t quite blend with the rest of the app’s look. It’s the kind of thing maybe most people wouldn’t notice, but my audience here is graphic designers. So this was important, no matter how much I tried to convince myself otherwise.

I also didn’t like the color of the keypad for my app, nor the use of letters under the keys. The letters make sense for phone dialing, but they were adding visual clutter that is completely unnecessary for my purposes.

Because I was a noobie to programming, I assumed that changing the default keyboard would be a huge pain in the butt. So when releasing 1.0 I decided to live with it.

After all, you have to make compromises to ship apps, right?

Then I started playing around with making the app iPad compatible, and I quickly realized that the iPad doesn’t have a default keypad. You literally have to roll your own keypad if you don’t want to use a full keyboard.

So I figured I have to build my own keypad soon, anyway. Why not put it in the iPhone version first?

As with many other aspects of iOS app creation, coming late to the party made my life a lot easier. Switching out input views in iOS is a lot easier now than it was when iOS was much younger. That’s not to say it wasn’t still more work than it should be, however.

While dropping in my new, pretty, Futura keypad, I got to see firsthand what so many of my developer friends have told me over the years. Every time you solve a problem in your app, two or three new problems seem to crop up. I pop in new code, and something breaks somewhere else. You think you’ve got one new thing to learn how to do, but you actually end up having to learn how to do four or five other things before you’re done.

It was a huge reminder of just how little I really know, having just built one simple app. But it was also encouraging, because ultimately I was able to figure it out on my own. One more thing I’m confident I can do the next time it comes up. And several other things I understand about how classes and nibs work that I didn’t know.

A look at the before and after, I think, speaks for itself. This is a huge improvement to the app.

Version 1.1 was submitted last night, and will be available as soon as Apple approves. I also added in a few extra ratios to the list of Common Aspects whlie I was at it.

Now to tackle the rest of that iPad layout.

I work with an amazing team at Bombing Brain Interactive. While my role there has always been visual and user experience design, along with web site development, one of my goals this year was to branch out a little into real, honest-to-goodness app coding. Not that we don’t already have an abundance of coding talent going on with Gene and Tim, but because I wanted to improve my skill set and make myself more valuable to the group in any way I could.

I believe firmly that in order to work with other people in various disciplines, it always helps to learn a bit about what your collaborators do all day. Not only does that help inform decisions you make in your own role, it also helps with empathy for your teammates. You need to appreciate everyone else’s contributions, and that’s so much easier when you can see clearly just how hard their jobs are.

Does that mean I plan on being a super-pro coder someday? Not necessarily. But I did want to bring something more to the group than I was able to a year ago.

So I embarked on a quest to learn Objective-C and to get more comfortable inside Xcode.

I didn’t come into this with no coding experience at all. I do have several years of Javascript, HTML, CSS, and a touch of PHP under my belt. But I don’t kid myself into thinking any of that makes me a programmer. That’s baby stuff, essentially. And I’ve never had any formal training in C or any other computer language. I’ve always sort of hunted and pecked my way into figuring out whatever the current project needed, much the same way I did with Photoshop and Illustrator so many years ago.

So I picked up some books, downloaded some course materials from Harvard’s excellent CS50 on iTunes U, and started reading and learning in my spare time.

Then I came across Mysterious Trousers’ TinkerLearn series. And for whatever reason, that style of teaching really worked well for me. How TinkerLearn works is you download full Xcode projects, and all the lessons are embedded in the files of a real working app. This way, you get to experiment and learn about real code in a very practical way, in context.

After a few lessons, I decided to give myself a project. I’d take an idea and turn it into a full-fledged working app that I could develop all the way to the App Store. I needed something small and easy enough to do without getting overwhelmed, but at the same time, I wanted it to be a challenge, and I wanted the app to be something I’d actually use.

So after some thinking I settled on an Aspect Ratio Calculator. Three main reasons why this was the perfect project for me to work on as my first App:

1. It wasn’t your typical tip calculator, or other sort of “my first app” project. It was different enough to not be an also-ran, without being something that was completely useless to anyone, either.
2. I’m a web designer, and I really need to do these sorts of calculations often. So it was a personal project. Usually the best apps are ones made by people who want to use those apps every day.
3. The aspect calculator apps that were already on the Store weren’t lighting my world on fire. No offense to the other fine apps in this category, but most of them haven’t been updated in quite a while, don’t offer much in terms of visual design, and don’t tackle the problem the way I feel I would want it done. In other words, I needed this app, but nothing on the Store was fulfilling that need to my personal satisfaction.

And thus x2y was born. Simple. Elegant. Solves a real world problem. Whenever I wanted to add a feature that I didn’t know how to add, I would consult YouTube, Apple’s Documentation, web articles, whatever I could get my hands on. It’s amazing how much knowledge is out there, free or very cheap, that could get anyone up to speed on making apps. Developers are extremely generous with their knowledge.

At one point, I even enlisted Tim to help me out with a big problem I was having. As expected, he suffered my noobie questions with grace and got me back on track.

When I started this project, I thought maybe I’d get it done by sometime next year. But once I got past the first few big bumps, I became more driven to finish it. And then I remembered all the other stuff that goes into launching an app. The web site, the screenshots, the description, the keywords, the user guide—there was plenty to keep me busy, but the closer I got, the faster I worked.

I’ll be happy to sell ten copies of x2y; my goal here isn’t to have a big hit. After all, this is a niche app, and a very simple one at that. But I am proud to see that I was able to get all this done in a few short months and that I sweated the details as much as I did. Forcing myself to put the app out there on the Store, with my name attached to it, ensured that I would take every aspect of development seriously. This may be the first app of someone new to Objective-C, but it was built with all the design and user experience expertise that I’ve built up over several years making iOS apps with others.

I’m looking forward to my next project, which will challenge me even further.

But mostly, I’m just glad I’ll finally have a good aspect ratio calculator on my iPhone whenever I need it.

x2y is available now on the App Store for a special introductory price of just 99 cents USD. More infomation can be found on the official x2y web site.

Today I’m launching my first iOS app, x2y. While I’ve collaborated on many apps with my partners at Bombing Brain Interactive, this is the first app developed entirely by yours truly and published under my own name.

x2y solves an old and common problem. You have an image or other media file, and you need to display it at a different size than the original. But when resizing the image, you need to be careful to keep the aspect ratio consistent, so that your media doesn’t get stretched or pulled.

So you take the original dimensions, the height or width of the desired new dimensions, and cross multiply to get the new missing dimension.

x2y helps make that calculation much simpler. Nothing more or less. Clean. Elegant. And best of all: Futura.

The app is fully compatible with both 3.5-inch and 4-inch Retina screens, works well with Voice Over for the visually impaired, and includes a full user guide within the app itself.

I’m really proud of the way x2y turned out. I had a simple goal this year of learning enough Objective-C to make myself more valuable to the Bombing Brain team, and I thought the best way to do that would be to give myself a project and see it all the way through to the App Store. And because I was putting my name on it, I wanted it to reflect every bit of the polish and care that would go into any project to which I commit myself.

I hope you enjoy x2y. You can find out more at x2yapp.com, or buy it today on the App Store. The special introductory price of 99 cents USD is for a limited time only, as a thank you to my friends and readers. If you have any feedback or want to see a feature added, there’s a contact form on the x2y web site.

Appeals court rules against Seattle’s curbs on yellow pages | Local News | The Seattle Times: “The court ruled the city’s law is unconstitutional, saying yellow pages are protected, like other publications, by the First Amendment.

‘Although portions of the directories are obviously commercial in nature, the books contain more than that, and we conclude that the directories are entitled to the full protection of the First Amendment,’ Judge Richard Clifton wrote in the decision. ‘As a result, when we evaluate the ordinance under strict scrutiny, it does not survive.'”

(Via. the Seattle Times)

The huge thing that bugs me about a story like this is not all the legal issues involved. I actually agree with the court’s finding in principle. It’s the notion that you have a group of people who clearly don’t want these books, and yet the Phone-book companies want to shove them on their doorsteps, anyway. I mean, once someone tells you point blank they are completely uninterested in your product, what is the point of shoving it down their throat? You’re not going to make any money off these people. You’re going to waste your own money printing a book that immediately gets trashed. So why would you give it to them, and pay a lawyer do defend your right to do so?

This is the problem with advertising as a business model. All the stats are based on the number of “eyeballs” rather than the effectiveness of the ads themselves. Reach the maximum number of people, period. Don’t worry if you’re offering breast implants to men or Viagra to women. Just reach people, because at best you’re going to convert on 1 or 2 percent of them. The money comes from total people who saw the ad, not the percentage of those who actually bought the product as a result.

This was the problem that Google’s promise of “targeted” ads was supposed to solve. But it hasn’t. At the end of the day, all the targeting in the world doesn’t pay as well as good old fashioned dumb carpet bombing of the entire universe.

Sad, really.