One address per application
- Every application has its own directory,
/app/<appID>/, with its own page, Service Worker and offline page – branded with the application's name, in the nine client languages, and reconnecting by itself. - The address
/iiziApp.html?0:0&app=<appID>of earlier versions answers with a redirect to/app/<appID>/. - No password travels in an application's address any more: the page removes
pw,password,prtandvfrom the address bar before it runs anything else, and the server's request log masks them.
Installable web apps (PWA)
- An application with PWA settings (
.iiziPWA) also gets a web app manifest per language, its icons and the head tags that let a Browser install it. - Icons from one image. A master icon (a square PNG of at least 512 × 512 pixels, required) and optional maskable, monochrome and Apple touch icons, or files in the module's
assets/PWA/folder; missing sizes are generated from the master, fitted to each platform's safe zone. The same master also generates the missing files of the application's iiziRun icon set. - Dark-mode icons. An application can have an icon for dark mode (“Icon (vector, dark)” and “Icon (bitmap, dark)” on iiziGo's App page), which the server's
/appspage and iiziRun show in dark mode. - Screenshots, a category and an orientation go into the manifest; the application's name, description and colors come from the App. An application without colors of its own uses the IIZI theme's: theme color #f5f5f5 in light and #2c2c2c in dark, and #e0e0e0 behind the splash screen and the generated icons.
- iiziGo's PWA page picks its icons from the module's own assets, says what OK writes and where, and fills the empty icon fields with the files it generated from the master.
Installing a web app
IIZI 5.0 shows no install button of its own; the user installs from the Browser, over HTTPS:
- Windows, Chrome: the install icon in the address bar, or the Browser menu's install entry.
- macOS, Safari: File, “Add to Dock”.
- Android, Chrome: the menu, “Install app” (or “Add to Home screen”).
- iPhone and iPad, Safari: Share, “Add to Home Screen”.
Menu wording can differ between Browser versions. An application without a master icon is not offered for installation.
One web app per server address on Android. Chrome on Android installs one web app per origin (scheme, host name and port). Two IIZI applications served from the same server address cannot both be installed on the same Android device.
Web Analytics for application developers
- An application can name its Google Analytics 4 Measurement ID on iiziGo's App page; IDs of the retired Universal Analytics are refused.
- GA4 tells a Browser tab from an installed web app: the event parameter and the user property
iizi_display_modearebrowserorinstalled. To report on them, register both in the GA4 property (Admin, Custom definitions: a dimension of event scope on the parameteriizi_display_mode, and one of user scope on the user property of the same name). - Application Java sends its own events through
sendStat. Event names follow GA4's rule (letters, digits and_) in every sender: a-becomes_; a name still not valid, or one GA4 or Firebase reserves (such assession_startorfirst_visit), is refused with one WARNING in the server log; text values are cut to 100 characters.
Data collection and consent
Status of this section. This section, dated November 1, 2026, describes the behavior of IIZI version 5.0 software published by Mindus SARL, Monaco. It does not form part of, and does not amend or supplement, the license agreement published at https://www.mindus.co/license-agreement or the privacy policy published at https://www.mindus.co/privacy-policy, which alone govern.
Definitions. In this section, “Application” means an application built with IIZI and served by iiziServer; “Operator” means the person or entity that runs the iiziServer serving an Application; “End User” means a person using an Application in a Browser, an installed web app or iiziRun; “Measurement ID” means a Google Analytics 4 measurement identifier entered in an Application's settings.
- Applications. An Application sends analytics data only where a Measurement ID is entered in its settings. By default, IIZI asks the End User's consent, naming the Application, when the Application is launched, and sends no analytics data before consent is given. The Application may instead obtain consent itself (
setAnalyticsConsent), or be configured not to ask; that configuration is made by the developer and the Operator of the Application. - Storage of the decision. The End User's decision is kept in the Browser's local storage for the Application's address. IIZI 5.0 sets no cookie of its own.
- iiziRun. iiziRun does not use an Application's Measurement ID, and iiziRun Developer or iiziRun Custom opened in a Browser sends no analytics data.
- Usage statistics of iiziRun. iiziRun Developer, iiziRun Custom and every Customized iiziRun built with iiziGo 5 ask at their first start whether usage statistics may be sent, and send none until the End User answers yes; Firebase Analytics collection starts disabled on Android and iOS and is enabled only by that answer. The “Usage statistics” switch in Settings disables it again.
- Data not sent. From the 5.0 store builds onwards, iiziRun does not send GPS position, device serial number, device UUID or the signed-in user's name to Firebase Analytics. Its error event is sent with e-mail addresses and URL query strings removed from its message and source.