Skip to main content

My App

Manage private and public apps with upload, publish, and control features. Supports GMA and KMA/IMA app policy settings.

Updated yesterday

1. Features and Application Objectives

The “My Apps” module is used to centrally manage all application resources used by the organization. It supports multiple ways to build the app library, including adding public apps from Google Play, uploading enterprise private APKs, and configuring enterprise Web Apps.

Administrators can perform unified operations such as app addition, version updates, enable/disable, and deletion in this module, providing fundamental support for policy configuration.

This module is the core entry for KiwiCloud's application lifecycle management, supporting modules such as “App Distribution Policy,” “Kiosk Mode,” and “Device Policy.”

  • GMA-type apps (from Google Play public/private/Web): Only available for GMA devices and policies;

  • Enterprise apps (from APK upload or Web App): Can be used for policy configurations for KMA and IMA devices.

Purpose

  • Support private APK upload to build an internal enterprise app library;

  • Enable fast access to public apps from Google Play to enrich available software options;

  • Support publishing Web Apps based on URL to meet browser-based business requirements;

  • Centrally maintain version info, status, and source to improve app management efficiency;

  • Integrate with Policy Center for distribution and control by group, schedule, and rule;

  • Provide app details page showing key info like package name, version, and status for tracking and traceability.

Primary Operations:

  • Add Google Play public apps;

  • Add Google Play private apps (including APK upload or Web App);

  • Add enterprise public apps;

  • Publish enterprise private apps;

  • Publish enterprise Web Apps;

  • View app details.

Secondary Operations:

KMA Apps

GMA Apps

Submit

Approve

Edit

Enable / Disable

Delete app

Add new version

Version list

Edit

Enable / Disable

Remove app

Typical Use Cases

  • System integrators upload custom apps for grouped deployment and version control;

  • Chain stores deploy private APKs to KMA devices to unify installation and update policies;

  • Enable customers to integrate with Google Play ecosystem for GMA device management;

  • Deploy SaaS pages to devices as the Kiosk homepage through Web App;

  • Centrally manage app status to prevent unauthorized apps from being mistakenly pushed to devices.

2. Primary Operations

2.1 Add Google Play Public App

Description

This feature allows you to add publicly listed apps from the Google Play Store to the "My Apps" list for use in GMA application policies. With this, administrators can easily search and select compliant public apps without uploading APK files.

Notes:

  • Public apps added are only applicable to GMA-type devices;

  • Once added, the app is marked as "Published"—no approval is required, and it can be used directly in policy configurations.

Steps

  1. Open the Add Menu

    • On the "My Apps" page, click the [Add App] button in the top-right corner;

    • Select [Add Google Play Public App] from the dropdown menu.

  2. Browse and Search for Apps

    • The system will load the Google Play Store interface, showing popular apps;

    • Use the top search bar to enter keywords and find your target app;

    • Filter by rating, editor’s choice, new arrivals, and more.

  3. Select the Target App

    • Click the desired app to view its details page;

    • Click the [Select] button in the top-right corner;

    • Click [Add] at the bottom of the page to complete the process.

  4. Complete Addition

    • Once added, the app will immediately appear in "My Apps" with a status of "Published";

    • You can now include it in application-related policy configurations.

Notes

  • Only apps that are already listed in the Google Play Store are supported; app name and developer info will sync automatically;

  • Public apps cannot be edited—only disabled or deleted;

  • You can view the status, source, and version details in the "My Apps" list;

  • Public apps are only supported in GMA application policies and cannot be used for KMA or IMA devices;

  • For custom APK or Web App use, please use the "Add Private App" feature.

2.2 Add Google Play Private App (Private App)

Description

This feature allows you to upload and add Google Play private apps exclusive to your organization. These apps are not publicly visible on the Play Store and are only accessible and installable on the organization’s devices. Private apps are ideal for distributing custom enterprise apps securely.

Google Play Private Apps are apps developed internally and intended for use by members of the same organization. They are not publicly listed on the Google Play Store but are managed and distributed through the KiwiCloud console. These apps provide enhanced security and manageability.

Notes:

  • Google Play Private Apps include "Private App" (APK/AAB upload) and "Web App"; this process refers to the "Private App" type;

  • Once added, the private app is only applicable to GMA-type devices and cannot be configured for KMA or IMA devices;

  • AAB format is recommended for better size and modular support.

