1. Connectivity One thing we NEVER want to worry about at a hackathon is connectivity and bandwidth. That’s a given. We should only have to worry about our hackathon project, not trying to find a wifi signal or futzing around with the Wifi password. Along with that, there should be plenty of outlets. We really hate going to hackathons and having to fight for power outlets.
2. Clear schedule / agenda We want to know when things begin, when code freeze occurs and judging takes place. When lunch and dinner is served is also very important.
3. Prizes What’s going to motivate a developer to give up his weekend to code on your API? I would venture developers who come to hackathons already have side projects. They probably command a decent salary or consulting rate. Prizes have to be compelling or worthwhile. Having multiple prizes also helps so it’s not a winner take all situation.
4. Multiple categories/judging criteria Having multiple categories for prizes is another great motivator. There could be different prizes for Best Overall, Best Design, Best Mobile, etc etc. This way someone might feel like they might have a shot at winning if one of the categories matches their strong suit.
5. Make sure it works If you are holding a hackathon where developers use your API or code library works. The hackathon is NOT the place to be debugging it. The developers are not there to find your bugs. It should just work. Along with that, make sure that the API key and whatnot are readily available.
6. Good food Pizza and red bull are great but many people I run into have special dietary needs. Some are vegan, some are vegetarian. Often times these developers are totally neglected when it comes to their dietary restrictions. Make sure you take care of these folks. Make sure you also have enough food. On especially long hackathons, snacks are always welcome.
7. Clear/accessible location People hate getting lost. Make sure to provide adequate instructions to finding the location. It also helps to have signs saying “Hackathon” pointing in the right direction. If the location is locked down because it’s the weekend (as hackathons are often held on weekends), then make sure that there’s someone to let people in.

I love using Instagram. The problem with Instagram however is their web experience is non-existent. I’ve been frustrated that the only way to consume Instagram is through my iPhone. Lately, Pinterest and Instagram have been getting a lot of press because of Instagram’s 1 billion dollar purchase by Facebook and Pinterest’s hypergrowth.

My cofounder Brandon and I were having a discussion on startup pitches, especially the ones that go “we’re an X for Y” and thought a hilarious VC pitch would be “we’re a Pinterest for Instagram”. The more I thought about it, the more I liked the idea. I liked Instagram, and this was a real need for me. There was nothing like it out there that I would use. So last weekend I decided I would make it a weekend project.

I spent a few hours putting something together using my design and front end skills. I was able to show the popular Instagram feed using their API in a Pinterest-like UI. I showed this to Brandon which quickly convinced him this was a good idea and together we started clobbering together the project. By the end of the weekend we had something that basically worked. You could log in with your Instagram id and view your feeds, your photos, what’s popular and search.

We found that Pinstagram was really useful. I actually consume Instagram a lot more through this. It was an easier experience and I can see a lot more photos faster. Brandon told someone the idea and they wondered why anyone would want to use such a service but as soon as they tried it, they immediately realized that it was very useful.

So without further ado, it is my pleasure to present you:

The site does integrate with Instagram and will require that you have a valid Instagram account.

For those of you interested in how it was made. It’s a very simple Ruby and Sinatra app. It doesn’t even have a database. The front end was built on Twitter Bootstrap. Haters can hate me for not building the html from scratch but I prefer to build my house using off-the-shelf tools instead of having to go and chop wood in the forest. The Pinterest style layout was built using Masonry, a very useful jQuery plugin. All this of course was also made possible using the Instagram API which was very well documented and easy to use.

Client doesn’t know what they want. This is a pretty common problem with inexperienced clients or ones that haven’t dealt with a lot of software development shops or consulting firms. This is exacerbated by firms that don’t know how to manage clients and projects properly. The combination is disastrous because clients have a vague idea of what they want and consultants don’t know how to get it out of them.

Client doesn’t know how to articulate what they want. This is very similar to the first problem but not nearly as bad. They know what they want, but don’t have the vocabulary to describe it or the breadth of experience to point you to what they want. It’s up to the consulting firm to be able to guess and point to existing examples in the real world that might be close to the client’s vision.

