Branded mobile application build

Console branding does not automatically change the mobile application, its icon, package identifier, or signature. Likewise, AppConfig passes supported parameters to the application but does not rename or rebuild it.

Preparing a mobile build is a separate, agreed process. Before starting, you need to determine the application and platforms, provide brand materials, and agree on the application identifier, server addresses, notifications, signing, and the update method. Then the specific variant must be built, and the installation, connection to the required environment, sign-in, notifications, and update must be verified on test devices.

The availability of specific changes depends on the source application and the agreed scope of work. Do not consider a generator or a ready-made custom build to be an available console feature without confirmation for your project. In the case of AMAPI, the Android Device Policy application remains Google’s agent; a branded Aitera build does not replace it.

Workspace parameters · AppConfig setup · Android channel comparison