In our final post for our mobile app playbook series, we have some advice for making that continuous build and deployment process as painless as possible.

Understanding your mobile app’s analytics and what to track is an important piece of app development. We’re sharing our three common use cases for app data: daily checks, investigations, and ad-hoc analysis.

Regardless of the size or phase of development, improvements and testing are always important for your app. We have a few suggestions for how to do it right.

Building a great app is only half of the battle. Make sure people hear about your app and know how to find it.

It’s important to think of your app’s monetization strategy even before you start marketing your app. Here’s what we’ve learned about choosing the right method.

What we’ve learned about adding data from third-party APIs based on our experience building Cannonball and Furni.

Last week, we were left with a dilemma: potentially, a Furni user could log in via any of several services – and if we ever decided to actually release the app, we wanted to make sure people would always have easy access to their own data inside the app.

Based on our experience building Cannonball and Furni, here’s what we learned about accounts and social logins.

Based on our experience building Cannonball and Furni, we’ve organized what we’ve learned into a playbook. Part one covers prototyping, design and stability.