Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Growth Hacking for Mobile Product Managers

DZone's Guide to

Growth Hacking for Mobile Product Managers

No, this article won't help you get taller, but it will give you six steps you can follow to growth hack your way into mobile product management.

· Mobile Zone
Free Resource

Download this comprehensive Mobile Testing Reference Guide to help prioritize which mobile devices and OSs to test against, brought to you in partnership with Sauce Labs.

Mobile product management is taking the PM world by storm. As more companies make the transition to mobile, PMs everywhere are expanding their knowledge to encompass a new set of tools that can be applied directly to mobile products.

Although mobile is the next big thing in product management, the learning curve can be steep. Where does a PM begin their mobile journey? Through growth hacking their skills, of course!

Here are six steps to growth hack your way into mobile product management:

Change Your Mindset to Mobile-First

To take on the world of mobile product management and build world class app and mobile experiences, the only way to think is mobile-first. More specifically, you could go one step further and start thinking “screen-first” or “platform-first,” depending on your product’s needs.

As mobile continues eating the web, many companies are beginning to take on the “mobile-first” mindset as their standard for designing new products and features. Is your company mobile-first? If yes, you should already be thinking this way (but there’s always room for improvement!). If not, be the change you wish to see across your company.

Surround Yourself With Mobile

To understand what makes a good experience good, and a bad experience bad. By immersing yourself in mobile, you’ll begin to intuitively recognize product experiences that are worth emulating and will have an easier time brushing up on the basics. For example, do you know the difference between a mobile website, a hybrid app, and a native app? Now is the time to dive in and learn.

For your first quick lesson, here’s a quick explanation around the difference: There are plenty of situations where native is clearly the right choice from the beginning. Native apps are necessary when taking advantage of uniquely mobile capabilities such as a functional offline product and having a strong in-app purchase flow. You may also decide to build a hybrid app before a native app, which will allow much of the same functionality, look, and feel of a native app, but will reduce the cost and time it takes to build the app (for more on hybrid apps, check out five points to consider before deciding to go hybrid).

Become an Expert in Mobile Usability

Customer expectations shift dramatically depending on the device. Whether you help your team build for iOS, Android, tablet, wearable, or all of the above, having a deep understanding of how to use specific mobile devices will keep you a step ahead.

People have different expectations depending on what device they use to engage with your product, and knowing how to “design for mobile” in a broad way is no longer enough. The more you know about customer usability expectations, the quicker you can make data-driven product decisions.

Build an App From Scratch

Sound crazy? You’ve got this! Not only will this exercise help broaden your coding skills, it will also help you understand your development team and process at a deeper level. The more confident you are in your technical skills, the more trust your development team can put in your hands when it comes to assessing scope of work, solving challenges, ordering bug lists, etc. Plus, building an app from scratch can be tons of fun.

Check out these tutorials to help you get started:

Use Your Device Often

The best mobile product managers are always on top of new trends, and the best way to see what’s hot or not is to use your device(s) as often as you can. If you can’t explain what makes your favorite apps great from a technical, marketing, and product perspective, chances are you have some learning to do. The more you challenge what you like and dislike in the mobile experiences you use consistently, the better it will translate to how you build your product.

Additionally, it’s important to experience parity on the platform you are developing for. You can’t be a good mobile PM if your product runs on Android, but you haven’t used Android as your primary personal mobile platform for at least three months in the past couple years, and that goes for iOS as well. In order to build the best product for the platform you choose, you must be as familiar with it as possible.

Read

All the time. Every day. As much as you possibly can. Here are a few product and mobile-focused blogs recommended by your peers:

I hope these steps give you a starting point to boost your mobile product management skills. Have additional growth hacking tips to share? Let’s discuss it in the comments section!

Analysts agree that a mix of emulators/simulators and real devices are necessary to optimize your mobile app testing - learn more in this white paper, brought to you in partnership with Sauce Labs.

Topics:
app ,experiences ,platform ,management

Published at DZone with permission of Kendrick Wang, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}