In short:
ak-mobile-developmentreads your real project to learn the framework, SDKs and supported devices, then builds or fixes iOS and Android work on that same stack. It does not switch frameworks on its own, does not turn the whole app offline-first unasked, and does not treat sample performance numbers as pass or fail thresholds.
Disclosure: I maintain AgentKit and have an affiliate relationship with it: the AgentKit link in this post is an affiliate link; buying through it gets you 30% off.
Summary
Use it when you need to build or fix an iOS, Android, React Native or Flutter app, or when you are torn over which framework to pick for a new app. You do not need to ask it for a framework comparison when you only change one screen: for scoped work, it keeps the stack you already use.
flowchart LR
A["Work on an iOS or Android app"] --> B["ak-mobile-development"]
B --> C["Read the project's framework, SDKs, devices"]
C --> D["Build on the stack in use"]
C --> E["Compare frameworks when none is chosen"]
D --> F["Check store requirements before release"]It always pins down 4 points:
| Point | Question | Example |
|---|---|---|
| The project's real stack | Which framework, SDKs and toolchain does the app run on, and which devices does it support? | pubspec.yaml plus ios/ and android/ means Flutter, so a screen fix keeps the architecture |
| Offline behavior | What does the user see when the network drops? | Show cached data and a "Retry" button |
| Performance budget | How fast is fast enough, measured on which device? | App opens in under 2 seconds on the mid-range Android phones your customers use |
| Evidence from real devices | Which device backs a claim about performance, battery or memory? | "Measured on a real iPhone. No low-end Android device to measure yet." |
Whatever the feature, the skill keeps three things: storing sensitive data safely (Keychain on iOS, KeyStore on Android), accessibility, and a recovery path when something fails.
Sample prompt for changing a screen in an existing app:
/ak-mobile-development Add an "Order history" screen to the <app name> app.
Outcome: users open the Orders tab, see their list of orders, and pull down to refresh.
Constraints: keep the current architecture and state library, add no new framework.
Done when: it runs on both iOS and Android, with tests for the data fetching.This skill has no flags. After the command you can write the platform and then the feature ([platform] [feature]), but stating the request plainly, like the sample prompt, is still the safest way.
Below is the detailed version: the run flow, 5 situations with prompts, how to write the input, the change history by ak release, and common pitfalls. The detailed version and the interactive page are for subscribers. Your agent can also search them through the portal's MCP.
Opens when your account has subscriber access
This guide is for subscribers
Once your account has access, the full piece, the interactive visual and the agent call all open.
- Sign in or create a modernEngineer accountReading access belongs to your account email.
- Choose a plan on the pricing page1, 3 or 12 months, paid by VietQR bank transfer. Access opens about a minute after the money arrives.
- Or redeem a Facebook subscriber codePeople supporting the page on Facebook get an activation code by message each month.
Already a subscriber? Sign in to read.
Use this piece in your agent
Get an API keyCopy the text below and paste it into Claude Code, Codex or whichever agent you use. The agent reads the piece and checks it against the repo you have open.
Read "ak-mobile-development: build iOS and Android apps on your existing stack" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-mobile-development". If the modernengineer MCP server is not connected, stop and walk me through connecting it from https://modernengineer.dev/en/mcp.
2. Summarize the main steps of the piece and point out which apply to this repo.
3. Propose concrete changes and ask me before editing any file.Connect MCP in Claude Code (once)
claude mcp add --transport http modernengineer \
https://api.modernengineer.dev/mcp \
--header "Authorization: Bearer <API key>"Reading the full piece over MCP needs an API key from a subscriber account or one that bought this guide. Without access, the agent only gets the opening.
- Version
- v1.0.0
- Updated
- 22/10/2026
- Licence
- All rights reserved
- Slug
- ak-mobile-development
