04
Open on this phone
Assistant
Not a person. Berth 4 is marked open until 21:00.
iOS frame
Night dock
The knock carries to both shores.
RAK DOKY LTD has spent years making mobile apps for iOS and Android. The work runs from behavior and design through the build, testing, release, and the updates that follow a version already in people's hands.
- iOS and Android together
- One shared plan
- A unique id, not a profile
04
Same mark, this shore
Assistant
Not a person. Berth 4 is marked open until 21:00.
Android frame
Platforms
Two berths, one pier
Every product is made for both platforms. iOS and Android are planned as two berths on the same pier, not as a finished hull and a later copy. Navigation, wording, and the way a screen answers a thumb are decided with both shores in view.
What should feel at home on the phone stays with that platform. The iOS frame keeps its island, its type rhythm, and the habit of a back swipe. The Android frame keeps its own status logic, its gesture bar, and the notification shade people already know. What must not drift stays shared: the task, the assistant's limits, and the rule that one person is not sending personal data to another.
Testing covers both. A release is ready only when both builds are. An update ships to both, so a fix does not live on one shore while the other is still waiting for it.
Process
Along the pier
A product moves in one direction: from the first conversation to a version people can install, then back again when something has to change. Both platforms walk that length together.
-
01
Behavior
What the app must do, and what it must refuse. The assistant's limits are written here, before any screen looks finished.
-
02
Design
Screens, empty states, and the path a thumb actually takes. iOS and Android sit on the table at the same time.
-
03
Build
An interface that feels at home on each system, with logic that does not fork into two products.
-
04
Testing
Whole flows, a fresh install, an update over an older build, and checks that a screen can be used without perfect eyes or hands.
-
05
Release
Listings, builds, and the week after, when phones outside the studio show what a quiet room missed.
-
06
Updates
Later versions, still for both platforms, with the same care as the first knock on the timber.
Questions
At the rail
Straight answers about platforms, the assistant, and the one identifier these apps keep.
Is every app made for both iOS and Android?
Yes. RAK DOKY LTD treats the two platforms as one product. Behavior, design, the build, testing, release, and updates are planned for both. A second platform is not a leftover phase that starts after the first one is tired.
What does the in-app assistant do?
It can talk with the person using the app. It answers inside that conversation so the task on the screen can continue. It is not a human on the other end, and it is not professional advice. A reply is not a stand-in for a lawyer, a doctor, or any other specialist.
Are messages shared with other users?
No. What someone writes is used only to answer that person. It is not passed to other users. The apps are not a channel between people, and there is no shared inbox hiding under the pier.
Do the apps build a personal profile?
No. They do not collect a name, an email address, a phone number, a contact list, or a precise location in order to describe who someone is. There is no profile whose job is to follow a person from one service to another.
What is the unique id?
The only identifying item is a unique id. It lets attribution and push notifications tell one installation from another. It is not a name. In these apps it is not tied to an email address or a phone number, and another user cannot use it to find you.
Why Singular and OneSignal?
Attribution uses Singular, so the studio can see which listing or campaign led to an install. Push notifications use OneSignal, so a notice can reach that installation. Nothing sits between users. The unique id is the identifier those services receive from these apps.
How do I reach the studio?
Write to RAK DOKY LTD at [email protected]. The privacy note and the terms sit beside that address. Email is read by the studio. It is not mixed into the unique id, and it is not shown to other users.
Approach
Six planks
The hull is the same on both shores. These are the planks the studio will not leave out of a build.
-
Native feel
Controls, type, and motion follow the platform a person already knows. A shared plan does not mean a foreign set of gestures pasted onto both shores. The thumb should meet a control where that system taught it to look.
-
Accessibility
Type can grow. Contrast holds on the night water. Actions are reachable without a perfect, tiny gesture. A screen that only works for one kind of hand is not finished.
-
Performance
Screens stay light. Motion is a change of position or opacity, not a filter working the whole display. The phone should not heat up to prove that the studio was busy.
-
Offline
A task that can be done on the device does not wait on a perfect signal. When a reply from the assistant needs the network, the app says so instead of pretending the lantern is still lit.
-
Updates
A later version is part of the build, not an apology pinned on afterwards. Both platforms receive it. One shore does not keep a repair the other has not seen.
-
Testing
Real flows, both families of phone, and the dull cases: deny a permission, rotate, leave, come back a week later. The interesting path is not the only path that has to work.
Demonstration
A scripted echo
The bubbles beside this note appear as you reach the rail. They are written in advance. There is no field, and nothing you read here is a live person.
The tone is the one the in-app assistant is allowed to keep: short, limited, and unwilling to pretend. It can point at what the screen already shows. It cannot pass a note to another crew, and it cannot give advice a specialist would have to own.
On the phoneIs berth 4 free tonight?
AssistantI can only see the pier log on this phone. Berth 4 is marked held until 22:00. I am not a person, and this is not a booking.
On the phoneTell the other crew I am late.
AssistantNo. Notes written here are used only to answer you. They are not passed to other users.
AssistantI also cannot tell you whether to sail. That is not professional advice. For a human reply, write to the studio.
The assistant
Not a person on the line
It can answer. It cannot stand in for a person.
The in-app assistant can talk with users. That is the whole of its role. It is not a human. It is not professional advice. What someone writes is used only to answer, and it is not passed to other users.
The apps build no personal profile. Users do not send personal data to each other. If a question needs a judgment a person must own, the honest reply is to say so and point toward the studio's address.
Privacy
What crosses the water
Attribution uses Singular. Push notifications use OneSignal. The only identifying item is a unique id. There is no second copy of a person gathered to build a profile: no name, no email address, no phone number, no contact list, and no precise location.
The drawing shows the path. A phone keeps a unique id. That id is what Singular uses for attribution and what OneSignal uses for push. There is no line from one user to another. The apps do not hand personal data across that gap, because they do not collect it for a profile in the first place.
Read the privacy note and the terms before you write. Questions go to RAK DOKY LTD at [email protected].
Contact
Hail the yard
RAK DOKY LTD
The studio reads what you send. This address is a real mailbox. It is not joined to the unique id inside an app, and it is not shown to other users.