Steps

  1. Select Private App Type

    • In "My Apps", click [Add App], then select [Google Play Private App];

    • Choose “Private App” and click [Next].

  2. Acknowledge Requirements

    • The system will display key upload notes, including package name, signing, and deletion restrictions;

    • Check “I acknowledge” and click [Confirm] to proceed.

  3. Go to Upload Page

    • On the "Private Apps" screen, click the [➕] button in the bottom right.

  4. Upload Package & Fill Info

    • Enter the App Title (max 30 characters);

    • Click [Upload App] to upload a .apk or .aab file;

    • After upload, click [Create] to finish.

  5. Select Uploaded App

    • Once uploaded, your app will appear in the list;

    • Click the app icon to enter its detail page.

  6. Confirm Addition

    • Click the [Select App] button on the detail page;

    • Click [Add] in the bottom-right to finish.

Note: It may take 1–2 minutes for the [Select App] button to become clickable.

Notes

  • Google Play Private Apps are only applicable to GMA application policies and GMA devices, not KMA/IMA;

  • Private apps cannot be deleted directly—first [Disable] them, then delete;

  • APK file limit is 100MB; use AAB or external hosting for larger packages;

  • Only release versions are supported; debug builds cannot be uploaded;

  • Once added, private apps can be used in GMA policies without approval.

2.3 Add Google Play Private App (Web App)

Description

This feature allows you to create and add enterprise Web Apps (Web applications) to Google Play. It packages a company URL into a Web App for deployment to devices, enabling quick access and centralized management.

Notes:

  • A Web App is essentially a browser-based webpage entry, packaged as an Android app and accessible only within the organization;

  • Web Apps are distributed via the KiwiCloud backend and can be configured and deployed to GMA-type devices;

  • This process refers to the “Web App” option under Google Play Private Apps and differs from the APK upload process (“Private App”);

  • Once created, a Web App cannot be deleted directly—it must be disabled first before deletion is allowed.

Steps

  1. Select Web App Type

    • On the "My Apps" page, click [Add App], then select [Google Play Private App];

    • In the popup window, choose "Web App" and click [Next].

  2. Acknowledge Requirements

    • The system will display important notes, including name uniqueness, valid URL format, and legal content compliance;

    • Click [Confirm] to proceed to the Web App creation page.

  3. Create Web App

    • Click the [➕] button in the bottom right to start creating a new Web App;

    • Fill in the following details:

      • Title: App name, up to 30 characters;

      • URL: Target URL (must be in HTTPS format);

      • Display: Choose the display mode (recommend “Fullscreen”);

      • Icon: Upload a 512x512 PNG or JPG icon;

    • After completing the form, click [Create].

  4. Select Uploaded Web App

    • After creation, the new Web App will appear in the Web Apps list;

    • Click the icon to open the app detail page.

  5. Confirm Addition

    • On the detail page, click the [Select App] button;

    • Then click [Add] in the bottom right to complete the addition;

Note: It may take 1–2 minutes before the [Select App] button becomes available after creation.

Notes

  • Web Apps are only supported on GMA-type devices and are not compatible with KMA or IMA;

  • URLs must use HTTPS protocol to ensure security;

  • App icons must meet standard size and Google Play design requirements;

  • Avoid using dynamic IPs or unstable URLs to prevent access failures;

  • Do not configure sensitive data or login-required systems to avoid potential data exposure.

2.4 Add Enterprise Public App

Description

This feature allows you to add enterprise-level public apps published by other organizations via KiwiCloud to your "My Apps" list for use and policy configuration. These apps are typically shared by software vendors for specific industry clients to simplify app acquisition and centralized deployment.

Notes:

  • Enterprise public apps can be used by multiple organizations and cannot be modified;

  • Once added, the app is immediately marked as "Published" without requiring approval and can be used in policies;

  • Supported for KMA / IMA device types depending on the app package type.

Steps

  1. Enter Add App Menu

    • On the "My Apps" page, click the [Add App] button in the top-right corner;

    • From the dropdown menu, select [Add Enterprise Public App].

  2. Agree to Terms & Select App

    • Check the box "I have read and agree to the Enterprise Public App Publishing Agreement";

    • Browse or filter the app list by pages, select the public apps to add (supports multi-selection);

    • Click the [Add] button at the bottom-right to complete the process.

  3. Complete Addition

    • Successfully added apps will appear in the “My Apps” list with status "Published";

    • These apps can then be selected for deployment and version control in policy settings.

