This past weekend I participated in my first NYC hackathon. The New York Hackathon is a mythical beast. They’ve been written about quite extensively, but you really need to just show up to one to know what it’s all about.

This particular hackathon (Photo Hack Day) was organized by Aviary, with sponsorships by Bing, Pepsi, PBR and others. There was plenty of food so that hackers didn’t have an excuse to leave, ever. I still ended up going home to get some sleep on Saturday night before the demo on Sunday.

I really think I picked a good first hackathon to attend, as the prizes were pretty insane. First place got $5000 and the cash prizes for second and third place were quite good as well. On top of those, there were prizes for best use of certain APIs. Face.com’s API stood out as a popular one; 500px had quite a few users as well.

I ended up working on a project I had wanted to build for a while: a custom collage creator for your iPhone wallpaper. I called it “AllPaper.” It seemed pretty catchy and I don’t think there’s a product with that name yet. I integrated Instagram into it first, then threw support for 500px, PicPlz and Facebook before calling it a hack. I also integrated the Sincerely Ship Library which lets you turn your collage into a real postcard. I’m really looking forward to trying that out!

Overall I’m pretty happy with how the hack turned out. I can probably turn it into a real app fairly easily with some tweaking here and there. As this was my first hackathon, I noticed a few interesting things about the top hacks. There was some grumbling about how many of them seemed “hardcoded.” I wonder if presentation really counts more than actual hack-worthiness these days. You could spend your time actually coding something, or you could create the facade of something that looks even better, but is not really that worthy of being called a “hack.” It seems that the presentation wins over the true hack-worthiness, as one of the cooler ones, a jailbroken iPhone that took MMS messages and uploaded them to a web service, won nothing.

Coming away empty-handed was a little damaging to the ego, especially after winning something in my last hackathon, but my ego’s not too bruised. I hate to sound like I’m complaining! Almost all of the presentations were well done, and the winners certainly did deserve to win. I’m hoping to participate in something similar again soon, as the atmosphere was really enjoyable.

It’s been about 4 years since I announced the launch of Mapskrieg, my Google Maps and craigslist mashup web app. Since then, I’ve gone to school (again), worked for Microsoft and quit, and made a few apps. Today, I’m happy to announce the launch of my newest app, Mapskrieg for iOS!

I’ve been working on this app for a few weeks, and I think it’s ready for public consumption. It’s basically Mapskrieg, but developed natively for the iPhone and iPad. In the past, I’ve taken a sort of iterative approach of releasing fairly minimal apps and improving on them. For example, I released Threadless as an iPhone only app and later added the iPad support. I wanted to release Mapskrieg on both platforms so the launch would have a little more bang. Plus I think the iPad app is the better of the two, and I really wanted that one to stand out for the release. I’ve been getting much more comfortable with mobile development, and I’m very happy with the rate at which I was able to conceive and release this app.

That’s not to say I didn’t struggle or learn anything new with it. While a lot of the concepts are borrowed from my Threadless iPad app, I had to do a lot of stuff I hadn’t done before. For example, since Mapskrieg is going to rely on iAds to make money, I decided that both the iPad and iPhone versions would support iAd. Apple, in their infinite wisdom, made the split view controller a very useful and now, standard, design paradigm. Unfortunately, they don’t provide any support for using it with iAd at all. What the fucking fuck, Apple!? So I had to basically recreate the Split View (well, the landscape mode at least) in order to support iAds. It’ll be well worth it if I can rake in some iAd dough, though!

This post also comes almost 1 year after I quit my job at Microsoft. That milestone probably deserves its own post, but I’ll just say that I have not yet regretted my decision in the very least so far. This is as fun as it gets, folks!

Edit: Oh, I forgot to link to a demo video that I recorded for a contest. Check it out in case you don’t have an iOS device:

I knew that I wanted a grid-y layout as opposed to the list-y one of the iPhone/iPod, which was partly the reason why I hadn’t done the iPad version yet. Lists on iOS are easy because they’re given to you for free. Grids are a whole other beast. Luckily, I ran into a framework (AQGridView) on GitHub that does grid layouts in a tableview-y sort of paradigm. The framework was still a little beta (or alpha) as I had to go in and change a few things that were crashing, but it did succeed in making my job a lot easier overall. I’d like to try contributing to that code to improve it, but I guess that’s another post altogether.

