When to use this skill
ALWAYS use this skill when the user mentions:
- Android or iOS builds / Android or iOS builds
- Mobile debugging or run flows / Mobile debugging and run flows
- Bundle identifier configuration / Bundle identifier configuration
Trigger phrases include:
- "mobile", "android", "ios", "bundle id", "debugging"
- "mobile", "Android", "iOS", "bundle identifier", "debugging"
How to use this skill
- Confirm mobile prerequisites and target platforms
- Configure bundle identifiers and platform settings
- Set up mobile debugging workflow
- Validate responsive UI behavior and platform constraints
Outputs
- Mobile development checklist / Mobile development checklist
- Bundle ID and platform settings plan / Bundle ID and platform configuration plan
Scope
- Boundary: Mobile-specific setup and workflow only
- Key points: Bundle ID and mobile debugging
References
- https://v2.tauri.app/llms.txt
- https://v2.tauri.app/mobile/
- https://v2.tauri.app/mobile/development/
- https://v2.tauri.app/learn/mobile-file-associations/
- https://v2.tauri.app/learn/mobile-multiwindow/
Keywords
tauri mobile, android, ios, bundle id, debugging
Common Gotchas (Gotchas)
- Version compatibility: Pay attention to the compatibility of framework versions and dependency libraries; APIs may differ across versions
- Configuration file format: Configuration file format errors are the most common issue; it is recommended to use the editor's syntax checking
- Environment variables: Ensure all necessary environment variables are set correctly, and do not hard-code sensitive information
- Dependency conflicts: When multiple versions coexist, watch out for dependency conflicts and use a lock file to pin versions
- Performance pitfalls: In large-data scenarios, pay attention to performance optimization and avoid common issues such as N+1 queries
Usage flow
Step 1: Environment preparation
Ensure the development environment has the necessary dependencies and tools installed.
Step 2: Configuration initialization
Perform basic configuration according to project requirements.
Step 3: Using core features
Implement core features according to the example code.
Step 4: Test verification
Run tests to ensure the functionality works properly.
Step 5: Deployment and release
After development is complete, proceed with deployment and monitoring.