Notes

  • Enterprise public apps are uploaded by third-party organizations; your company can only use and deploy them, not edit;

  • No approval is required—apps become effective immediately upon addition and are marked as "Published";

  • To delete an app, you must first [Disable] it;

  • After adding, you can perform operations such as "Enable / Disable / Delete / View Version List";

  • It is recommended to confirm the app version source and compatibility range before adding.

2.5 Publish Enterprise Private App

Description

This feature allows your organization to upload and publish in-house developed APK applications as “Enterprise Private Apps,” making them available exclusively for internal use. These apps are only visible to and installable by members within the same organization, making them ideal for custom development and targeted usage.

Notes:

  • Enterprise Private Apps are exclusive to your organization and can only be accessed and installed by internal members and devices;

  • Standard Android installation packages (.apk format) are supported;

  • After upload, you must configure app details and permissions before submitting for approval;

  • Only after approval can the app be used in policy configurations, and only for KMA and IMA device types;

  • Apps that fail approval will not reach “Published” status and cannot be used in policies.

Steps

  1. Upload App File

    • Click [Upload File] to select and upload a local APK file;

    • Once uploaded, click [Next] to proceed to the configuration page.

  2. Configure App Information

    • Fill in app icon (optional), category, supported devices (user-defined), and description (optional);

    • The system will auto-detect app name, package name, and version;

    • Click [Next] to enter permission settings.

  3. Configure App Permissions

    • Configure access to camera, location, external storage, etc. (permissions are auto-detected from the APK);

    • Choose from [Allow], [Deny], or [User Control] for each permission;

    • Click [Submit] to complete the publishing request.

  4. Submit for Review and Publish

    • After submission, the app enters [Pending Approval] status;

    • Admins can go to "My Apps" and click [Review] to approve or reject the app;

    • Once approved, the app status becomes “Published” and it can be used in policy deployment.

  5. Status Update

    • Apps approved will show “Published” status;

    • The app can be selected in KMA policy configurations;

    • Future versions can be uploaded and will also go through the approval process.

Notes

  • Only .apk files are supported (.aab not supported at this time);

  • The maximum upload size is 500MB. For larger files, please contact KiwiCloud Support;

  • Both release and debug APKs are supported;

  • Enterprise private apps are only compatible with KMA / IMA devices, not GMA;

  • To delete a version, it must first be [Disabled]. Published versions cannot be deleted directly;

  • App information and permissions can be updated later via “Edit Version.”

2.6 Publish Enterprise Web App

Description

This feature allows enterprises to wrap internal websites into Web Apps and publish them as “Enterprise Private Apps” on the KiwiCloud platform. These apps are only available for installation and use on the enterprise’s KMA and IMA devices. Web Apps load business content via URL and are ideal for lightweight SaaS services or internal portals that don’t require installation packages.

Notes:

  • Enterprise Web Apps are private to your organization and only visible and manageable within the enterprise;

  • Supports converting HTTPS URLs into Web Apps that can be centrally deployed and configured via policy;

  • Must be submitted for approval after creation—only approved apps can be used in policies;

  • Only supports KMA / IMA device types, not compatible with GMA;

  • Three display modes are supported: Fullscreen, Standalone Window, and Minimal UI.

Steps

  1. Enter the Creation Page

    • On the "My Apps" page, click [Add App], then select [Publish Enterprise Web App];

    • The system will open the Web App configuration page.

  2. Fill in Basic Information

    • Enter the app name (up to 256 characters);

    • Enter the Web App URL (must use HTTPS protocol);

    • Select app category (e.g., Default, Tools, Retail);

    • Choose display mode (Fullscreen / Standalone Window / Minimal UI);

    • Upload an app icon (recommended size: 512×512, PNG/JPG format).

  3. Submit the App

    • Click [Submit]; the app enters "Pending Approval" status;

    • You can view the submission record in the “My Apps” list.

  4. Approval and Publishing

    • Admin clicks the [Review] button in the “My Apps” section;

    • A pop-up will confirm approval. Click [Approve] to complete the process;

    • Upon approval, the app status changes to “Published.”

  5. Status Change & Policy Configuration

    • Approved Web Apps will show a “Published” status;

    • Can be configured and deployed in KMA / IMA policy settings;

    • You can later disable, modify, or delete the app from its detail page.

