Product Analyst – Mobile Apps (Research, UX & Product Validation)

Product Analyst Mobile Apps

Research, UX & Product Validation

Location:

Marol, Andheri East, Mumbai

Work Mode:

In-Office

Employment Type:

Full-time

Experience:

35 years

About the Role

We are looking for a research-driven and hands-on Product Analyst Mobile Apps who can identify what we should build, translate research into clear product journeys, and validate whether the final feature delivers the intended customer outcome.

You will work on consumer mobile applications involving GPS, maps, location services, offline downloads, audio, payments, and travel experiences.

This role follows an 80/10/10 model:

• 80% Competitor, market and product research
• 10% UX documentation and wireframing
• 10% Product-acceptance testing and validation

You will follow features across the complete product lifecycle:

• Research
• Recommend
• Document
• Wireframe
• Test
• Validate
• Measure

80% Competitor, Market and Product Research

• Regularly download, use, and analyze competing and best-in-class iOS and Android applications.
• Map complete journeys covering onboarding, discovery, purchase, activation, engagement, retention, upselling, and support.
• Study competitor features, navigation, pricing, paywalls, permissions, notifications, error handling, and monetization strategies.
• Monitor App Store and Play Store trends, ratings, reviews, releases, and customer feedback.
• Use tools such as [REDACTED], [REDACTED], [REDACTED], [REDACTED], or equivalent research platforms.
• Analyze internal mobile funnels, cohorts, conversion rates, retention, and customer drop-off points.
• Use [REDACTED], [REDACTED], Firebase Analytics, GA4, [REDACTED], or equivalent analytics tools.
• Compare performance across iOS, Android, app versions, products, geographies, and acquisition channels.
• Combine competitor intelligence, customer feedback, support issues, and internal data to identify product opportunities.
• Prioritize opportunities based on customer value, business impact, evidence, complexity, risk, and strategic relevance.
• Present clear recommendations explaining what should be built, why it matters, and how success should be measured.
• Maintain an organized repository of competitor screenshots, journeys, benchmarks, findings, and recommendations.

10% UX Documentation and Wireframing

• Convert approved opportunities into concise feature briefs.
• Define the problem, target user, supporting evidence, proposed solution, scope, exclusions, business rules, dependencies, risks, and success metrics.
• Create end-to-end user journeys covering primary, alternate, empty, loading, error, offline, permission, interruption, and recovery states.
• Produce low- or medium-fidelity mobile wireframes using [REDACTED], FigJam, [REDACTED], [REDACTED], or similar tools.
• Annotate wireframes with user actions, navigation behaviour, validations, system responses, and analytics requirements.
• Write lightweight user stories and clear acceptance criteria.
• Define the features Definition of Ready and Definition of Done.
• Conduct a structured handoff to Product Managers, designers, developers, and QA.

This role owns the user journey and feature logic, not polished visual UI design.

10% Product-Acceptance Testing and Validation

• Convert requirements, wireframes, business rules, and acceptance criteria into feature-level test scenarios and test cases.
• Personally test new features on iOS and Android development, staging, beta, and release-candidate builds.
• Perform functional, exploratory, usability, interruption, and end-to-end customer-journey testing.
• Test relevant conditions such as poor connectivity, offline usage, app relaunch, permission changes, GPS inaccuracies, audio interruption, deep links, payment failures, and incomplete downloads.
• Validate that analytics events and properties fire correctly.
• Report defects with clear reproduction steps, expected and actual results, screenshots, recordings, and environment details.
• Classify issues by severity, priority, customer impact, and release risk.
• Retest fixes and perform focused regression around the affected feature.

Recommend whether a feature is:

• Ready for release
• Ready with accepted limitations
• In need of additional fixes
• Not ready for release

Monitor feature adoption, customer feedback, conversion, and errors .