Clients want the wrong thing. I’ve had potential clients come to me who know exactly what they want and that’s great. However, sometimes the thing they want, you know it’s just a bad idea. By that I mean, they want stuff you know to be bad weather it’s a flash site with tons of music or a social network that bombards you with ads because they think that’s what people want to do: click on ads. I try to convince them that it’s a bad idea but this rarely works because you are basically attacking their ego. That’s their idea and you are saying it’s dumb. I usually just turn these clients down.

Lack of communication. Software development is a collaborative process. Consultants rarely know everything about the business of the client and relies heavily on the client to bring their domain expertise. It’s not like going to a car dealership and just picking out the car you like and agreeing on the price. The software firm will need a lot of information from you. A lot of times, getting content, feedback from clients is like pulling teeth. This usually holds up the project and adds needless delays.

Client doesn’t know what customers want. This is a common problem among startup clients. The fledgling company may have a clear vision of what they want, however, that doesn’t mean that it will work. It’s merely a hypothesis. Even if everything is executed as the vision, there’s no guarantee that users will flock to it. Color comes to mind. Clients may think they know what users want, but that is not always the case.

Trying to finish a project by throwing more people at it. You can’t just throw more people at it. Nine women can’t give birth in 1 month. Software development is problem solving. It’s not a simple application of force like adding more people to move a boulder. Thus just throwing more people at it without understanding how to apply them doesn’t necessarily lead to project completion or success. I highly recommend this book “The Mythical Man Month” regarding this topic.

Software as a checklist. This occurs more at big organizations. Software is treated as little more than a feature list to be checked off. Little thought is given on usability, whether or not it actually solves any problem, or if people end up actually using it. When software doesn’t solve the problem or is so hard and unintuitive to use, even if it was delivered on budget and on time, it’s not a success.

On motivation:

(Y)ou should never start a company with the goal of getting rich. Your goal should be making something you believe in and making a company that will last.

On impressions:

People DO judge a book by its cover. We may have the best product, the highest quality, the most useful software etc.; if we present them in a slipshod manner, they will be perceived as slipshod; if we present them in a creative, professional manner, we will impute the desired qualities.

A great Jonny Ive quote:

Steve and I care about things like that, which ruin the purity and detract from the essence of something like a utensil, and we think alike about how products should be made to look pure and seamless.

On Apple stores:

Jobs decided that Apple stores should have only one entrance, which would make it easier to control the experience.

On problems:

If something isn’t right, you can’t just ignore it and say you’ll fix it later,” he said. “That’s what other companies do.

On how ruthlessly focused he was:

“What are the ten things we should be doing next?” People would fight to get their suggestions on the list. Jobs would write them down, and then cross off the ones he decreed dumb. After much jockeying, the group would come up with a list of ten. Then Jobs would slash the bottom seven and announce, “We can only do three.”

On the simplicity of the iPod:

In order to make the iPod really easy to use—and this took a lot of arguing on my part—we needed to limit what the device itself would do. Instead we put that functionality in iTunes on the computer.

On creativity:

There’s a temptation in our networked age to think that ideas can be developed by email and iChat,” he said. “That’s crazy. Creativity comes from spontaneous meetings, from random discussions. You run into someone, you ask what they’re doing, you say ‘Wow,’ and soon you’re cooking up all sorts of ideas.

On Apple’s approach to building great products:

We believe that it’s technology married with the humanities that yields us the result that makes our heart sing.

On focus:

Deciding what not to do is as important as deciding what to do,” he said. “That’s true for companies, and it’s true for products.

These quotes are courtesy of Isaacson, Walter (2011). Steve Jobs (Kindle Location 1601). Simon & Schuster, Inc.. Kindle Edition.

For example, for years I clung to the ritual of paying my bills by writing physical checks. I liked going through the process because it felt like I was paying more attention to my finances by doing so. When I finally awakened to paying my bills online and even setting the recurring payments to autopay – it was amazing. You don’t have to pay attention to it anymore. It’s always good to every once in a while make sure you are not being billed for anything you didn’t want but in general, setting this and forgetting this task is an overal productivity plus.

