Consumer Mobile Security & Safety Portfolio

Problem

The portfolio addressed device security, personal safety, and family-monitoring needs across several mobile applications and audiences.

My Role

I owned product direction and lifecycle priorities across the portfolio, from discovery and requirements to release and post-launch optimization. I worked with design, engineering, and QA on delivery.

Product decision

I treated the apps as a portfolio, sharing patterns and audience insight across security, safety, and family-monitoring products.

Constraint

Prioritization had to account for different audiences and use cases across security, safety, and family-monitoring products.

Process

• Treated the apps as a portfolio rather than isolated launches, so device-security, safety, and family-monitoring products could share patterns and audience insight.
• Shaped behavior-triggered recommendations and alerting workflows — device-performance optimization suggestions, fall detection, and parental controls with location tracking and geofencing.
• Used behavioral analytics, user feedback, and in-product signals to decide what to build next and which improvements to prioritize.
• Ran discovery, requirements, prototyping, UI/UX, testing, and release management with design, engineering, and QA.
• Outlined go-to-market strategy for each launch, focused on retention, engagement, and conversion rather than install counts alone.

Outcome

Six products launched in two years, contributing to 30% year-on-year revenue growth and achieving 40% product adoption. The portfolio reached 100K+ users and was recognized twice with The Popular Apps Award, once as an App of the Day, and once as a Fierce Innovation Award finalist.

Takeaway

A portfolio approach creates opportunities to reuse patterns and audience insight, while keeping each product’s user needs visible in prioritization.