Notes

  • Only applicable for KMA and IMA devices;

  • URL must begin with https:// for security;

  • It is recommended to follow Android icon guidelines for better UI compatibility;

  • Web Apps cannot be deleted directly—please disable them first;

  • Approval is handled internally by admins with the appropriate permissions.

2.7 View App Details

Description

This feature allows you to view detailed information about added apps, including basic info, permission settings, publishing strategies, distribution records, and operation/system logs. Admins can use this view to quickly understand the app’s usage scope, version configuration, associated policies, and deployment status. It is ideal for routine checks, policy reviews, and issue troubleshooting.

Notes:

  • The top section shows version info, number of linked policies, and associated groups/devices; historical versions can be viewed;

  • Tab navigation allows browsing of policies, groups, device distribution records, and logs;

  • All information displayed corresponds to the currently selected version for audit tracking.

Steps

  1. Open the Details Page

    • On the "My Apps" page, click the [Details] button for the target app;

    • The system opens the “App Details” window, showing the current version by default.

  2. View Key Information

    • The top summary shows the current version, number of associated policies, group count, and device count;

    • Use the version dropdown to switch and view historical versions.

  3. App Info Tab

    • Displays app type (e.g., Enterprise Private App), package name, version code, upload time, and other base info;

    • If the app is from Google Play, the Play Store link will be shown; for private apps, this is omitted.

  4. App Permissions Tab

    • Shows requested sensitive permissions such as camera, location, and storage;

    • Displays the permission policy (Allow / Deny / User Control) for each item;

    • Only auto-detected permissions are shown.

  5. Policies Tab

    • Lists all policies that include the current version of the app;

    • Displays policy name, type, version, operator, and actions (e.g., Unlink);

    • Helps identify usage scenarios and version control context.

  6. Groups Tab

    • Shows all device groups where the app has been deployed via policy;

    • Includes group name, number of devices, policy type, policy ID, and execution time;

    • Useful for tracing distribution paths.

  7. Devices Tab

    • Lists all terminals that have received the app deployment command;

    • Shows device name, OS version, policy details, and execution time;

    • Supports filtering by device name or policy ID for quick traceability.

  8. Operation Logs Tab

    • Displays admin actions performed on the app (e.g., enable/disable, add version, approval);

    • Includes operation ID, type, executor, result, and timestamp;

    • Useful for permission audit and troubleshooting.

  9. System Logs Tab

    • Records system actions such as auto-deploy, enable/disable by the platform;

    • Shows action type, result, duration, and timestamp;

    • Helps diagnose failed deployments or abnormal events.

Notes

  • Only apps uploaded or added by your organization can be viewed;

  • Each version has independent data; switching versions refreshes the display;

  • Permission settings are defined during app publishing—adjust via policy center if needed;

  • Distribution data is based on version-policy binding and only shows valid execution records;

  • Operation and system logs are retained for 30 days—consider exporting regularly;

  • Apps cannot be edited directly from the details page; use the "My Apps" main list to make changes.

3. Secondary Operations

3.1 Submit

Description

This operation is used to submit applications in “Draft” status for approval. Once submitted, the app status changes to “Pending Review” and can only be published after admin approval. If the approval process is disabled in the system, the app will directly enter “Published” status without review.

This feature applies to Enterprise Private Apps (APK) and Enterprise Web Apps and is only available for applications in draft status, ensuring content is reviewed before official release.

Notes:

  • Only applications in “Draft” status can be submitted;

  • After submission, status becomes “Pending Review”; if approval is disabled, it changes to “Published” immediately;

  • Once submitted, the app cannot be edited until reviewed;

  • Submission logic is the same for Enterprise Private Apps and Web Apps, supporting version releases and initial publishing.

Steps

  1. Access the “My Apps” Module

    • Go to the “My Apps” page to view the list of all applications;

    • Use the status filter to select “Draft” and quickly locate apps that can be submitted.

  2. Initiate Submission

    • Click the [Actions] button in the target app’s row;

    • From the dropdown, select [Submit];

    • The system executes the submission immediately without a confirmation popup.

  3. Check Status Update

    • After successful submission, the app status updates to “Pending Review”;

    • If approval is disabled, the status changes directly to “Published”;

    • Use the “Status” filter to check pending or published applications.

  4. Review and Publish (if approval is enabled)

    • Admins go to the “My Apps” list and click [Approve] to review pending apps;

    • Upon approval, the app status changes to “Published” and becomes available for policy configuration and device deployment.

