Behavior, the build, and a version to install
ROKALO LTD has spent years making mobile apps for people who carry them through an ordinary day. The work is on iOS and on Android. It runs through how an app should behave when a thumb is in a hurry, through the build that turns those decisions into software, and through a version a person can install on a phone they already own. We stay with that sequence until the install is real. Screens, states, and the quiet rules between them are part of the same job as the release, so the product that leaves the studio still behaves the way it was meant to.
Both platforms, finished
A product from this studio is made for both platforms, not parked on one of them. The same purpose is built for iOS and for Android, while the controls, type, and habits of each system stay familiar to the person holding the phone. Shared work stays shared underneath. What differs is the surface a person actually touches. Neither version is a leftover of the other, and neither ships as a sketch that only the studio can open.
From the need to the install
Work begins with what the app needs to do, said plainly enough that a person outside the studio could repeat it. Those needs become screens, states, and the passages between them. After that comes the build: the code, the checks, and the hours on real devices where a behavior either holds or fails. The path ends as a version someone can install, signed and ready for a phone, rather than a demonstration that only runs on a machine in the studio.
An assistant, not a person
An assistant in the product can talk with the user. It is not a human sitting behind the screen, and it is not professional advice of any kind. It answers inside the product, about what the person just asked. What someone writes is used to answer that person. It is not passed to other users, and it is not folded into a conversation the rest of the audience can open or read.
Nothing passed between users
There is no personal profile to complete, and nothing in the product asks people to describe themselves to one another. Users do not send personal data to each other. Attribution uses Singular. Pushes use OneSignal. The identifying item is a unique id, used so those services can attribute an install and deliver a push. How that id is handled is written on Privacy, one fact at a time.
Write when you need a person
ROKALO LTD is the developer behind these apps. If a product, a release, or an install needs a question asked of a person, write to [email protected] and the letter will be read. Read Privacy for what the app handles and what it refuses to collect. Read Terms for how the product may be used, and for what happens when those terms change. When either page leaves a point unfinished, write to the developer and say what you need resolved.