Getting and installing the mobile app
Where the platform's Android application is downloaded, the difference between the two files, and how it is installed and updated on a phone.
The applications built in Keplin run in the browser of any computer or phone. On an Android phone there is a second way to use them: the platform's mobile application, KeplinGo. You install it once and it opens every app of this installation, each one with its own shortcut on the home screen, with its own name and icon.
KeplinGo shows the same screens as the browser, with everything they have, custom widgets included. What it adds is access to the device: the GPS position, the camera, and opening reports, exports, and attachments in the phone's apps.
Where the app is
- Open Settings in the left sidebar, in the administration area.

- Scroll down to the Mobile app panel: "The Android app used to enter this platform's apps."

Note
The panel only exists in the platform Settings, which belong to whoever administers it. With a developer profile, the menu doesn't appear: ask an administrator to give you the file.
The two files
The panel has two rows:
| Row | What it's for |
|---|---|
| APK | The file you install directly on an Android phone. This is the one you want. |
| AAB | The store publishing format. Only relevant to whoever distributes the app through the organization's Play Store. |

Each row shows the file name and the size in MB, and has a Download button. While the platform checks what it has available, the row says "Checking…".
If, instead of the size, you see "Not available on this installation yet.", the Download button is disabled: this installation doesn't have that file yet. It isn't a configuration error. Talk to whoever administers the installation.
Install on an Android phone
- In Settings, click Download in the APK row.
- Move the file to the phone: by email, through a shared folder, or by downloading it on the phone itself, with the platform open in its browser.
- On the phone, open the file. Android asks for permission to install apps from this source, which is the normal request for apps that don't come from the store. Allow it.
- Confirm the installation. KeplinGo appears in the phone's app list.
KeplinGo is generic: right after installing, it knows nothing about your installation or your apps. Adding an app is the subject of the next page, Connecting the phone to an app.
Tip
One KeplinGo, many apps. There isn't one Android app per application you build: the same KeplinGo adds every app the person needs, and each one gets its own shortcut on the home screen.
Publish to the organization's store
The AAB file exists for whoever wants to distribute the application through the usual channels: the Play Store, or the company's device management console. Download it with the same button, in the panel's second row.

This is the way to go when phones are managed centrally and it isn't practical to ask each person to allow the installation of a loose file.
Update the app
KeplinGo is updated by replacing the file: download the new APK from the same panel and install it over the old one. The configured apps, the shortcuts, and the sessions are kept.
The content needs no update: screens, data, and rules always come from the server. A change you make in the editor appears the next time the screen opens, without installing anything. The APK only changes when KeplinGo itself changes, and its version is the version of the platform that built it.
Note
Anyone who had KeplinGo version 2.19 or earlier sees the address screen again after updating: the app now stores the configured apps in a different way. Scan the app's QR code again.
Why don't I see…?
- …the Mobile app panel? You're in the settings of an app. The panel lives in the platform Settings, in the sidebar menu.
- …the Download button enabled? The row says "Not available on this installation yet.": this installation doesn't have that file to give.
- …a version for iPhone? KeplinGo is Android only. On an iPhone, the applications are used in the browser, at the published address.