Superapp Homepage
Last updated: 2025-10-24 17:46:16
Feature description
Superapp is the host environment for running mini programs or mini games. It is created by superapp team admin or senior developers on the superapp homepage. After creating a superapp, a configuration file is generated. Download the configuration file and import it into the code project to complete the mini program container SDK integration.
Roles and permissions
Feature | Role | Super admin | Platform admin | Superapp admin | Senior superapp developer | Superapp developer | Superapp operator | Approver |
Superapp homepage | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ | ✓ |
Create, modify, and delete superapps | - | - | ✓ | ✓ | - | - | - |
Download the configuration file | - | - | ✓ | ✓ | ✓ | - | - |
Add/modify package names | - | - | ✓ | ✓ | - | - | - |
Super admin/Platform admin: has read-only access to the superapp homepage and permission to view superapps; cannot create, modify, or delete superapps.
Superapp admin/Senior superapp developer: has full access to the superapp homepage, including permissions to view, create, modify, and delete superapps, download configuration files, and add or modify package names.
Superapp developer: has access to the superapp homepage with permissions to view apps and download configuration files.
Superapp operator/Approver: has access to the superapp homepage with permission to view apps.
How to operate
1 Create a superapp
Required information:
Superapp name: Supports 3-64 characters including a-z, A-Z, 0-9, spaces and some special symbols ("+", "=", ",", ".", "@", "-", "_").
Optional information:
Superapp description: Brief introduction of the superapp, primarily for internal reference.
Superapp icon: Supports uploading square images in .jpg or .png format, with a resolution of 128 × 128 and a file size under 2 MB. If the icon is not uploaded, the system default icon will be used.
2. Complete the integration
2.1 Add the package name or bundle ID
Add the package name for Android and bundle ID for iOS.
The following fields need to be filled in when adding the package name/bundle ID:
Type: Once selected, the type cannot be changed. Package names for non-production types are only used for superapp test versions and have a monthly device usage limit (up to 500 devices).
Package name/bundle ID: Only supports lowercase letters (a-z), numbers (0-9), dots (.), and hyphens (-), up to 255 characters. It is recommended to use reverse domain name notation, such as com.example.myapp.
Download URL: Only supports lowercase letters (a-z), numbers (0-9), dots (.), hyphens (-), and slashes (/), up to 2,048 characters.
Scheme: Only supports lowercase letters and numbers, up to 64 characters. Once the scheme is configured, the QR code of the mini program (or mini game) will include this scheme. Using the phone system’s built-in scanning function, users can directly launch superapp and open the mini program (or mini game).
Note:
Only one production package name/bundle ID and one non-production package name/bundle ID can be added for a superapp.
Package name/bundle ID can only be used for genuine superapps. The SAS SDK will verify the real package name/bundle ID of the superapp against the one entered in the console. If they do not match, the SDK features will be unavailable (the mini program cannot be opened).
2.2 Download the configuration file
After adding the package name/bundle ID, superapp developers need to download the configuration file and import it into the superapp code project.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback