Document App Generator

The installer title and launcher label - what users see in the app drawer and on the home screen.

The colour behind the splash screen and the system bars while the app launches - the first thing a user sees. Separate from the Accent below, which tints the in-app document library. A baked default; pick something close to your brand.

512 x 512 px PNG or JPEG recommended (for Play Store quality; optionally maskable). Built into an adaptive launcher icon. Not stored server-side, so re-attach it on each rebuild. A default icon is used if you skip it.

Tints folders, the active navigation item, and selection states throughout the library. Accepts #rgb or #rrggbb; the app flips foreground text between dark and light automatically for contrast. A baked default your EMM can re-tint at runtime via managed configuration (branding_accent).

The theme the app opens with. Auto follows the device's day/night setting. A baked default your EMM can change at runtime via branding_theme_mode; it is a managed default, not a lock, so the user's in-app choice takes precedence.

How the library first appears - List packs more documents per screen; Gallery shows tiles with thumbnails, better for visual documents. A baked default the user can switch in-app; your EMM can override it via ui_default_view.

Each document is a file the app makes available - baked into the APK for offline use, or fetched from a URL on your intranet. Add at least one. Drop files or a whole folder below to add several at once, or add them one at a time. Your EMM can replace the whole set later via managed config.

None yet - drop files above or add one below.

Optional groups for organising the library. Define a folder here (name, id, colour), then assign documents to it through each document's Folder dropdown. Folders are a baked default your EMM can override via documents_folders.

How often the app refreshes its document list and re-fetches URL sources in the background. Minimum 15 minutes (Android coalesces background work).

On top of the interval: config change refreshes as soon as your EMM pushes a new configuration; network available catches up after the device regains connectivity; Wi-Fi only skips syncing on metered mobile data.

How long a slow URL source can stall a sync before it is abandoned. Built-in documents are unaffected.

Off by default - URL sources are fetched over HTTPS only. Baked at build time: a build made HTTPS-only blocks cleartext at the OS level, so turning network_allow_http on later via managed config will not enable an http:// source without a rebuild.

APK installs directly - sideload, ADB, or direct EMM push. AAB is for publishing a private app through Managed Google Play.

Enter the code from a previous build to reuse the same Android package name - required for EMM silent-update flows. Leave blank to create a new app with a fresh package name.