mobile-product-extension

Assess mobile app changes for lifecycle, offline, permission, and privacy correctness.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/machenjie/rd-skills --skill mobile-product-extension
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile-product-extension
Source: https://github.com/machenjie/rd-skills/tree/main/src/domain-extensions/mobile-product-extension
Command: npx skills add https://github.com/machenjie/rd-skills --skill mobile-product-extension

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Mobile change work often breaks when the app goes offline, the OS suspends or terminates processes, permissions are denied, or platform privacy and store requirements are missed—leading to data loss, crashes, and app rejections.

Core Features & Use Cases

  • Lifecycle + offline-first correctness: designs state preservation, pending queues, and sync conflict handling so user data is not lost across app lifecycle transitions.
  • Permission and push notification flow safety: ensures permission-denied UX is treated as a first-class product path and validates deep links from notifications to prevent misrouting and crashes.
  • Security, privacy, and store readiness: verifies secure credential storage (Keychain/Keystore), certificate pinning, iOS Privacy Manifest accuracy, and Play Store Data Safety completeness.

Quick Start

Use this skill to assess whether a proposed Android and iOS change correctly handles offline behavior, permissions, notification deep links, performance, and store/privacy requirements.

Frequently Asked Questions about mobile-product-extension

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent data loss when an app goes offline or the OS suspends processes?

To prevent data loss during offline states or OS suspensions, evaluate mobile changes for lifecycle and offline-first correctness by designing state preservation, pending queues, and sync conflict handling across app lifecycle transitions.

How do I handle permission-denied UX in iOS and Android apps?

Handle permission-denied UX by validating it as a first-class product path. Assess mobile changes to ensure push notification flows and deep links from notifications prevent misrouting and crashes when permissions are denied.

What do I need to check for iOS Privacy Manifest and Play Store Data Safety compliance?

For iOS Privacy Manifest and Play Store Data Safety compliance, verify secure credential storage using Keychain or Keystore, validate certificate pinning, confirm privacy manifest accuracy, and ensure Data Safety form completeness to avoid store rejections.

How do I validate deep links and universal links to prevent crashes from push notifications?

Validate deep links and universal links by enforcing push routing validation checks. Assess mobile changes to ensure deep links from notifications route correctly across app lifecycle states, preventing misrouting and crashes.

Does this mobile assessment support cross-platform and native iOS/Android scenarios?

Yes, this mobile assessment applies to native iOS/Android and cross-platform mobile scenarios. It evaluates lifecycle transitions, background execution, offline sync, and permission request updates across these platforms.

What are the common reasons mobile app changes get rejected by app stores?

Mobile app changes get rejected due to missing privacy manifest accuracy, incomplete Play Store Data Safety forms, insecure credential storage, or lacking certificate pinning. Verify security and privacy gates to ensure store readiness.