Install myJikita
myJikita runs on iOS and Android and is free to download.
Requirements
| Android | Android 8.0 (Oreo) or later, with GPS. Bluetooth is needed only if you use a Jikita tag. |
| iOS | iOS 14 or later, with GPS. |
| Storage | A few tens of MB for the app, plus whatever you choose to download as offline maps — a large area can be several hundred MB. |
| Account | A free Alpik account. You can create one from the app — see Create your account. |
| Network | An internet connection to sign in and to share positions. The app is designed to keep working without one once you are set up. |
Download
The App Store and Google Play links go here once the listings are published.
The application id is com.jikita.my on both platforms.
- Android — Google Play: link to be added
- iOS — App Store: link to be added
File: img/myjikita/install-01-store.png
Shows: The myJikita store listing on Google Play / the App Store.
First launch
The first time you open myJikita you will see the sign-in screen with the myJikita mark. From here you can either sign in with an existing Alpik account or create one — both are covered in Create your account.
File: img/myjikita/install-02-login.png
Shows: The sign-in screen with the myJikita mark, tagline, and the Sign in
and Create an account buttons.
After signing in, the app asks for the permissions it needs to do its job. It explains each one before the system dialog appears, so you always know what is being asked and why. Do not skip these — the location permission in particular decides whether tracking survives your phone going into your pocket. Work through Permissions before your first real outing.
Then you land on the map, with your own position on it once the first GPS fix arrives.
If you are upgrading from an earlier build
Testers who installed the app while it was still called ALPIK or myALPIK must uninstall the old version and install myJikita fresh. The application identifier changed before publication, which means the two are different installations to the phone: the old one will not update itself, will not remove itself, and its locally stored outings cannot be recovered.
If you have unsynced outings on the old build, let it sync while you have signal before you remove it.
Next: Create your account