metodologia-mobile-architecture

Analyze mobile architecture decisions for iOS and Android projects.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-mobile-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metodologia-mobile-architecture
Source: https://github.com/JaviMontano/metodologia-propuesta-agent-public/tree/main/.claude/skills/architecture/mobile-architecture
Command: npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-mobile-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Mobile apps require thoughtful platform decisions, scalable architectures, offline readiness, and reliable release processes. This Skill provides a structured approach to choosing between native, cross-platform, and hybrid options, and to planning release pipelines.

Core Features & Use Cases

  • Platform decision matrix comparing Native, Flutter, React Native New Architecture, and KMP/CMP for code sharing, UI fidelity, and team fit.
  • App architecture patterns guidance (MVVM, MVI, Clean Architecture, BLoC/Redux) and modularization strategy.
  • Offline-first design and data synchronization patterns, conflict resolution, and background tasks.
  • Performance budgeting, accessibility, and release pipeline planning (CI/CD, app store readiness).

Quick Start

Provide the app or project name and I will generate the platform decision matrix, architecture plan, and release roadmap.

Frequently Asked Questions about metodologia-mobile-architecture

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

FAQPage Schema
How do I choose between native, Flutter, React Native, and KMP for mobile app architecture?

To choose a mobile app architecture, you need a platform decision matrix comparing Native, Flutter, React Native New Architecture, and KMP/CMP across code sharing, UI fidelity, and team fit to find the best match for your project requirements.

What is the best way to plan an offline-first data synchronization strategy for mobile apps?

Planning an offline-first data synchronization strategy requires defining conflict resolution rules, background task scheduling, and data sync patterns to ensure local data availability and seamless background synchronization when network connectivity is restored.

How do I structure a modular mobile architecture using MVVM or MVI?

Structuring a modular mobile architecture involves applying patterns like MVVM, MVI, Clean Architecture, or BLoC/Redux to separate concerns, define module boundaries, and ensure scalable, maintainable codebases for iOS and Android applications.

Can I use this approach to plan both mobile app architecture and CI/CD release pipelines together?

Yes, you can plan both mobile app architecture and CI/CD release pipelines together by defining performance budgets, accessibility targets, and app store readiness workflows to ensure reliable continuous integration and delivery for iOS and Android.

What are the limitations of cross-platform mobile architecture compared to native development?

Limitations of cross-platform mobile architecture include potential trade-offs in UI fidelity, platform-specific performance budget constraints, and the need for specialized bridge implementations when accessing native iOS or Android device capabilities.

When do I need a performance budget for my mobile application?

You need a performance budget for your mobile application when defining architecture patterns and release pipelines, ensuring the app meets specific optimization targets for load times, frame rates, and memory usage across iOS and Android devices.