mobile-development

Verify mobile engineering changes across Apple platforms, Android, and cross-platform runtimes.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/Blaze-sports-Intel/uber-engineer --skill mobile-development-blaze-sports-intel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile-development
Source: https://github.com/Blaze-sports-Intel/uber-engineer/tree/main/plugins/uber-engineer/skills/mobile-development
Command: npx skills add https://github.com/Blaze-sports-Intel/uber-engineer --skill mobile-development-blaze-sports-intel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents “build success” from being mistaken for “shipped and working” by enforcing a platform-specific shipping ladder for iOS/iPadOS/macOS/visionOS/watchOS/tvOS, Android, and major cross-platform stacks.

Core Features & Use Cases

  • Apple-platform shipping ladder: clean local builds, real device installs, Xcode Cloud distribute workflows, TestFlight processing state checks, and install-list verification before claiming done.
  • Android + release hygiene: Gradle/variant correctness, physical-device validation, Compose + accessibility checks, and Play Console pre-launch plus rollout discipline.
  • Cross-platform release and bridging choices: stack selection (native vs React Native/Expo vs Flutter), EAS build/channel OTA update testing, and native escape-hatch bridging when runtimes reach limits.

Quick Start

Use /mobile to plan and verify an iOS/Android or cross-platform change through the on-device and store readiness steps for your targeted release.

Frequently Asked Questions about mobile-development

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

FAQPage Schema
How do I verify an iOS build passes on-device before claiming it is done?

To verify an iOS build passes on-device, follow a platform-specific shipping ladder: clean local builds, real device installs, Xcode Cloud distribute workflows, TestFlight processing state checks, and install-list verification before claiming done.

What is the best way to prepare an Android app for Play Console rollout?

Prepare an Android app for Play Console rollout by ensuring Gradle/variant correctness, physical-device validation, Compose and accessibility checks, and pre-launch report discipline before starting the rollout.

Does mobile shipping verification support cross-platform runtimes like React Native and Flutter?

Mobile shipping verification supports cross-platform runtimes like React Native, Expo, and Flutter by testing EAS build/channel OTA updates and providing native escape-hatch bridging when runtimes reach their limits.

How do I test offline-first data handling and concurrency-safety for mobile features?

Test offline-first data handling and concurrency-safety for mobile features by applying platform-specific verification ladders that capture evidence, rollback paths, and strict concurrency, accessibility, and privacy checks.

Why does my build success not guarantee the mobile feature works on a physical device?

Build success does not guarantee a mobile feature works on a physical device because store-verified outcomes require real device installs, background and push behavior validation, and deep-link authentication flow checks.

When do I need to check TestFlight processing states for an Apple platform release?

Check TestFlight processing states for an Apple platform release during the store review or rollout preparation phase to ensure on-device and store-verified outcomes before claiming the shipping ladder is complete.