5 Lessons I Learnt as an App Product Manager

With a checklist that assists me in considering all aspects.

4 min readNov 10, 2023

Stepping into the role of a product manager is never straightforward. If you’re embarking on a career in product management, especially in mobile Apps. I hope my insights can help shorten your learning curve.

1 Understanding the Interplay of Backend and Frontend is Essential

As a product manager, coding expertise isn’t necessary, but a basic understanding of backend and mobile technology is vital. For instance, I once thought app push notifications were solely a mobile feature, similar to sending a text message. However, I soon learned that they’re predominantly controlled by backend systems — triggers, rules, and services included. Another personal example involved developing a text-heavy app screen. It seemed straightforward until I realised the dynamic nature of the content, which needed regular updates. Without backend involvement, updating such content becomes a complex task.

2 Localisation and Translation Require Attention

If your product is intended for multiple countries or languages, localisation and translation are unavoidable aspects. Having a dedicated copywriter for each language your product serves is a luxury. As a product manager, factoring in the time for accurate translations is crucial. This may involve waiting for assistance from a company colleague or explaining the context to a temporary translator. Always allocate a generous time buffer for translation tasks!

3 Don’t Forget About Your Existing Users

Introducing new features demands consideration of their impact on current users. This is especially true when addressing issues faced by new users. For example, integrating a new login and onboarding flow with a PIN system for first-timers sounds great, but what about existing users? The challenge lies not just in the solution itself but in operational costs and potential future administrative issues. Could this increase customer support queries? Might it annoy existing users? What backup plans are in place for those who fail to set up new features?

4 Cater to Users on Older App Versions

One of the major mindset shifts I experienced in mobile app management is acknowledging that not all users will have the latest version. Unlike web or desktop products that update automatically online, app users often remain on older versions. When launching significant updates, consider how they will affect these users. For instance, how will new login procedures or payment methods impact those who haven’t updated the app? Sometimes, waiting until a significant number of users have the latest version is necessary before fully implementing new features.

5 Be Mindful of App Motions, Sounds, and Haptics

The underlying technology in mobile development is fairly standard across iOS and Android platforms. Any impressive feature seen in an app can be replicated through coding. I’ve developed a habit of capturing screenshots or recording specific flows, motions, or animations. Over time, I’ve noticed that well-timed haptics can effectively prompt user actions. However, before suggesting mimicking certain features, it’s important to understand the ‘WHY’ behind them. Why was a particular flow designed this way? What purpose does a specific haptic serve? Understanding these reasons is key to successful implementation.

Here’s my checklist that assists me in considering all aspects.

[ ] We need to create new API endpoints?
[ ] How many new API endpoints are needed?
[ ] We need to update existing API endpoints?
[ ] How many existing API endpoints have to be updated?
[ ] If new API endpoint is needed, should be restricted or unrestricted endpoint?
[ ] Is it possible to affect the performance of the system?
[ ] What users it affects? Employer / Employee / Site / All
[ ] Do the users require specific priviledge(s) to use the feature?
[ ] Is the feature configurable from Admin UI? (Employer/Admin can enable it/change default values)
[ ] Is this feature visible in mobile APP?
[ ] Is this feature visible in WEB APP?
[ ] Is this feature visible in Admin UI?
[ ] Is the feature testable in DEV env?
[ ] Is the feature testable in Pre-prod env?
[ ] Can the tests be automated?
[ ] Is the UI design already available in FIGMA?
[ ] Does the feature require DB migration(s)?
[ ] Have we implemented a similar feature before?