As part of my work, I design a lot. I can spend hours on Photoshop. One thing I started to finally notice after years of using Photoshop was that I kept doing a certain task a lot. I would copy a Layer Style of one design element and apply it to another. This would take several clicks – Right clicking on the element I liked and click on the menu item. Then I had to right click the new element and apply that style. There weren’t any shortcut keys, or at least none that I saw. It dawned on me that it was so inefficient and time consuming and that there had to be a better way.

I finally started researching this and found that you can create your own shortcut keys and I did so. Now I can do the same set of routine tasks that would take at least 4 steps and reduced them to 2.

Of course not everyone uses Photoshop but if you generalize this lesson, you have to be aware of the things you do. You have to be critical of all the steps you take to accomplish a task. Ask yourself, can this be simplified, reduced or automated in any way. Can you systematize this. Even better, can you remove yourself from the steps. I’ve really started to think about this and it has helped streamline my day and focus on the things I have to focus on.

This is the story of Outlaw Poker, an iPhone game I just launched that is equal parts Tetris and Poker. It’s a western themed puzzle falling blocks game. The object is to make 5 hand poker hands with the falling cards. The cards can be rotated just like in Tetris-style games so that you can arrange the cards into Poker hands horizontally or vertically. It is available here on the iTunes App store.

I initially had the idea almost a year ago. I wanted to make an iPhone game just to go through the process of making one as well as to have potential for some passive income. For those of you who are not familiar, developers can sell apps in the iTunes App Store and make money. The developer determines the price and whatever you make, Apple keeps 30% for facilitating the transaction and taking care of the distribution, billing, etc. Not a bad deal especially considering there are over 100 million iPhones in the world.

So how did this game come about? I was thinking about games I liked and games people liked in general. If I had to name one game that had mass appeal, it was Tetris, hands down. Another trend that has caught on in the recent years is the popularity of Poker. My thought was to combine the two popular concepts together: a falling cards game where you have to make Poker hands.

There wasn’t anything out there like this and I wanted to play it. People say one way to make a successful product is to scratch your own itch – that is, make something you want and hopefully others will want it too.

Since I wasn’t an iOS developer but designed stuff, I went about looking for a developer who would want to partner with me to develop this game. Initially I had recruited a lead Creative Designer who would lead the charge on the design direction of the game but he was quickly overwhelmed with his own work. I also managed to find an iOS developer who was initially interested but was also too busy to take the project on.

So the project never went anywhere for a good six months. I would design some screens and work out some details every now and then, always keeping an eye out for an iOS developer looking to meet a cofounder and have a game under his/her belt.

One day I went to some developer meetup and met my cofounder Ben Roesch. He was a friend of a friend and worked at Accenture Tech Labs, where I used to work. I was straight up with him. I told him about the concept, showed what screens I had to him and asked if he wanted to work on this app. I basically told him everything. If he decided to decline but run away and take my idea, he had it and I would be screwed. He was game though. Within 2 weeks he had a rough prototype of the game that basically worked but had none of the bells and whistles. It was a very good sign.

Over the next months, we would hash out the missing artwork/screens, tweak the gameplay, find the sound and music. One of the hardest things to come up with was the new company we formed. I love puns and wanted this new game studio to have a witty name. Since it was an game app company, I thought it would be cool to have the word ‘app’ in the name. Unfortunately anything that I came up with like ‘tap that app’ was already taken. I think I finally came up with Appuccino Games because I’m a big coffee drinker and it reflects the fact that coffee helped us make this game. I wanted the logo to reflect the dual nature of the word play (app and cappuccino). Once the name came together though, it was easy to come up with a concept for the logo – an iPhone that looked like a coffee cup.

I wanted to take this moment to thank everyone who had a hand in making it. A big chunk of this goes to Ben who without him, my concept would never have been realized. Thanks Ben. I also owe Matt Jensen a big thanks. He came up with the original art direction. Even though you didn’t have the bandwidth to join us on this, I still want to thank you for all the work you put in. Don, thanks for forming our new company. I look forward to more business with you. I also want to thank all the beta testers who gave us valuable feedback. I won’t remember everyone but here goes: Craig, Ulliott, Sami Rageb, Christian Arca, Joe Dwyer, Christopher Lee, Brad Flora, Ravi Singh, Tal Liron, Nick Aiello, Brandon Leonardo, and more.

