[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"pack-detail-mobile-app-dev-ai-stack-fr":3,"seo:pack:mobile-app-dev-ai-stack:fr":96},{"code":4,"message":5,"data":6},200,"操作成功",{"pack":7},{"slug":8,"icon":9,"tone":10,"status":11,"status_label":12,"title":13,"description":14,"items":15,"install_cmd":95},"mobile-app-dev-ai-stack","📱","#06B6D4","new","Nouveau · cette semaine","Stack IA pour Développement Mobile — iOS + Android","Dix choix pour le dev Swift\u002FKotlin\u002FReact Native\u002FFlutter qui livre sur App Store et Play : agent Mobile App Developer, agent iOS Developer, agent Flutter Expert, Expo, Flutter, Swift, Kotlin, XcodeBuildMCP, Maestro E2E, Fastlane. Ordre : framework → UI IA → build → test → publication.",[16,28,35,42,50,57,65,72,82,89],{"id":17,"uuid":18,"slug":19,"title":20,"description":21,"author_name":22,"view_count":23,"vote_count":24,"lang_type":25,"type":26,"type_label":27},4377,"b04f20a2-c2b7-4f6b-ab45-2a68987e85ef","claude-code-agent-mobile-app-developer-b04f20a2","Claude Code Agent: Mobile App Developer","Use this agent when developing iOS and Android mobile applications with focus on native or cross-platform implementation, performance optimization, and platform-specific user...","TokRepo精选",29,0,"en","skill","Skill",{"id":29,"uuid":30,"slug":31,"title":32,"description":33,"author_name":22,"view_count":34,"vote_count":24,"lang_type":25,"type":26,"type_label":27},4376,"a8e25468-f750-4d91-9c2e-87983673e94a","claude-code-agent-ios-developer-a8e25468","Claude Code Agent: IOS Developer","Native iOS development specialist with Swift and SwiftUI. Use PROACTIVELY for iOS applications, UIKit\u002FSwiftUI components, Core Data integration, app lifecycle management, and...",27,{"id":36,"uuid":37,"slug":38,"title":39,"description":40,"author_name":22,"view_count":41,"vote_count":24,"lang_type":25,"type":26,"type_label":27},4522,"775e4ab6-01f3-453e-b4f5-6f5f7781cb4d","claude-code-agent-flutter-expert-775e4ab6","Claude Code Agent: Flutter Expert","Use when building cross-platform mobile applications with Flutter 3+ that require custom UI implementation, complex state management, native platform integrations, or performance optimization across iOS\u002FAndroid\u002FWeb. Specifically:\\\\n\\\\n\u003Cexample>\\\\nContext: B...",37,{"id":43,"uuid":44,"slug":45,"title":46,"description":47,"author_name":48,"view_count":49,"vote_count":24,"lang_type":25,"type":26,"type_label":27},1002,"ee9542c4-3577-11f1-9bc6-00163e2b0d79","expo-universal-native-apps-ios-android-web-ee9542c4","Expo — Universal Native Apps for iOS, Android & Web","Expo is an open-source framework and platform for making universal React Native apps. Ship to iOS, Android, and web from one codebase — OTA updates, managed workflow, EAS Build cloud service, and 100+ prebuilt native modules.","Script Depot",173,{"id":51,"uuid":52,"slug":53,"title":54,"description":55,"author_name":48,"view_count":56,"vote_count":24,"lang_type":25,"type":26,"type_label":27},1070,"7cce6fed-3606-11f1-9bc6-00163e2b0d79","flutter-google-cross-platform-ui-toolkit-beautiful-apps-7cce6fed","Flutter — Google Cross-Platform UI Toolkit for Beautiful Apps","Flutter is Google cross-platform UI toolkit for crafting beautiful, natively compiled applications for mobile, web, desktop, and embedded devices from a single codebase. Powered by the Dart language and the Skia rendering engine (now Impeller).",190,{"id":58,"uuid":59,"slug":60,"title":61,"description":62,"author_name":63,"view_count":64,"vote_count":24,"lang_type":25,"type":26,"type_label":27},1071,"7cce7840-3606-11f1-9bc6-00163e2b0d79","swift-apple-modern-programming-language-7cce7840","Swift — Apple Modern Programming Language","Swift is a powerful and intuitive programming language for building apps for iOS, macOS, watchOS, tvOS, Linux, and the server. Created at Apple to replace Objective-C. Fast, safe, and expressive with protocol-oriented design.","AI Open Source",168,{"id":66,"uuid":67,"slug":68,"title":69,"description":70,"author_name":48,"view_count":71,"vote_count":24,"lang_type":25,"type":26,"type_label":27},1072,"7cce7cf5-3606-11f1-9bc6-00163e2b0d79","kotlin-modern-statically-typed-language-jvm-beyond-7cce7cf5","Kotlin — Modern Statically Typed Language for JVM and Beyond","Kotlin is a statically typed, general-purpose programming language developed by JetBrains. Runs on the JVM, Android, native, WebAssembly, and JS targets. Officially endorsed by Google as the preferred language for Android development.",130,{"id":73,"uuid":74,"slug":75,"title":76,"description":77,"author_name":78,"view_count":79,"vote_count":24,"lang_type":25,"type":80,"type_label":81},3065,"95ba5976-c0ac-4530-9ede-f3cb418ba38d","xcodebuildmcp-xcode-build-tools-for-agents","XcodeBuildMCP — Xcode Build Tools for Agents","XcodeBuildMCP adds an MCP server + CLI so agents can build iOS\u002FmacOS projects, list tools, and capture logs. Install via brew or npm, then run init.","MCP Hub",66,"mcp","MCP",{"id":83,"uuid":84,"slug":85,"title":86,"description":87,"author_name":63,"view_count":88,"vote_count":24,"lang_type":25,"type":26,"type_label":27},2950,"619c649e-4c8d-11f1-9bc6-00163e2b0d79","maestro-painless-e2e-testing-mobile-web-619c649e","Maestro — Painless E2E Testing for Mobile and Web","A declarative UI testing framework for iOS, Android, and web that uses simple YAML flows instead of complex test code.",38,{"id":90,"uuid":91,"slug":92,"title":93,"description":94,"author_name":63,"view_count":71,"vote_count":24,"lang_type":25,"type":26,"type_label":27},3074,"f4e27875-4d54-11f1-9bc6-00163e2b0d79","fastlane-automate-building-releasing-ios-android-apps-f4e27875","Fastlane — Automate Building and Releasing iOS and Android Apps","Fastlane is an open-source platform that simplifies iOS and Android deployment. It handles code signing, screenshots, beta distribution, and App Store releases from a single command.","tokrepo install pack\u002Fmobile-app-dev-ai-stack",{"pageType":97,"pageKey":8,"locale":25,"title":98,"metaDescription":99,"h1":100,"tldr":101,"bodyMarkdown":102,"faq":103,"schema":119,"internalLinks":162,"citations":175,"wordCount":188,"generatedAt":189},"pack","Mobile App Dev AI Stack — iOS + Android Tools for Swift, Kotlin, RN & Flutter","Mobile App Developer agent, iOS Developer agent, Flutter Expert agent, Expo, Flutter, Swift, Kotlin, XcodeBuildMCP, Maestro E2E, Fastlane. Curated install order for native and cross-platform mobile engineers from framework choice through App Store \u002F Play submission. Install via TokRepo.","Mobile App Dev AI Stack — A Framework-to-Store Pipeline","Ten picks in a deliberate order — pick framework, wire AI UI generation, get an agent that drives the simulator, test on real devices, then ship the build with Fastlane. Skip the React-Native-vs-Flutter holy war, wire the pipeline, file the app.","## What's in this pack\n\nThis is the stack a mobile engineer reaches for when *AI actually has to ship to App Store and Play* — not the listicle of every IDE on Earth. Every pick covers one rung of the same ladder: pick the framework you'll write in, give the agent enough context to scaffold real UI in that framework, give it the build tools to compile and boot a simulator, prove the screen works on a real device through an E2E driver, and ship the signed artifact to the stores without doing the upload dance yourself.\n\nThe pack is **deliberately framework-plural** — Swift for native iOS, Kotlin for native Android, Expo + React Native for the JavaScript shop, Flutter + Dart for the single-codebase shop. The five layers (framework, AI UI, build, test, ship) are the same regardless of which you pick; the tooling under each layer is what changes. Treat the framework picks as a menu — install the one (or two) you'll actually code in, then the four pipeline layers that wrap around it.\n\n| # | Asset | Layer | What it does |\n|---|---|---|---|\n| 1 | Claude Code Agent: Mobile App Developer | AI orchestrator | cross-platform agent that reads the repo, calls the right framework agent, runs the build |\n| 2 | Claude Code Agent: iOS Developer | AI UI (iOS) | Swift \u002F SwiftUI \u002F UIKit specialist for screens, navigation, Core Data |\n| 3 | Claude Code Agent: Flutter Expert | AI UI (Flutter) | Flutter 3+ specialist for widgets, state, platform channels |\n| 4 | Expo | framework (RN) | universal React Native runtime — iOS, Android, web from one codebase |\n| 5 | Flutter | framework (cross) | Google's cross-platform UI toolkit, Dart + Impeller renderer |\n| 6 | Swift | framework (iOS) | Apple's modern language for iOS, macOS, watchOS, visionOS |\n| 7 | Kotlin | framework (Android) | JetBrains language, Android-first, also JVM and multiplatform |\n| 8 | XcodeBuildMCP | build (iOS) | MCP server that exposes xcodebuild, simctl, and device list to agents |\n| 9 | Maestro | E2E test | declarative YAML flows for iOS + Android, runs on simulator and device |\n| 10 | Fastlane | ship | TestFlight upload, App Store Connect metadata, Play Store deploy, certs |\n\n## Install in this order (framework → AI UI → build → test → ship)\n\n1. **Pick your framework first** (assets 4–7). The rest of the pipeline depends on the choice. **Flutter** (#1070) if you want one codebase and Google-grade rendering. **Expo** (#1002) if your team already lives in TypeScript and you need OTA updates. **Swift** (#1071) and **Kotlin** (#1072) if you're building a native-first app where every platform-specific affordance matters. Most teams install two — one cross-platform plus one native — so they can drop down when the cross-platform abstraction leaks.\n2. **Mobile App Developer agent** (#4377) — the orchestrator. Cross-platform agent that reads your project structure, decides whether the change is iOS, Android, or both, and delegates to the specialist agents. Daily driver; everything below routes through it.\n3. **iOS Developer agent** (#4376) — Swift \u002F SwiftUI \u002F UIKit specialist. Use for native iOS screens, Core Data schemas, AVFoundation pipelines, and anywhere SwiftUI's modifiers go six layers deep. The agent understands `@StateObject`, `@Observable`, navigation stacks, and the `Info.plist` privacy keys you forgot.\n4. **Flutter Expert agent** (#4522) — Flutter 3+ specialist. For widget trees, state management (Riverpod \u002F Bloc \u002F Provider — pick one and stick), platform channels to native APIs, and the `pubspec.yaml` dance. Pair with the Flutter framework (#1070) install above.\n5. **XcodeBuildMCP** (#3065) — build & simulator tools for the agent. Without this, the agent writes Swift code and can't compile it; with this, the agent can call `xcodebuild`, list simulators, boot one, install the `.app`, and read back logs. The missing link between an agent that *writes* iOS code and one that *ships* it.\n6. **Maestro** (#2950) — E2E test that the agent can write. Declarative YAML (`tapOn`, `assertVisible`, `swipe`) runs on iOS simulator, Android emulator, and physical devices over USB. Replaces the Appium \u002F Detox \u002F Espresso debate with one tool that the agent can author flows for in 30 seconds.\n7. **Fastlane** (#3074) — the ship layer. Automates code signing, TestFlight uploads, App Store Connect metadata, Play Store releases, screenshot generation. The agent writes the `Fastfile`, you run `fastlane beta`, and the next build is in TestFlight without you opening Xcode Organizer.\n\n## How they fit together (ASCII pipeline)\n\n```\n   product idea \u002F Figma\n        │\n        ▼\n  ┌──────────────────────────────────┐\n  │ Mobile App Developer Agent       │\n  │ (#4377) — repo-aware orchestrator│\n  └──────┬───────────────────────────┘\n         │ routes by platform\n         ├──────────────┬──────────────┐\n         ▼              ▼              ▼\n  ┌────────────┐ ┌─────────────┐ ┌──────────────┐\n  │ iOS Dev    │ │ Flutter     │ │ Expo \u002F RN    │\n  │ Agent      │ │ Expert      │ │ (#1002)      │\n  │ (#4376)    │ │ (#4522)     │ │ + JS \u002F TS    │\n  │ + Swift    │ │ + Flutter   │ │              │\n  │ (#1071)    │ │ (#1070)     │ │              │\n  └─────┬──────┘ └──────┬──────┘ └──────┬───────┘\n        │               │               │\n        ▼               ▼               ▼\n  ┌────────────┐ ┌─────────────┐ ┌──────────────┐\n  │ Kotlin     │ │ XcodeBuild  │ │ Metro \u002F EAS  │\n  │ (#1072)    │ │ MCP (#3065) │ │ build        │\n  │ for Android│ │ build + sim │ │              │\n  └─────┬──────┘ └──────┬──────┘ └──────┬───────┘\n        └───────────────┼───────────────┘\n                        ▼\n              ┌──────────────────┐\n              │ Maestro E2E      │\n              │ (#2950)          │\n              │ iOS + Android    │\n              └────────┬─────────┘\n                       │\n                       ▼\n              ┌──────────────────┐\n              │ Fastlane (#3074) │\n              │ certs · TestFlight│\n              │ App Store · Play │\n              └────────┬─────────┘\n                       │\n                       ▼\n               App Store \u002F Play\n```\n\nThe critical join is **Mobile App Developer Agent + XcodeBuildMCP + Maestro**: the agent writes Swift or Dart, XcodeBuildMCP compiles it and boots a simulator, Maestro proves the screen actually responds to taps. Without XcodeBuildMCP, the agent ships code that compiles in its head; without Maestro, you find out at TestFlight that the login button doesn't fire on Android 12 small screens.\n\n## Tradeoffs (the honest part)\n\n- **Cross-platform vs native.** Flutter and Expo are 70% of the way to native feel; the last 30% (haptics, custom keyboards, share extensions, platform-specific privacy prompts, Live Activities, App Clips, Wear OS tiles) is where the abstraction leaks. Pick cross-platform when you ship one product to both stores fast; pick native when one platform's deep integrations *are* the product. Real teams ship Flutter for the main app and native modules for the 5% that needs it.\n- **Expo vs bare React Native.** Expo gives you OTA updates, EAS Build, prebuilt native modules, and a faster local loop. Bare React Native gives you full Xcode \u002F Gradle access and any third-party SDK. Default to Expo, eject only when you hit a wall — most teams never need to.\n- **Maestro vs Appium vs Detox.** Maestro is in this pack because the *agent* can author flows in YAML in seconds. Appium is more mature and supports any framework but the WebDriver dance is painful. Detox is fast for React Native specifically. For agent-driven testing, Maestro wins on author cost.\n- **XcodeBuildMCP vs running xcodebuild yourself.** You can call `xcodebuild` from a terminal; the MCP wraps it so the agent can call it without you copy-pasting. The value is *agent autonomy*, not faster builds.\n- **AI-generated UI quality.** First-draft SwiftUI from an agent often has the right shape but wrong navigation patterns (NavigationStack vs NavigationView, sheet vs fullScreenCover, the right keyboard avoidance). Always run the screen in the simulator before merge; reviewers will catch what the agent missed.\n- **Apple Review risk.** Apple's reviewers reject for 4.2 (\"minimum functionality\") faster than they did two years ago. An AI-scaffolded MVP that's a thin wrapper around an API will fail review. Ship a feature, not a chat UI on top of a model.\n- **Fastlane vs Xcode Cloud vs EAS.** Fastlane runs anywhere (your laptop, GitHub Actions, Bitrise) and stays portable. Xcode Cloud is convenient but iOS-only and locks you in. EAS is convenient for Expo specifically. Fastlane is the lingua franca.\n\n## Common pitfalls\n\n- **Apple Review 4.2 rejection.** \"Your app does not provide enough functionality\" — the most common rejection for AI-scaffolded MVPs. Wrappers around ChatGPT, single-screen utilities, and \"AI photo edit\" clones get rejected on first submit. Ship a real feature with offline state, settings, an account flow, and at least three meaningful screens before submitting.\n- **Android fragmentation.** Build looks great on a Pixel 8 emulator, ships, then breaks on a Samsung mid-range with a 3:2 aspect ratio and a non-standard density. Test on at least three real form factors (small phone, large phone, tablet) — Maestro on a device farm is the cheapest way.\n- **Missing privacy permission strings.** iOS rejects builds (Apple 5.1.1) if you access camera \u002F mic \u002F location \u002F photos and the `Info.plist` `NSCameraUsageDescription` etc. is missing or generic. The agent forgets these constantly; add a pre-submit checklist that greps for every privacy key.\n- **IAP sandbox testing skipped.** App Store Connect rejects (3.1.1) if your subscription \u002F IAP flow wasn't tested with a sandbox tester account. The sandbox is its own world (separate Apple ID, different receipts, slower) and easy to skip when iterating. Build a Maestro flow that drives the IAP purchase end-to-end on a sandbox account before every release.\n- **Pushing a non-signed build to TestFlight.** Fastlane handles certs and provisioning profiles if you let it (`match` for shared keys). Doing it manually leads to the 11:59 PM cert-expiry panic. Set `match` up on day one, store the keys in a private repo, never look back.\n- **Letting the agent generate platform-specific code into shared files.** Expo \u002F Flutter shared code with `Platform.OS === 'ios'` branches everywhere is a maintenance tax. Push platform-specific logic into `*.ios.tsx` \u002F `*.android.tsx` files (Expo) or platform channels (Flutter) so the shared layer stays clean.\n- **Skipping Maestro because \"the simulator looks fine\".** The most common AI-mobile regression is a tap target that's 40pt on iOS (fine for fingers) but the agent sized 20pt (fine for clicks); accessibility scan catches it once, your hands catch it never. Maestro `tapOn` with explicit coordinates surfaces this in 30 seconds.\n- **Treating MCP servers as optional plumbing.** Without XcodeBuildMCP, the agent has to ask you to run `xcodebuild` and paste output. Wire the MCPs first (an afternoon), then the rest of the pack pays off every day.",[104,107,110,113,116],{"q":105,"a":106},"Flutter vs React Native vs native — which framework should I pick?","Honest answer: it depends on the team you already have and the platform-specific affordances you need. Pick **Flutter** if you want one codebase, opinionated tooling (Dart, pubspec, the Material\u002FCupertino widget split), and Google-grade rendering — best when the app is mostly your own UI. Pick **React Native + Expo** if your team is TypeScript-first, you want OTA updates without a store re-review, and you can live with the JavaScript bridge. Pick **native Swift + Kotlin** when platform-specific features *are* the product (App Clips, Live Activities, Wear OS tiles, complex camera pipelines, watch apps) — the cross-platform abstractions leak exactly where you can't afford the leak. Real teams ship Flutter or Expo for v1 and rewrite hot screens to native when usage justifies the engineering.",{"q":108,"a":109},"Can Cursor \u002F Claude Code actually write Swift, or do I still need Xcode?","Both. Claude Code (via the iOS Developer agent #4376) writes Swift \u002F SwiftUI well — it understands `@StateObject`, navigation stacks, Combine vs async\u002Fawait, Core Data schemas, and the common Info.plist privacy keys. But you still need Xcode for the things only Xcode does: provisioning profile signing, simulator runtime downloads, Instruments profiling, Interface Builder for legacy code, and Apple's submission tooling. The workflow that works: agent writes the code and tests in the editor, you switch to Xcode for sign-and-ship steps, XcodeBuildMCP (#3065) lets the agent run builds and boot simulators without you tabbing over for every iteration.",{"q":111,"a":112},"Apple rejected my build — how do I get an AI-scaffolded app through review?","Three rejection patterns cover ~80% of AI-app rejections: (1) **4.2 minimum functionality** — your app is a thin wrapper, fix by adding a real feature (offline state, account, settings, three+ meaningful screens, not just a chat UI). (2) **5.1.1 privacy** — missing or generic `NSCameraUsageDescription` \u002F `NSLocationWhenInUseUsageDescription` strings; fix by writing a specific reason (\"Used to scan receipts for expense tracking\") and double-checking every privacy-sensitive API is justified. (3) **3.1.1 IAP not tested** — your subscription flow wasn't exercised with a sandbox tester; fix by testing IAP on a sandbox Apple ID before every submission. Build a pre-submit checklist that greps for these three classes; reviewers are pattern-matching to known bad shapes and the agent doesn't know your business reasoning.",{"q":114,"a":115},"What's the cheapest way to test in-app purchases without paying real money?","Apple sandbox testers (free, created in App Store Connect) and Google Play license testers (free, configured in the Play Console) are the standard answer. Both let you complete the IAP flow end-to-end with a fake card and instant refund. Pitfalls: the sandbox subscription duration is *minutes*, not months — a 1-year sub renews every 5 minutes for the first 6 cycles, then stops. Plan your test scripts around the compressed timeline. For automated testing, RevenueCat ships a free SDK that abstracts both stores' receipt validation and ships sandbox helpers; pair it with a Maestro flow (#2950) that runs the purchase loop on a sandbox account before every release. Don't ship an IAP build without at least one real sandbox purchase + restore test — App Store Connect 3.1.1 rejections are the most expensive bug to fix because they cost a review cycle (1–3 days).",{"q":117,"a":118},"Are there AI tools that handle push notifications well, or is this still manual config?","The setup itself (APNs key on iOS, FCM service account on Android) is still a one-time manual gotcha — no agent will hand-fix your Apple Developer Account certificates for you. But the *integration* side is increasingly agent-friendly: the Mobile App Developer agent (#4377) can scaffold APNs \u002F FCM client registration, write the server-side send code (Firebase Admin SDK, OneSignal SDK, or your own APNs HTTP\u002F2 stack), and add the entitlement and capability changes to the Xcode project. For sending, the boring open-source options (Apprise #1871 for personal pushes, Novu #449 for cross-channel orchestration with templates and segmentation) cover most needs. Don't roll your own push retry logic; pick one of these and let the agent wire it. Test with the simulator's notification payload tool *and* a real device — APS payloads behave differently when the device is locked, killed, or in a low-power state, and the simulator doesn't fully reproduce that.",{"@context":120,"@type":121,"name":122,"description":123,"numberOfItems":124,"inLanguage":25,"itemListElement":125,"publisher":158},"https:\u002F\u002Fschema.org","ItemList","Mobile App Dev AI Stack — iOS + Android","Ten assets across five layers (framework, AI UI, build, test, ship) for Swift, Kotlin, React Native, and Flutter engineers using AI from project scaffold through App Store and Play Store submission.",10,[126,130,134,137,140,144,147,150,153,156],{"@type":127,"position":128,"name":20,"url":129},"ListItem",1,"https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Fclaude-code-agent-mobile-app-developer-b04f20a2",{"@type":127,"position":131,"name":132,"url":133},2,"Claude Code Agent: iOS Developer","https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Fclaude-code-agent-ios-developer-a8e25468",{"@type":127,"position":135,"name":39,"url":136},3,"https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Fclaude-code-agent-flutter-expert-775e4ab6",{"@type":127,"position":138,"name":46,"url":139},4,"https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Fexpo-universal-native-apps-ios-android-web-ee9542c4",{"@type":127,"position":141,"name":142,"url":143},5,"Flutter — Google Cross-Platform UI Toolkit","https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Fflutter-google-cross-platform-ui-toolkit-beautiful-apps-7cce6fed",{"@type":127,"position":145,"name":61,"url":146},6,"https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Fswift-apple-modern-programming-language-7cce7840",{"@type":127,"position":148,"name":69,"url":149},7,"https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Fkotlin-modern-statically-typed-language-jvm-beyond-7cce7cf5",{"@type":127,"position":151,"name":76,"url":152},8,"https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Fxcodebuildmcp-xcode-build-tools-for-agents-95ba5976",{"@type":127,"position":154,"name":86,"url":155},9,"https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Fmaestro-painless-e2e-testing-mobile-web-619c649e",{"@type":127,"position":124,"name":93,"url":157},"https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Ffastlane-automate-building-releasing-ios-android-apps-f4e27875",{"@type":159,"name":160,"url":161},"Organization","TokRepo","https:\u002F\u002Ftokrepo.com",[163,167,171],{"url":164,"anchor":165,"reason":166},"\u002Fen\u002Fpacks\u002Ffrontend-engineer-ai-toolkit","Frontend Engineer's AI Toolkit","shared design hand-off and component generation patterns translate to mobile",{"url":168,"anchor":169,"reason":170},"\u002Fen\u002Fpacks\u002Fai-test-generation-e2e","AI Test Generation + E2E","deeper coverage of test authoring and CI integration that extends Maestro to web and desktop targets",{"url":172,"anchor":173,"reason":174},"\u002Fen\u002Ftopics","Browse other topic packs","adjacent packs cover MCP servers, backend engineering, and CI\u002FCD pipelines that mobile apps rely on",[176,180,184],{"claim":177,"source_name":178,"source_url":179},"XcodeBuildMCP exposes xcodebuild, simulator, and device management to AI agents over MCP","XcodeBuildMCP on GitHub","https:\u002F\u002Fgithub.com\u002Fcameroncooke\u002FXcodeBuildMCP",{"claim":181,"source_name":182,"source_url":183},"Maestro is a declarative mobile UI testing framework that runs on iOS, Android, React Native, and Flutter","Maestro docs","https:\u002F\u002Fmaestro.mobile.dev\u002F",{"claim":185,"source_name":186,"source_url":187},"Fastlane automates iOS and Android beta deployments, code signing, screenshots, and store submissions","Fastlane official docs","https:\u002F\u002Ffastlane.tools\u002F",1380,"2026-05-23T14:00:00Z"]