Notes

  • Only draft apps can be submitted; once submitted, they cannot be edited;

  • To make changes, use the [Edit] option before submission;

  • If the approval process is disabled in system settings, submission will bypass review and publish immediately;

  • Apps in draft status support the following actions:

    • Enterprise Private Apps: View details / Edit / Delete / Manage versions;

    • Enterprise Web Apps: Edit / Delete;

  • Once the app enters “Pending Review” or “Published” status, editing and deletion are restricted;

  • Approval history and publish status can be traced via operation logs.

3.2 Approve

Description

This feature allows administrators to approve submitted Enterprise Private Apps or Enterprise Web Apps. In the “My Apps” list, admins can review apps with the “Pending Review” status. Once approved, the app status updates to “Published” and can be used in policy configuration and device deployment. If rejected, the app reverts to “Draft” status and must be edited and resubmitted.

Notes:

  • Only “Publish Enterprise Private App” and “Publish Enterprise Web App” require submission and approval;

  • Google Play public apps, private apps, and Enterprise Public Apps do not require approval;

  • If the toggle for 【System Settings → Other → My App Approval Workflow】 is turned off, submitted apps will skip the “Pending Review” state and be published immediately;

  • Approval actions are irreversible, so please confirm all details before proceeding.

Steps

  1. Open the “My Apps” Page

    • By default, all apps are displayed;

    • Use the “App Status” filter to locate all apps in “Pending Review” status.

  2. Perform Approval Action

    • Locate the pending app version and click the [Approve] button;

    • A confirmation dialog will appear: “Approve this app?”;

    • Click [Approve] to approve and publish the app;

    • Click [Reject] to revert the app status to “Draft.”

  3. View Approval Results

    • If approved, the app status updates to “Published” and can be used in policies;

    • If rejected, the status changes to “Draft,” allowing for further editing or deletion.

Notes

  • It’s recommended to assign approval rights only to admin accounts or designated app managers;

  • Approval is only available for apps in “Pending Review” status;

  • Approval outcomes are final and cannot be changed—please verify details beforehand;

  • Rejected apps revert to “Draft” and must be edited and resubmitted for another review;

  • If the approval workflow is disabled, apps are published immediately upon submission, and the approve button will not appear;

  • All approval actions are recorded in the platform’s operation logs for auditing and traceability.

3.3 Edit

Description

This feature allows editing of submitted content for Enterprise Private Apps or Enterprise Web Apps, including icon, app name, version description, display mode, and permission policy.

You can initiate editing when the app is in “Draft” or “Published” status. After editing, you may choose to either [Save] (remain in draft) or [Submit] (for approval).

Notes:

  • Only Enterprise Private Apps and Enterprise Web Apps support editing;

  • Google Play Public/Private Apps and Enterprise Public Apps cannot be edited;

  • Editing is allowed only when the app is in “Draft” or “Published” status;

  • All fields, including app information and permission settings, are editable;

  • If the approval workflow is disabled, submission will immediately publish the app.

Steps

  1. Open Edit Entry

    • On the “My Apps” page, locate the target app in “Draft” or “Published” status;

    • Click the [Actions] button on the right and select [Edit] to start editing.

  2. Edit App File / Basic Information

    • Enterprise Private App:

      • Step 1: Upload a new APK file (optional);

      • Step 2: Configure category, supported devices, description, and icon;

    • Enterprise Web App:

      • Edit the app name, URL, category, display mode, and icon;

    • All fields are editable. Click [Next] to proceed.

  3. Edit Permissions (Private App)

    • For private app versions, you can adjust camera, location, storage access, etc.;

    • Three permission modes supported: Allow / Deny / User Control;

    • After changes, click [Save] or [Submit].

  4. Save or Submit

    • [Save]: Keeps changes in “Draft” status for further editing;

    • [Submit]: Moves app to “Pending Review”;

    • If approval workflow is disabled, submission will change status to “Published” immediately.

Notes

  • Ensure the app is in “Draft” or “Published” status before editing; other statuses are not editable;

  • Editing modifies the current version directly; no new version is generated;

  • After submission, no further edits are allowed unless it is returned to draft;

  • If the approval workflow is disabled in system settings, submission results in immediate publishing;

  • When editing permission policies, review compatibility with target devices;

  • Enterprise Web Apps do not involve APK files and support field editing only.

3.4 Disable / Enable Application

Description

The "Disable / Enable Application" feature allows administrators to control whether an app can be used on devices. It supports all app types, including Google Play Public/Private Apps, Enterprise Public Apps, Enterprise Private Apps, and Enterprise Web Apps.

