mobile_skill

This skill helps you develop mobile apps across iOS, Android, and cross-platform frameworks with best practices and architecture guidance.

Python

5

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill truongnat/agentic-sdlc --skill mobile

SKILL.md1.9 KB

Overview

This skill represents the Mobile Developer role responsible for iOS, Android, and cross-platform mobile applications. It focuses on delivering production-ready apps with platform-consistent UX, reliable offline behavior, and optimized performance. Activate this role when mobile-specific design, architecture, testing, or release guidance is needed.

How this skill works

The skill inspects requirements and maps them to platform-appropriate solutions: Swift/SwiftUI or UIKit for iOS, Kotlin/Jetpack Compose for Android, and React Native or Flutter for cross-platform needs. It recommends architectures (MVVM, MVI, Clean), patterns (repository, DI), testing strategies, and release steps for App Store and Google Play. It also evaluates mobile-specific concerns like offline-first behavior, battery optimization, deep linking, and accessibility.

When to use it

Planning or scoping a new iOS, Android, or cross-platform app
Designing mobile app architecture, data layer, or dependency injection
Implementing offline support, push notifications, or deep linking
Preparing release pipelines and store submissions for App Store/Play Store
Creating test matrices for device/emulator coverage and UI tests

Best practices

Follow platform guidelines (HIG for iOS, Material for Android) for consistent UX
Use Clean Architecture and repository patterns to separate concerns
Prefer DI frameworks (Hilt/Koin or Swift DI) and typed APIs, never hardcode endpoints
Build offline-first flows and handle sync/backoff to preserve battery and data
Test on multiple device sizes and include accessibility and biometric scenarios

Example use cases

Choose between SwiftUI and UIKit for a feature while maintaining legacy support
Design a shared business logic layer for React Native or Flutter with native modules
Set up unit, UI, and snapshot testing across XCTest, Espresso, and Detox
Optimize app startup and background work with WorkManager or background tasks
Prepare CI/CD steps with DevOps for automated builds, signing, and store submission

FAQ

Choose cross-platform when time-to-market and shared business logic matter; pick native when platform-specific performance, UI fidelity, or advanced native APIs are required.

How do I ensure offline reliability?

Adopt an offline-first architecture with local persistence (Core Data/Room), queued sync, conflict resolution, and exponential backoff for network retries.