After getting the grid stuff working, I decided to use a modal pop up view to display the images and sharing options all in one view. Since the iPad has much more screen real estate, it’s easy to design things without running into space issues. You don’t, however, want to just stick a billion buttons in because you can. I think this design does a good job of showing enough stuff to the user, but not too much stuff too soon.

I still have some bugs to fix, mainly with memory management due to the grid view stuff. If you have any suggestions, feel free to comment on this blog!

Hopefully the iPad app continues the mission of the iPhone app, which is to provide a really easy and fun way to browse and share awesome Threadless designs! I may have been an early iPad doubter, but I really believe that it’s a great device for consuming content. Even on my iPad 1, the designs and colors just pop on the app. At least I think so. But you don’t have to take my word for it!

Get the app if you don’t have it already!

Checkmate ended up winning third place out of many many competitive entries (leaders and the best!), so I’m super happy about that. Here’s a story in the University Record about it. The HiJack project that’s been getting a lot of press was the grand prize winner. Props to those guys!

Winning a prize in this contest was a really nice way to start my year. It’s really encouraging me to continue doing mobile apps and exploring what’s possible.

I just got an Android phone, the HTC Hero, to play around with and perhaps develop on. It was only $55 on Ebay (including shipping) which seemed like a steal to me. I’m currently using it on WiFi without any phone service (the phone has a bad ESN, so that’s probably why the price was so low).

My first impression as an iPhone user is that the interface is really clunky. There just isn’t as much attention payed to detail. For example, there are often measurable delays between pressing a button and seeing something happen. This happens when I try to add a widget to the home screen or open an app that hasn’t been opened into memory. If I press a button and I don’t see something happen immediately, I will assume I missed the button and press it again. This is extremely frustrating since the iPhone animates immediately upon user interaction. The iPhone may not be any faster than my Android phone, but it at least gives the illusion of it (which is probably just as good in terms of usability).

Another thing I noticed is the lack of “back” buttons in the Android apps. Even Twitter lacks the onscreen back button. I assume this is following some kind of standard Android paradigm of favoring physical buttons over onscreen ones. It took me a while to get used to hitting the physical back button (and home, menu and search for that matter) instead of looking for navigation on the screen. While this is a different paradigm, I’m not sure I’m in a position to say it’s worse, better or on par with the iPhone. My suspicion is that the lack of onscreen navigation requires the user to go through more context switches (screen to physical button back to screen) which is disorienting. This is made worse by the fact that there’s seven fuckin’ buttons on my particular phone! I’m sure people adapt and get used to it, but I’m personally used to having just one button that takes me to the home screen (oh, and the volume and lock buttons, but they don’t serve dynamic functions in applications (unless they want to break the App Store terms)).

About the only positive thing I can say about the Android platform is that Google is integrating the shit out of it with their own services. I only have to sign in once with my Google account and I get Voice, Talk, Maps, Search, Goggles, Places, Latitude, Market, Contacts, Gmail, YouTube and probably some other things I’m forgetting. The voice commands are incredibly cool, though I wonder how many times I’d actually use them instead of doing things the normal way. Oh, another positive is that Angry Birds is free on Android, though my device is way too slow to run it.

I’m currently using a ROM with 2.2 on my HTC Hero, so that might account for some performance issues (though I thought it was supposed to be faster). I’m still kind of unimpressed by Android as a whole though, especially in terms of end to end usability. I originally got this device so I could test code on hardware, but I’m not so sure I even want to develop for Android anymore. I’ll probably end up writing some simple code, at least.

Does anyone with a newer Android phone want to debunk or argue with anything I’ve written?

It’s no secret that I’ve been a huge fan of Threadless since I discovered it back in 2005 (see these blog posts for proof). I really love the fact that the community provides designs and decides which ones will be printed. The company is really only there to provide the machinery to make shirts and fulfill orders! I wanted to contribute to the community by making an unofficial Threadless app (and maybe get a little store credit to feed my t-shirt needs).