Notes:

  • All application types support disable/enable operations;

  • Only apps in the “Published” status can be disabled;

  • Once disabled, the app on the device becomes inactive—its icon is grayed out and cannot be launched;

  • Disabled apps are moved to the “Disabled Apps” tab;

  • From the “Disabled Apps” tab, apps can be enabled or deleted;

  • When re-enabled, the app returns to the “Published” status and becomes usable again on devices.

Steps

A. Disable Application

  1. On the “My Apps” page, filter by apps in “Published” status;

  2. Click the [Actions] button next to the target app and select [Disable];

  3. A confirmation window will appear: “Are you sure you want to disable this app?”;

  4. Click [Confirm] to proceed;

  5. The app status changes to “Disabled” and it is moved from the “All” tab to the “Disabled Apps” tab.

B. Enable Application

  1. On the “My Apps” page, switch to the “Disabled Apps” tab;

  2. Find the target app, click the [Actions] button, and select [Enable];

  3. A confirmation window will appear: “Are you sure you want to enable this app?”;

  4. Click [Confirm], and the app status will revert to “Published”;

  5. The app returns to the “All” tab and becomes available for device usage.

Notes

  • Only apps in “Published” status can be disabled;

  • Once disabled, installed apps will be grayed out and cannot be opened;

  • Disabling does not uninstall the app; it only prevents it from running;

  • Only apps in the “Disabled Apps” tab can be re-enabled;

  • Enabling does not require re-submission or approval;

  • Once enabled, the app resumes normal functionality without needing reconfiguration or re-deployment.

3.5 Delete Application

Description

The “Delete Application” feature is used to permanently remove unused apps from the system. It applies to all types of applications, including Google Play Public/Private Apps, Enterprise Public Apps, Enterprise Private Apps, and Enterprise Web Apps.

Notes:

  • All application types support deletion;

  • Only apps in the “Disabled” status can be deleted;

  • Deletion is irreversible—please proceed with caution;

  • Once deleted, the app will be removed from all associated policies. Devices will recalculate results based on the "module-level merging, with the latest config in the same module taking precedence" strategy model.

Steps

  1. Go to the “My Apps” page and switch to the “Disabled Apps” tab;

  2. Find the target app, click the [Actions] button, and select [Delete App];

  3. A confirmation window will appear: “Are you sure you want to delete this app?”;

  4. Click [Confirm] to proceed;

  5. The app will be removed from the platform, and its configurations will be automatically removed from all related policies.

Notes

Impact on Devices After Deletion

Deleting an app triggers a recalculation of policy effects according to KiwiCloud’s policy overlay logic: “module-level merging, with the latest configuration in the same module taking precedence”:

  • If the app was a "Mandatory App" or "Allowlisted App" in the active policy, it will be automatically uninstalled from the device;

  • If the app was a "Blocklisted App", the restriction will be lifted, and the app can be reinstalled on the device;

  • The device will behave entirely based on the recalculated effective policy after the app is deleted.

  • The deletion action is not reversible;

  • Once deleted, the app is completely removed from “My Apps”;

  • Deletion does not affect historical operation logs, but the app will no longer appear in policy or device configuration details.

3.6 Add New Version

Description

The “Add New Version” feature allows administrators to upload a new APK version for an Enterprise Private App, supporting scenarios such as feature updates or version iteration. The newly submitted version will go through the approval process. Once approved, it becomes effective while the previous version can be retained or disabled.

Notes:

  • Only Enterprise Private Apps support adding new versions;

  • The app must be in “Published” status to add a new version;

  • The process is similar to that of “Publishing Enterprise Private App”;

  • The new version code must be higher than the existing one;

  • Use [Version List] to view and manage version history.

Steps

  1. Enter Entry Point

    • On the My Apps page, locate the target Enterprise Private App (in “Published” status);

    • Click the [Actions] button and select [Add New Version].

  2. Upload App File

    • Upload the new APK file by drag-and-drop or file picker;

    • The system will validate that the package name matches the original app;

    • After uploading, click [Next].

  3. Configure App Information

    • Optionally update the app icon;

    • Fill in fields such as version number, category, supported devices, and description;

    • The information applies only to this version.

  4. Set Permission Policies

    • Define permissions required for the new version (e.g., storage access, location, camera);

    • Each permission supports three control modes: Allow / Deny / User Controlled.

  5. Submit for Review

    • Click [Submit] to move the new version to “Pending Review” status;

    • Once approved by the administrator, the version will be marked as “Published”;

    • The system supports multiple versions simultaneously, accessible via the Version List.

