# Build Modern Mobile Applications

Mobile projects require careful choices across platforms, architecture, performance, testing, security, and distribution. This skill provides focused guidance for planning and implementing production mobile applications.

## Install

```bash
npx skillstore add sickn33/mobile-developer
```

## Metadata

- Status: approved
- Slug: sickn33-mobile-developer
- Skillstore revision: r2
- Version status: missing
- Tree hash: 98f4b423671f44499f87e63b5b3796587917a98c5f65186ca0018aa2cb33f82d
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/mobile-developer
- Ref: 81e05e636292629114b76cbb3922fbe57672fc02
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-mobile-developer
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-mobile-developer/manifest

## Capabilities

- Compare React Native, Flutter, and native platform approaches for specific product and team constraints.
- Design maintainable mobile architectures using clean architecture, MVVM, MVI, repositories, and dependency injection.
- Plan offline storage, background synchronization, caching, and conflict resolution workflows.
- Guide native integrations for authentication, notifications, payments, cameras, sensors, maps, and secure storage.
- Recommend testing, performance profiling, security controls, continuous delivery, and app store release practices.
- Support migrations involving React Native architecture, Xamarin replacements, and platform-specific native modules.

## Use Cases

- Choose a Mobile Stack: Compare platform options against product requirements, team experience, native integration needs, performance targets, and delivery constraints.
- Improve an Existing Application: Diagnose architecture, startup, rendering, memory, networking, offline behavior, and test coverage before planning focused improvements.
- Prepare a Reliable Release: Plan testing, signing, automation, observability, privacy disclosures, staged rollout, and store submission for iOS and Android.

## Prompt Templates

### Select a Framework

```
Compare React Native, Flutter, and native development for [product]. Consider [team skills], [required integrations], [performance needs], and [delivery date]. Recommend one approach.
```

### Design the Architecture

```
Design a mobile architecture for [application]. Include modules, state management, navigation, data access, error handling, testing boundaries, and platform-specific components.
```

### Plan Offline Synchronization

```
Create an offline-first synchronization strategy for [data model]. Cover local storage, queueing, retries, conflicts, authentication expiry, background limits, and recovery testing.
```

### Audit Production Readiness

```
Audit this [React Native, Flutter, iOS, or Android] application for production. Assess performance, security, accessibility, observability, testing, signing, privacy, and staged release risks.
```

## Limitations

- The skill does not replace testing on actual devices, operating system versions, and network conditions.
- Platform APIs, store policies, and framework versions may change after the skill content is published.
- Production signing, store submission, and third-party service setup require valid accounts, credentials, and project access.
- Security, privacy, payment, and compliance decisions still require project-specific review.

## Best Practices

- State platform targets, framework versions, device constraints, integrations, and measurable success criteria before requesting an implementation.
- Validate recommendations with profiling, automated tests, accessibility checks, and representative physical devices.
- Review security, privacy, permissions, background behavior, and store requirements before release.

## Anti Patterns

- Do not choose a cross-platform framework without evaluating required native APIs, team skills, and long-term maintenance.
- Do not treat simulator results as proof of performance, battery use, permissions, or hardware behavior.
- Do not place secrets in application bundles, source code, local storage, logs, or client-controlled configuration.

## Security Audit

- Audited at: 2026-08-04T14:38:52.237\+00:00
- Summary: All four static findings are false positives caused by Markdown formatting or ordinary mobile-development terminology. No command execution, reconnaissance behavior, prompt injection, or malicious intent is present.

## Stats

- Views: 124
- Downloads: 19
- Favorites: 1
- Popularity score: 0