User testing is often an afterthought, considered only after the design and development of an app. Our team at Savvy Apps believes in evaluating and validating your app from the outset and throughout the creation process. This allows us to iterate on what we learn and make sure your app appeals to users and meets their expectations before its launch. Without user testing, there's no way to know if you're on the right track until it's too late.
Blog Posts Related to 'Product'
In the second episode of The Savvy Apps Podcast, Ken chats with well-known app creator and Apple Design Award winner Jeremy Olson. They discuss the differences in app design, business models, market, and user expectations from the early days of the App Store to today. Now that Jeremy is at Coda, they also discuss what it's like to transition from being an indie developer to building apps within a startup.
Product management is a discipline that continues to be hard to describe and define. There are particular approaches for doing product management "the right way," which was part of my motivation for writing App Savvy. At the same time, a portion of this role simply comes from experience. That may even be truer for app product management, which as of this writing is still less than a decade old.
Many app updates focus on bug fixes, polish, tweaks, or maybe adding a smaller feature. Less frequently, a major update comes along, like an app moving from 1.0 to 2.0 or 7.0 to 8.0. For example, Instagram and Uber both saw major app updates in the past year that fundamentally altered their app experiences.
Major app updates may include a brand new user experience, new visual design, or a handful of new features. There are a number of ways to recognize if your app is due for a major update. Your app doesn't need to meet all of the following criteria to require an update. Even just one consideration may justify spending the time and effort involved. Let's take a look.
Once the first version of an app has been built in anywhere from 4-6 months the next step is to begin to maintain and support that app. The most popular apps on the app stores often see updates as frequently as weekly while other release cycles may happen once or twice a month. In this post, I'll break down how to approach app updates, balancing smaller and larger updates, and more generally accounting for different kinds of release cycles.
While it varies greatly, the general answer we provide to people asking us how long it takes to build an app is 4-6 months. That does not mean a first version of an app—a v1.0 app—can't be built faster than four months or that it won't take longer than six months. We've done both at Savvy Apps. As with any creative undertaking though, there are many factors that can influence this timeline. The remainder of this post will focus on these factors and the impact they can have on schedules.
You’ve seen the lists of “best new apps” and “top apps of the year.” What makes these apps any better than the thousands of others in app stores? What makes an app great? A catchy name and fancy animations help, but real quality comes from how well the app addresses these elements: purpose, audience, stability, and polish.