Notes

  • The package name must match the original app;

  • New versions do not overwrite old versions automatically—deployment must be configured in policies;

  • New versions require administrator approval, depending on system settings;

  • Multiple versions can coexist; older versions must be manually disabled if no longer needed;

  • Use [Version List] to view and manage the status of each version.

3.7 View Version List

Description

The Version List is used to view all historical versions of an Enterprise Private App, including version code, version name, status, and available actions. It facilitates version comparison, management, and control.

Notes:

  • Only Enterprise Private Apps support version management;

  • The app must be in the Published state to access the version list;

  • The version list supports actions such as [Add New Version] and [Disable].

Steps

  1. On the My Apps page, locate the Enterprise Private App in Published status;

  2. Click the [Actions] button and select [Version List];

  3. The system will open the Version List window, showing all historical versions of the app;

  4. In the version list, you can:

    • View each version's version code, version name, and status (Published / Disabled);

    • Perform [Disable] action on individual versions;

    • Click the [Add New Version] button in the top right to upload a new version.

Notes

  • Disabling a version only affects its policy delivery; it does not delete the app;

  • Multiple versions can coexist and be used by KMA-type app policies;

  • The deployment of different versions on devices depends on the associated KMA policy;

  • You can switch between enabling and disabling different versions at any time.

4. Configuration Items

Application configuration items are categorized based on application types and usage scenarios. The My Apps module in KiwiCloud supports the following key configuration items:

4.1 Basic Application Attributes

Configuration Item

Description

App Type

Includes: Google Play Public App, Google Play Private App (Private/Web), Enterprise Public App, Enterprise Private App, Enterprise Web App.

App Name

Display name of the app, manually entered or auto-recognized from the APK. Max 30 characters (256 characters for Web Apps).

Package Name

Android package name, automatically extracted after uploading the APK; must be unique.

App Icon

PNG/JPG format supported, recommended size: 512×512.

App Category

Default categories include: Default, Retail, Tools, etc. Managed under App Categories. Public app categories are managed by their publishers.

Display Mode

Applicable to Web Apps; options: Fullscreen, Standalone Window, Minimal UI.

Supported Device Types

Optional field for referencing supported models or types, with no strict restrictions.

App Description

Optional field to describe the app’s purpose, version highlights, etc.

4.2 Permission Configuration (Enterprise Private Apps)

Note: Permissions are automatically extracted from the APK. The control settings are only applicable during the upload of Enterprise Private Apps and can be modified later via the Edit action.

Permission Item

Control Mode

Description

Camera Access

Allow / Deny / User Control

Controls whether the app can access the camera.

Location Info

Allow / Deny / User Control

Controls whether the app can access device location data.

Storage Access

Allow / Deny / User Control

Controls whether the app can read/write external storage (e.g., SD card).

Microphone Access

Allow / Deny / User Control

Controls whether the app can access the microphone.

Contacts Access

Allow / Deny / User Control

Controls whether the app can access contact information (if requested).

Phone State Access

Allow / Deny / User Control

Controls whether the app can access phone state information.

...

...

...

4.3 Web App Attributes

Configuration Item

Description

URL

Web App access URL, must begin with a secure https:// prefix.

Icon

PNG/JPG format, recommended size: 512×512.

Display Mode

Options: Fullscreen, Standalone Window, Minimal UI; determines how the app is rendered on the device.

4.4 Version Management

Configuration Item

Description

Version Number

Automatically extracted after APK upload, e.g., 1.0.3, 2.0.1.

Version Status

Includes: Draft, Pending Review, Published, Disabled — affects availability and policy assignment.

Add New Version

Enterprise Private Apps can have new versions added; versions coexist and can be assigned with permissions. New versions must have higher version numbers.

Disable Version

Deprecated versions can be disabled to prevent further delivery.

4.5 Status & Approval

Configuration Item

Description

Approval Status

Includes: Pending Review, Approved, Rejected; applies only to Enterprise Private/Web Apps.

Enable / Disable State

Controls whether the app can run on the device. In “Disabled” state, icons are greyed out and apps are inaccessible.

Delete App

Only available in “Disabled” state. Once deleted, related policy delivery will be affected.

Did this answer your question?