playbooks

home / skills / partme-ai / full-stack-skills / uniapp-native-app

uniapp-native-app skill

/skills/uniapp-native-app

This skill helps you package uni-app as native Android or iOS apps, manage signing, and configure native settings with official offline guidance.

npx playbooks add skill partme-ai/full-stack-skills --skill uniapp-native-app

Review the files below or copy the command above to add this skill to your agents.

Files (10)
SKILL.md
2.0 KB
---
name: uniapp-native-app
description: A comprehensive skill for uni-app native app offline packaging. Use this skill to package uni-app as native Android/iOS apps, configure native app settings, handle signing, and follow official offline packaging documentation.
license: Complete terms in LICENSE.txt
---

## When to use this skill

Use this skill whenever the user wants to:
- Package uni-app as native Android app
- Package uni-app as native iOS app
- Configure native app settings (manifest, permissions, etc.)
- Customize native app features
- Integrate native plugins
- Configure app signing and certificates
- Handle native app build and distribution

## How to use this skill

To package native apps:

1. **Identify the platform** from the user's request:
   - Android → Use Android examples
   - iOS → Use iOS examples

2. **Load the appropriate example file** from the `examples/` directory:
   - `examples/guide/` - Native app packaging guide
   - `examples/android/` - Android packaging examples
   - `examples/ios/` - iOS packaging examples

3. **Load the appropriate template** from the `templates/` directory:
   - `templates/build-config.md` - Build configuration templates

4. **Follow the specific instructions** in those files for packaging

## Examples and Templates

### Examples

Located in `examples/`:

- **guide/** - Offline packaging overview and setup
- **android/** - Android signing, keystore, build configs
- **ios/** - iOS signing, provisioning, build configs

### Templates

Located in `templates/`:

- **build-config.md** - Build configuration templates

## Best Practices

1. **Follow platform guidelines**: Adhere to Android and iOS development standards
2. **Optimize app size**: Minimize APK/IPA size
3. **Security**: Properly configure app signing and certificates
4. **Testing**: Test on real devices before release

## Resources

- **Official Documentation**: https://nativesupport.dcloud.net.cn/AppDocs/

## Keywords

native app, 原生App, Android打包, iOS打包, 离线打包, app packaging, native plugin

Overview

This skill packages uni-app projects into native Android and iOS apps with offline, configurable build flows. It provides templates, examples, and step-by-step guidance for configuring manifests, permissions, signing, and distribution. The goal is a reproducible offline packaging process that follows official platform requirements and streamlines native integrations.

How this skill works

The skill inspects the target platform (Android or iOS) and selects corresponding examples and templates to drive the build. It loads packaging guides, platform-specific examples, and build configuration templates, then applies the instructions to configure project files, signing credentials, and build settings. The output is a ready-to-build native project (APK/IPA) with recommended settings for testing and release.

When to use it

  • You need to produce a native Android app (APK/AAB) from a uni-app project.
  • You need to produce a native iOS app (IPA) from a uni-app project.
  • You must configure native settings like manifest, permissions, and app identifiers.
  • You need to set up signing, keystores, or provisioning profiles for release builds.
  • You want to integrate or test native plugins and custom native features.

Best practices

  • Follow Android and iOS platform guidelines and target current SDK versions.
  • Use provided build-config templates to keep builds reproducible across environments.
  • Keep signing keys and provisioning profiles secure; never commit them to source control.
  • Optimize assets and remove unused plugins to minimize APK/IPA size.
  • Test builds on physical devices and multiple OS versions before distribution.

Example use cases

  • Offline packaging of a uni-app project into an Android APK for enterprise distribution.
  • Preparing an iOS IPA with correct bundle ID and provisioning profile for App Store submission.
  • Customizing AndroidManifest or Info.plist to add permissions and deep link handlers.
  • Configuring keystore and automatic signing for CI/CD release pipelines.
  • Integrating a native plugin and verifying native APIs on real devices.

FAQ

What files should I edit to change build settings?

Use the build-config templates and platform example folders to update manifest/Info.plist, build.gradle, and Xcode project settings as shown in the examples.

How do I handle signing and certificates safely?

Keep keystore and provisioning files out of source control, use secure storage for credentials, and reference them via CI secrets or local environment variables during builds.