My main reasoning for writing a native Threadless app is that I found it pretty hard to browse shirts, even in a fully fledged web browser let alone an iPhone browser. The Threadless site is by no means bad, but it’s hard to see what designs look like when the images are small and on models. I prefer viewing the actual design. So I built an app that makes it easy to 1) browse and find cool shirts and 2) share them with your friends.

In order to do this, I needed to get a database of shirts on Threadless. It’s kind of unfortunate that Threadless doesn’t have an API. At all. Threadless does, however, has a few feeds of shirts: one for shirts that are in stock and another for the weekly additions. I parsed this list of shirts and saved them in an App Engine database along with some other metadata like image urls, category info, etc. I also figured out a way to get the list of all Threadless shirts, including the ones that aren’t currently in stock. What this means is that the ♥s Threadless app will help you find more shirts than even the official website can. You can filter by category, color and run fulltext searches on the entire shirt database.

As far as the front end work went, I had to build a custom table view cell to scroll through shirts and a nested scrollview to view shirt images. The shirt view looks a lot like the native photo browser app for the iPhone. I also added features for sharing, including saving the image to your photo album, posting the design on Twitter and Facebook and emailing the shirt design as an attachment. I figure that covers most bases as far as sharing goes.

So far I’ve only designed and built the iPhone version. I think an iPad version would be neat, too, but I want to gauge the interest in the iPhone/iPod app before putting more time into this. If you like the app, let me know and write up a review for it!

Finally, here’s a video demo of the app, just for fun:

Something I noticed right away which disappointed me was that they basically slapped on a new view to the existing app, and didn’t even bother to match the style of the original app!

Screenshot from official foursquare blog

Not only is the new bar a different color, it’s also a different height than the existing one! It also lacks labels where the original one has labels below the icons. This is simply sloppy design. These two screens exist in the same version of their app! It wouldn’t have taken much more work to either update the app so both bars are grey, or match the new views to the old one.

I recently saw that foursquare is looking for a new Product Manager. I’m considering applying to help them out with their product issues

EDIT:
After emailing back and forth with Alex Rainert, foursquare’s head of product, it seems that, to answer my own question, this was a conscious design decision to change the visual style of the buttons. In one context, they are for navigating various top level features, and in another, they are buttons for various pop-up actions. It’s of my opinion that the change in visual style is a bit too much (the change in height along with the loss of the location footer in some screens), but that’s a design choice that foursquare made intentionally.

As I noted in an earlier post, Apple responded to a really low fill rate on their iAd program by enabling developer ads. Developer ads are simple banner ads that entice a user to download an iPhone app. Here’s what the use case looks like via Business Insider:

To Apple’s credit, the workflow is actually pretty good. It doesn’t require users to leave the app to download another one.

Since developers can’t really afford the insane $2 cost per click that the big media customers pay, Apple is charging $.25 a click instead, and no cost per impression. Theoretically, this should mean that the fill rate would be very high (as long as developers are not maxing out on their daily spend limit or too aggressively filtering out apps). Yet I’ve noticed a pretty big fall in fill rate (from about 30% to 20%) in the last month.

I think the main issue is that Apple never really intended iAd to be used for performance advertising. Performance advertising is about getting that direct action (in this case, an app download). Apple’s been pushing iAd as a great Brand advertising solution (where the user is not expected to go out and buy Dove soap from their phone). That’s why the premium brands are willing to pay so much per click and impression. By comparison, AdMob ads on the iPhone seem to be more geared toward performance advertising.

By introducing developer ads, I think Apple has tried to appease publishers at the cost of the perceived premium value of iAds. Sure, the developer ads aren’t as flashy as the premium advertisers’, but $.25 versus $2 a click for the same piece of real estate is quite a difference. Add the perception that iAds for developers are not cost-effective and you could come to the conclusion that Apple is doing it wrong. It doesn’t help that the premium brand advertisers seem to be frustrated with the process of dealing with Apple as a gatekeeper.

