APPO: After the initial buzz (including exhibiting at Google’s I/O Conference) of a new release wears off, how do you plan to maintain momentum and drive downloads of the app over time?

WB: We believe it starts with building a great product. We also have dozens of new features planned that our agile team can release quicker than larger competitors. By constantly releasing smart features that make our users’ lives easier, we hope to deliver traffic growth through word of mouth. Additionally, we have started conversations with several exciting partners for distribution.

APPO: DayZipping is a free app to download. What is your business model, and how do you plan to make money?

WB: We aren’t quite there yet, but we’ve had some great discussions with local venues about working on a referral basis or providing group purchasing discounts. We are mainly focused on getting the product right at this point though.

APPO: Describe how the app integrates with the website.

WB: The mobile app integrates with a powerful REST API that is designed from the ground up for scale. We’re currently working on tying in our suggestions engine for mobile users as well. This will allow us to generate personalized suggestions even when you’re in a new city. This functionality is slated for release later this summer.

APPO: Do you plan to launch an iOS app (and/or an app on any other mobile platform)?

WB: We have an iOS app in the works and plan to be in the App Store by the end of the summer.

APPO: As a developer somewhat new to mobile media, what are the three biggest things that keep you up at night?

WB: There are numerous glaring differences between web and mobile development that come to mind. The three things that stand out the most are:

1) different specs across hundreds of devices makes it virtually impossible to test all potential configurations (including different DPIs, platforms, etc.).

2) our users need to be able to view rich media, this can be tricky when network connections are often unreliable

3) limited memory relative to desktop development has forced us to consider architecture and memory management much more than we have grown used to over the last several years.