I also want to take a moment to thank Steve Jobs. He’s been an inspiration to my career. Without him, this game would not be possible. The platform this game was built on would not have existed. You have enabled me to not only create this game, but to be able to distribute it to the world. Thank you.

Without further ado, our game is here on the App Store. There’s also a free ad-supported version here. The difference is that the free version has ads AND the ad takes up one whole row so you end up with less playing area.

Earlier this week, Steve Jobs passed away. I don’t recall the many CEO passings but it was all over the blogosphere and social media on top of being over the regular news channels. Many fans of Apple mourned him including myself. He was many things to many people. To CEOs, he was a visionary leader – able to see trends and industries well before others could. To other business leaders he was an amazing CEO, able to turn around a struggling company. To many he was an inspiration. A baby born out of wedlock, who was adopted, dropped out of college to pursue a dream, built a successful company, got fired from said successful company, start a few more (NeXT and Pixar), and went back to the original company and created wave after wave of hit products. To consumers, he was the guy who they associated with their wonderful Apple products.

What struck me was how many people mourned him. This is a man who runs a company, not a Hollywood celebrity or a rockstar. I doubt many CEOs would have this much impact when their time comes. There are so many products that are much more fundamental to our everyday lives yet we hardly think of them. For example electricity and clean water are essential necessities, but I doubt people care for say Thomas Edison or the CEO of ComEd the way they do Steve Jobs. The other CEO that I can think has this much fame would be Bill Gates who I think mostly people associated with being the richest man in the world at the time. No other person I can think of has been so closely associated with their brand. For example, I know people love their Wii or Xbox, but could they identify the creator? Probably no. People also love their cars and expensive watches, but I also highly doubt those people could identify their makers.

With every product launch Steve Jobs has been at the helm of the presentation giving every keynote until he was no longer able to physically do so. By doing that, he made him and the brand inseparable. When the products and the company became successful because of his absolute focus on quality, design and the whole user experience, he became a pop culture icon. People loved Apple products – Steve’s products, and thus they loved him.

Not only did he represent great products, he symbolized an ideal. His commencement speech at Stanford in 2005 revealed a man who believed in only doing things that mattered because life was short. In his own words, he wanted to make a dent in the universe. He believed in not living someone else’s life. I can’t imagine how this message could not resonate with most people.

What’s going to kill Facebook in the end isn’t necessarily a better social network. It’s going to come out of left field and they won’t know what hit them. Here’s an example. If you were a very popular radio station in the 1940s, you were probably very worried about new radio stations popping up and becoming more popular. What they didn’t realize is that another radio station wasn’t going to be the end of their station. Televisions were just recently introduced at the time. At the end of 1946, only 44,000 homes had a TV set; by the end of 1949,there were 4.2 million TV homes. The reason people weren’t listening to your popular station wasn’t because they had found another popular station where all the cool kids were listening to. It was because they were spending their time watching broadcast television. When video games came out, kids spent less time watching television and more time playing games. When the internet came out, more people spent time online than watching TV and playing games (some people anyways). It’s like the guy who sold horses back in the 1900s worried that people are going to buy better and faster horses from another stable when he should really be worried about this little automotive company called Ford. My point is if Google is really serious about taking down Facebook, they should be thinking about fighting them on their turf on their rules.

There are so many new apps and services now other than Facebook that are all legitimately interesting. I myself have been spending less time on Facebook and more time on services like Instagram where all people can do is post interesting photos. I also spend more time playing with iPhone apps that aren’t necessarily even social. I agree with the Gigaom article that the way to beat Facebook is death by a thousand cuts. I’m sure people spend an unhealthy amount of time playing games like CityVille or Farmville – and even though that’s still within the Facebook ecosystem, those people are spending less time on Facebook proper because of it. There are only so many hours in the day and when the next big fun thing comes out – whatever that may be, that is what’s going to take attention away from Facebook, not another social network.

Here’s a video of the talk along with my slides.

Designing for iPad by Pek Pongpaet from ChicagoRuby on Vimeo.

For more presentations from that conference, please go to the WindiCityGo website.

He even created a very cool video