So what can Apple do to fix this? They should go back to their specialization: doing one or a few things really well. They should focus on iAd as a brand advertising platform. They should work on getting as many large partners onto iAd as quickly as possible. This will alleviate the growing pains that publishers (including me) are feeling with fill rates. Right now it seems like Apple is reacting rather than acting; following rather than leading. They need to show that they’re serious about carving their own niche in the mobile advertising space.

Just about two weeks ago, I released my first paid iPhone app, Checkmate. The experience has been priceless, plus I made a few bucks as well. I thought I’d share the stuff I learned, both technical and otherwise.

Technical:

Core Location. Being the first iPhone app I’ve done that uses Core Location, I learned a lot about the process of starting up the location manager, filtering location updates and getting them to work in the background. The background stuff is pretty new, just released in iOS 4.

Design takes thought. One of the most difficult things in designing an app is balancing between user expectations (“it should work like magic”) and real-world constraints (battery, accuracy tradeoffs). I’ve taken the approach of leaving the details under the hood (another app that does something similar gives users full control) for simplicity. This is a deliberate design decision. I’ve found that many users are happy with the app, and some are unhappy. I assume there is a minority that is unhappy, but that they seem to be more vocal (more on that later).

Core Data. I also learned about Core Data, since I use that for storing venue data persistently. There’s a bit of a learning curve with Core Data, but I have a pretty good idea of how it works. I guess it helps that I’ve designed a bunch of database schema in the past.

Get to good enough. I definitely feel like I have accomplished something by releasing the app. I have wrestled in the past between releasing something when it’s “good enough” but not getting stuck in perfectionist limbo. In the case of Checkmate, I got to a point where I was happy enough with its performance (it works) and did not want to delay any further, lest I lose steam and give up on ever releasing it. Now that I’ve gotten a feedback loop going, it’ll be easier to improve and update the app anyway. As far as interface design goes, the app is a bit clunky for my taste. Having admitted that, I think I could go back and make some things more obvious (like the login screen) and polish up the user experience.

Business-ey

Ask for reviews. Ask satisfied customers for reviews. Because if you don’t, only the unhappy users will post them. And you’ll end up getting a pretty bad average rating. Even if your app makes crap into gold, there will be users who don’t see the value in it, or think that $2 is too much to pay. Encourage users to post reviews in-app and you’ll see a well-rounded view of what people think about your app.

It’s okay to have a competitor. While developing my app, I found that another similar app had launched and gotten some press from Techcrunch. This was a bit depressing as I wanted to have that exposure. I ended up using it as a motivator since the blog post and app validated my own idea. There’s always room for competition, especially if you can outdo them.

Popular takes all on the App Store. There have been blog posts on the subject of iTunes ranking and how valuable it is to make a top 100 list. Apps seem to be ranked in search based on their sales volume, which means that popular apps will become more popular. Having been featured on Mashable at launch, my app got to #2 for a “foursquare” search. This helped a lot for residual sales. I’m assuming that most apps are sold directly from app store searches. There are other ways to discover apps.

Have fun! It was really exhilarating to see my app get into the app store and into the hands of users. I set up a twitter account to communicate with users, monitored twitter searches for my app and answered emails sent through a contact form on my website. It was really fun having people react to work that I did. It’s probably one of the strongest motivators for me to keep doing what I’m doing.

I have learned a great deal from my first commercial app launch. I’m really glad that I had an idea and stuck with it to completion. I’m still learning a great deal from Checkmate. I know that this experience will make the launch of my next product/app (whatever it might be) more smooth, both for me and users!

My second iPhone app, Checkmate, just got approved in the Apple App Store last night. It’s an auto-check-in app that runs in the background. You select your favorite venues, and Checkmate will check you into them when you get close enough, even when the phone is still in your pocket! I wrote this app because I got annoyed at forgetting to check into places on foursquare while there.

If you’d like to get Checkmate, you can buy it here for the low price of $2. For more info, check out the official website I made for it. And follow Checkmateapp on Twitter for news on the app.