mobile-product-extension

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.