mobile-development

Design iOS and Android mobile architectures with MVVM and Clean Architecture.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/vuminhieu/spexor-client --skill mobile-development-vuminhieu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile-development
Source: https://github.com/vuminhieu/spexor-client/tree/main/.agent/skills/skills/mobile-development
Command: npx skills add https://github.com/vuminhieu/spexor-client --skill mobile-development-vuminhieu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams navigate the complexities of mobile development by consolidating best practices, design patterns, debugging strategies, performance guidelines, and platform-specific guidelines for iOS and Android, enabling faster delivery of reliable mobile apps.

Core Features & Use Cases

  • Architecture guidance: MVVM, Clean Architecture, and modular structures tailored for mobile teams.
  • Performance & UX budgets: Establish and enforce launch times, memory limits, network efficiency, and smooth animations.
  • Platform guidelines & best practices: iOS HIG, Material You, accessibility, security basics, and deployment readiness.
  • Debugging & testing strategies: Cross-platform tooling, instrumentation, unit/integration/UI tests, and real device testing.
  • Use cases: Teams deciding between native vs cross-platform, selecting frameworks (React Native, Flutter, native), and planning offline-first architectures.

Quick Start

Start by reading the core concepts in the skill, then use the decision framework to pick the right mobile approach for your project. Then run a quick assessment by asking: "What is the best architecture for a new cross-platform mobile app with offline-first requirements?"

Frequently Asked Questions about mobile-development

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

FAQPage Schema
What is the best architecture for a new cross-platform mobile app with offline-first requirements?

Mobile architecture patterns like MVVM and Clean Architecture separate business logic from UI layers. This modular approach enforces performance budgets and ensures maintainable codebases across native and cross-platform iOS or Android applications.

How do I decide between native and cross-platform mobile frameworks?

Use a cross-platform decision framework to evaluate team expertise, app complexity, and performance budgets. This framework contrasts native iOS/Android capabilities against shared codebases to determine the optimal development approach for your enterprise project.

How do I establish performance budgets for mobile applications?

Mobile performance budgets are established by setting strict limits on app launch times, memory usage, network efficiency, and animation smoothness. Enforcing these constraints during development ensures reliable user experiences across iOS and Android devices.

Does this mobile development approach support iOS HIG and Material Design guidelines?

Yes, the approach integrates platform-specific guidelines for both iOS HIG and Material Design. It ensures mobile apps meet native accessibility standards, security basics, and deployment readiness requirements for their respective app stores.

What are the limitations of offline-first mobile architectures?

Offline-first mobile architectures introduce complexities in local data synchronization, conflict resolution, and increased storage management. These limitations require robust debugging workflows and comprehensive integration testing on real devices to ensure data integrity.