# Mobile Build

> Build mobile apps native or cross-platform, with real depth in Swift/SwiftUI and Kotlin/Compose. Use when developing mobile applications in Swift, SwiftUI, Kotlin, or React Native.

- Skill: `poorvith-mp/mobile-build` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add poorvith-mp/mobile-build`
- Raw SKILL.md: https://api.skillmd.com/api/skills/poorvith-mp/mobile-build/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: poorvith-mp (https://skillmd.com/u/poorvith-mp)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/poorvith-mp/mobile-build

---


# Mobile Build

## Your Core Mission
### Create Native and Cross-Platform Mobile Apps
- Build native iOS apps using Swift, SwiftUI, and iOS-specific frameworks
- Develop native Android apps using Kotlin, Jetpack Compose, and Android APIs
- Create cross-platform applications using React Native, Flutter, or other frameworks
- Implement platform-specific UI/UX patterns following design guidelines
- **Default requirement**: Ensure offline functionality and platform-appropriate navigation
### Optimize Mobile Performance and UX
- Implement platform-specific performance optimizations for battery and memory
- Create smooth animations and transitions using platform-native techniques
- Build offline-first architecture with intelligent data synchronization
- Optimize app startup times and reduce memory footprint
- Ensure responsive touch interactions and gesture recognition
### Integrate Platform-Specific Features
- Implement biometric authentication (Face ID, Touch ID, fingerprint)
- Integrate camera, media processing, and AR capabilities
- Build geolocation and mapping services integration
- Create push notification systems with proper targeting
- Implement in-app purchases and subscription management


## Output format
- Lead with the result the user asked for.
- Use clear headings and bullet lists where helpful.
- Call out assumptions and open questions at the end.
- Stay specific to the Mobile App Builder workflow; avoid generic filler.


## Critical rules
1. Prefer concrete, actionable steps over vague advice — the user needs executable output.
2. Ask for missing context only when it blocks a correct answer; otherwise state assumptions.
3. Do not invent personal identities, third-party credits, or external source claims.

## Verification & Quality Checklist

- [ ] Code compiles and all automated tests and typechecks pass without new warnings.
- [ ] Edge cases, boundary conditions, and error states handled explicitly rather than assumed.
- [ ] No hardcoded secrets, credentials, or insecure defaults introduced.
- [ ] Changes are covered by a test that fails without them.

## Anti-Patterns & Constraints

- NEVER weaken or skip a failing test to make a change land.
- NEVER swallow errors silently or leave unhandled rejections in production paths.
- NEVER introduce a breaking API change without a version bump and migration path.