mobile-developer
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.
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "mobile-developer" from https://skillstore.io/skills/sickn33-mobile-developer.md and its manifest at https://skillstore.io/api/skills/sickn33-mobile-developer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "mobile-developer". Choose a framework for a small commerce team that needs iOS, Android, payments, camera access, and a six-month launch.
Expected outcome:
Recommendation: React Native with native payment and camera integrations. The assessment compares delivery speed, platform behavior, maintenance cost, testing, and staffing risks.
Using "mobile-developer". Design offline message delivery for a mobile chat application.
Expected outcome:
- Store outgoing messages locally with stable client identifiers and explicit delivery states.
- Retry through a durable queue with backoff, connectivity checks, and authentication renewal.
- Reconcile server acknowledgements idempotently and test process termination, duplication, and ordering failures.
Using "mobile-developer". Prepare a Flutter application for store release.
Expected outcome:
The release checklist covers signing, automated tests, performance baselines, crash reporting, accessibility, privacy declarations, staged rollout, and rollback criteria.
Security Audit
SafeAll 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.
Risk Factors
⚙️ External commands (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-mobile-developer/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-mobile-developer?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-mobile-developer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-mobile-developer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-mobile-developer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). mobile-developer security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-mobile-developer/audits/5BibTeX citation
@techreport{sickn33-sickn33-mobile-developer-2026,
author = {sickn33},
title = {mobile-developer security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-mobile-developer/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "mobile-developer security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-08-04"
url: "https://skillstore.io/skills/sickn33-mobile-developer/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-mobile-developer:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
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.
Try These Prompts
Compare React Native, Flutter, and native development for [product]. Consider [team skills], [required integrations], [performance needs], and [delivery date]. Recommend one approach.
Design a mobile architecture for [application]. Include modules, state management, navigation, data access, error handling, testing boundaries, and platform-specific components.
Create an offline-first synchronization strategy for [data model]. Cover local storage, queueing, retries, conflicts, authentication expiry, background limits, and recovery testing.
Audit this [React Native, Flutter, iOS, or Android] application for production. Assess performance, security, accessibility, observability, testing, signing, privacy, and staged release risks.
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.
Avoid
- 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.