AA Grapevine & La Viña Apps

The challenge was coordinating four related apps, two languages, a large content archive, subscriptions, and a recurring audience across their release cycles. Accessibility, store coordination, and consistent behavior across platforms were part of every release.

I helped guide product and technical delivery for four apps serving an established audience across iOS and Android.

• 20K+

  monthly active users

  The apps serve a broad, recurring audience.

• 4.7★

  app-store rating

  The products held strong public ratings while serving a broad and recurring audience.

• 4

  apps delivered

  Four live products across AA Grapevine and La Viña, each with its own release and support surface.

• 70+ years

  of archive content

  Subscriptions and a long-running archive add operational and content-delivery complexity.

I helped lead delivery across product scope, coordination, and release work:

• Cross-functional coordinationAligned engineering, QA, stakeholders, and release timing across four related mobile products.
• Scope and roadmap translationTurned stakeholder goals into execution-ready work while keeping iOS and Android parity in view.
• Technical delivery leadershipStayed close to implementation and release details so product decisions remained grounded in platform reality.
• Quality and rollout disciplineKept releases synchronized across stores, subscriptions, archive content, and multilingual surfaces.

A few constraints defined the delivery work:

• Four-store release surfaceChanges had to work across iOS and Android, English and Spanish, without the products drifting apart.
• Archive and subscription continuityThe app experience had to respect a paid content library, subscription state, and long-lived reader expectations.
• Accessibility-first audienceThe user base demanded clarity, readability, and a low-friction reading experience over novelty.
• Steady releasesThe apps needed careful coordination and incremental improvements across a long-lived product.

• Scale changes the PM jobAt this audience size, release coordination, QA discipline, and stakeholder alignment matter as much as any single feature call.
• Leadership needs technical fluencyThe most useful product decisions came from staying close to the platform constraints instead of treating engineering as a black box.
• Accessibility is part of the product promiseFor this audience, clarity and readability are not polish items; they are core to whether the software is genuinely usable.
• Consistency mattersLong-lived content apps benefit from dependable release habits and measured interface changes.