An important part of your role as a mobile product manager will be to understand exactly why your customers are using your app, what they absolutely need it for, and what they can do without.
To make a successful mobile app, you’re going to have to unleash your inner-minimalist.
You’ve gotta be a portrait artist and a landscaper
Your colleagues who manage the desktop version of your product can’t empathize with you on this challenge. They don’t have to worry about what’ll happen if a user suddenly picks up his computer monitor and turns it on its side.
But you do. For every screen you develop, and every feature, text blurb or action you include in your app, you need to make sure the user will have a great experience regardless of how her device is oriented.
And yes, both versions of the user experience — portrait and landscape — need space and time on your mobile product roadmap.
You’ve gotta be ready to handle massive success right away
When the product manager of a desktop app (or fitness equipment or just about any other type of product) launches her product into the market, she and her team have a lot of work to get the word out about it. This is usually a slow process, which is why most products don’t become mega-monster-super-duper successes right out of the gate.
When you release your mobile app, on the other hand, in addition to your own app rollout marketing you will have at least a little professional help—because you’ll be launching it through one or more of the app stores, and those platforms get zillions of searches every day.
And if your app goes viral on day one, but your team isn’t ready to support that kind of traffic and the user experience suffers as a result, you could be saying goodbye top—and even creating vocal critics out of—what could have been some of your best customers.
All of which is to say that when you’re launching a mobile app, assume it could be swamped with traffic in the first minutes after it hits the app stores. Now ask yourself, have we built the infrastructure (servers, customer support team, etc.) to handle that great news?
You’ve gotta budget additional resources for app-store submissions
There’s also a flipside to the advantage of being able to offer your mobile app through a massive platform like the App Store: You’ll need to submit it to the store(s) for approval, and this requires some work.
Generally, the major platforms (the App Store, Google Play) give the thumbs up to new apps relatively quickly—often within just days. But getting everything in order to make sure your app glides through the application process and has all of the technical infrastructures it needs for a successful download and sale on these platforms will require some development cycles.
So, for a new app you’re rolling out, the app store submission process also needs some time on your mobile product roadmap.
You’ve gotta be ready to defend your decisions with clear data
The great thing about a service is that it gives you actionable information—not just numbers of user clicks or swipes, but the real story behind that user data—to help you make smart decisions about how to continually improve your app.
And you’ll need that actionable information because in your roadmap meetings you’re going to hear a lot of opinions. We all use apps every day, after all, so you can expect pretty much everyone on your cross-functional team to have an opinion about what to prioritize, what a screen should look like, what to streamline, what functionality needs to match the full desktop version exactly—you name it.
Real-world data will make for a more compelling product roadmap, which makes for better team alignment on your strategic plan.
This article originally appeared in AppSee. This article was written by Andre Theus from Business2Community and was legally licensed through the NewsCred publisher network. Please direct all licensing questions to firstname.lastname@example.org.