mobile-hybrid-application-development

Implement cross-platform shared-code applications with platform bridges and test matrices.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill mobile-hybrid-application-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile-hybrid-application-development
Source: https://github.com/FernanSuoza/AIDD-project-bootstrap/tree/main/templates/skills/mobile-hybrid-application-development
Command: npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill mobile-hybrid-application-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams implement cross-platform or shared-code applications that must operate across web, native, and desktop environments while keeping platform-specific behavior explicit and controlled, reducing duplicated effort and platform drift.

Core Features & Use Cases

  • Shared vs platform-specific separation: Define what belongs in shared business logic, shared UI, and platform adapters before coding.
  • Bridge and adapter patterns: Provide clear contracts and error handling for native bridges (e.g., LocationProvider, FileStore, PushNotifications).
  • Cross-platform testing and performance: Establish test matrices, run unit/integration/E2E across targets, and optimize bundle size and startup time.
  • Use Case: Implement a camera upload flow where a shared orchestrator coordinates permissions, platform bridge calls, validation, and upload while recording design decisions in the story.

Quick Start

Run the mobile-hybrid-application-development skill to implement a minimal shared-code feature across the specified platforms, test the shared and platform paths, and record the platform-specific decisions in the story.

Frequently Asked Questions about mobile-hybrid-application-development

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

FAQPage Schema
How do I separate shared business logic from platform-specific code in cross-platform apps?

Cross-platform shared-code applications separate shared business logic, shared UI, and platform adapters before coding to keep platform-specific behavior explicit. This separation reduces duplicated effort and prevents platform drift across web, native, and desktop environments.

How do I set up native bridge contracts for hybrid apps using React Native or Capacitor?

Native bridges in hybrid apps require clear contracts and error handling for adapters like LocationProvider, FileStore, and PushNotifications. Defining these bridge and adapter patterns ensures reliable communication between shared code and platform-specific capabilities.

What's the best way to test cross-platform features across web, native, and desktop targets?

Cross-platform testing requires establishing test matrices to run unit, integration, and E2E tests across all specified targets. This verifies both shared code paths and platform-specific paths function correctly before feature delivery.

Does this hybrid app approach work with Flutter and Electron for shared feature delivery?

Yes, this approach applies to React Native, Flutter, Capacitor, Electron, and Tauri stacks for stories requiring shared business logic. It reconciles web, native, and desktop boundaries to deliver features consistently across platforms.

How do I optimize bundle size and startup time for hybrid applications?

Hybrid application performance optimization targets bundle size and startup time alongside cross-platform testing. By profiling shared code and platform-specific paths, teams identify bottlenecks and document design decisions that improve runtime performance.

When should I not use a shared-code architecture for cross-platform development?

Shared-code architecture becomes problematic when platform-specific behavior cannot be explicitly controlled through bridge interfaces or adapters. If requirements demand heavily divergent native capabilities with minimal shared logic, bridge complexity may outweigh duplication benefits.