{"id":752,"date":"2014-03-20T08:10:51","date_gmt":"2014-03-20T12:10:51","guid":{"rendered":"http:\/\/novicenolonger.com\/?p=752"},"modified":"2016-01-13T10:11:43","modified_gmt":"2016-01-13T15:11:43","slug":"how-i-built-and-promoted-workburst-my-first-os-x-app","status":"publish","type":"post","link":"https:\/\/novicenolonger.com\/how-i-built-and-promoted-workburst-my-first-os-x-app\/","title":{"rendered":"How I built and promoted WorkBurst, my first OS X app"},"content":{"rendered":"

\"workburst-bts-header\"<\/p>\n

My first OS X app, WorkBurst<\/a>, is now available in the App Store<\/a><\/strong>! To celebrate, I want to share with you my entire process, from idea to app release. I did everything without writing a single line of code. The total cost? $304.<\/strong><\/p>\n

The most important lesson here is that you don’t need to learn how to code to make apps<\/em>. You should learn to code if you want to know how to code<\/em>. If you want to make apps<\/em>, there are other, more direct paths to take.<\/p>\n

Here’s mine.<\/p>\n

The idea<\/h2>\n

Some of my favorite apps are the most basic. I use Quiet<\/a><\/strong> to block out off background applications and Freedom<\/a><\/strong> when I don’t want to be distracted by the internet. Neither are complicated apps. They do their job, and do it well. That’s it.<\/p>\n

I wanted a Pomodoro<\/a><\/strong> timer app that did the same thing. See, I have a hard time focusing when I have large tasks looming over my head. The longer the article, the worse I get. I’ll stall and pace and browse Twitter and make myself completely miserable.<\/p>\n

At times like this, the only thing that helps is the Pomodoro technique.<\/p>\n

I’m by no means a lifestyle Pomodoro master. It’s not something I use every day. I don’t break out my tasks into Pomodoro segments in order to plan my day. But if I’m working long hours on a tight deadline, the Pomodoro structure is the only thing that gets me through the task.<\/p>\n

But when I searched for a good Pomodoro timer, everything I found was filled with settings, options, lists, and complications. I wanted to be able to just start a timer and go. My problem was that I kept getting distracted, and searching for the right timer and messing with all the settings was just another distraction itself.<\/p>\n

I knew I couldn’t be the only person who wanted an app like this. So I decided to make it myself.<\/p>\n

Another important feature I wanted the app to have was to dim the screen during breaks. I have a terrible habit<\/a><\/strong> of never looking away from the screen. I didn’t want the screen to go completely dark during breaks, but bringing the brightness down to about 20 percent encourages me to get up and look away from the screen.<\/p>\n

Thus, the idea for WorkBurst was born. Since I don’t know how to code, here’s how I went from idea to App Store.<\/p>\n

Development<\/h2>\n

A little over a year ago, I stopped teaching myself how to code. By that point, I had made my way through Programming in Objective-C<\/em><\/a><\/strong> by Stephen Kochan (highly<\/em> recommend) and was partly through the free iPad and iPhone Application Development<\/a><\/strong> Stanford class by Paul Hegarty in iTunes U. I was understanding everything and making good progress.<\/p>\n

But then I had a realization: coding was not how I wanted to be spending my time. I wanted to make<\/em> apps, not code<\/em> apps.<\/p>\n

I don’t regret the time I spent learning to code \u2014 it’s given me an appreciation for development work as well as the skills to intelligently communicate with programmers. But I’d much rather pay someone to spend 10 hours of work instead of trying to do it myself, taking two months, having a worse product, and saving the money.<\/p>\n

Fortunately, I already knew a fantastic developer from when I built my first iPhone app<\/a><\/strong>. I shot him a quick email asking if he was still available for work and if he was able to do OS X apps in addition to iOS apps. He wrote back in a few hours, saying yes and yes.<\/p>\n

Next, I drew a couple of sketches using FiftyThree’s Paper<\/a><\/strong> on my iPad mini and shot him a quick summary of the app’s functionality.<\/p>\n

\"Email<\/a>I had a response the next day, saying that this app would take five hours of work. My developer, Planet 1107<\/a><\/strong>, charges $40 per hour (and if you follow that link, you’ll save an extra 10 percent off). The development work would would cost me $200.<\/p>\n

Design and Assets<\/h2>\n

Next, I had to find a task bar icon for the app as well as the sound effect to alert the user when the break starts and stops.<\/p>\n

For the icon, I used Iconfinder<\/a><\/strong> and set the search parameters to only show free icons that were available for commercial use. I used Freesound<\/a><\/strong> for the alert sound, also making sure I had the proper permission to use the asset in a commercial product.<\/p>\n

After sending those to the developer, we had many five or six more emails hammering out the details. I was sent version one of the application the following day (how’s that for a fast turnaround!?) and I sent him back my comments. We went back and forth a few times before the app was just right.<\/p>\n

Next, I needed an app icon. I jumped on Fiverr and searched for designers with experience making iOS 7-style icons. I found someone I liked and bought the gig. In the instructions field, I included a concept I had in mind (maybe a clock inside a lightbulb?) as well as a few colors that I like. I based the colors on the palate I chose for Novice No Longer.<\/p>\n

The icon was finished in a few days, and I absolutely loved it. I had a couple of changes, and the revision was returned the next day. Beautiful.<\/p>\n

Submitting the app<\/h2>\n

While I could have used Planet 1107 to help me provision and submit WorkBurst to the App Store, I decided to do it myself. The first order of business was to purchase a Mac Developer Account, which costs $99 per year.<\/p>\n

Just like with Reader Tracker<\/a><\/strong>, I tried to do the provisioning myself, but just found it too confusing. I set up a meeting with my friend and iOS developer Will Larche<\/a><\/strong>, and he helped me create and download the proper distribution profiles, and get everything set up properly in Xcode.<\/p>\n

Next, I wrote the app description and researched the best keywords to use. I took screenshots using Skitch (the old version<\/a><\/strong>, before it sucked) and edited them in Photoshop CS6 (although Pixelmator<\/a><\/strong> is a fantastic and inexpensive alternative that would also work).<\/p>\n

I submitted everything to the App Store, but chose a release date far in the future. This is because I wasn’t sure how long the app review process<\/a><\/strong> would take and I wanted to orchestrate a number of events around the launch.<\/p>\n

Once everything was submitted, all I had to do was wait. WorkBurst was approved in about four days, so not long at all. Everything was all set to go live, now it was time to get press.<\/p>\n

Marketing<\/h2>\n

In terms of press, I decided I didn’t want to do an all-out assault on every productivity blog imaginable. If this was a much larger and more important app, I would have made a list of every productivity blog I could find and send them each a personalized letter. Instead, I only targeted a few that would have the biggest impact.<\/p>\n

Shameless plug:<\/strong> if you want to know exactly what this process would look like, check out my upcoming course Turning Emails into Press: Getting and Keeping Journalists\u2019 Attention<\/em><\/a><\/strong>.<\/div>\n

The websites I decided to contact were:<\/p>\n