Records desk
OFFICE CRAP PTY LTD has built mobile apps for years. The desk covers iOS and Android from the first behavior note through design, build, testing, release, and the updates that follow. Every product is made for both platforms. One file is written, then placed in both trays.
Twin trays
iOS and Android are filled from the same plan. Neither tray is a later copy of the other.
Gestures, type, and the way a screen opens stay native to that system. The product underneath is the shared file: the same tasks, the same empty states, the same release. Behavior is not rewritten because the phone looks different.
Back navigation, the notification shade, and the system’s own controls are handled as Android expects. This tray is filled in the same pass. It is not an afterthought waiting on the other platform to finish first.
How the work moves
Six marks, in order. A screen that looks finished still waits for the marks above it.
What the app does is written before it is drawn. The path a person takes, the empty day, the failed request, and the next tap all get a line on the slip.
Each screen is drafted like a form. Hierarchy, type, and the one action the view is for. A mark that does not serve that action does not stay on the sheet.
The file is built for iOS and Android together. A decision made in one tray is carried into the other while the work is still open, not rediscovered after release.
The behavior list is walked on both platforms. Edge cases are part of the pass. They are not a surprise saved for the week a build is supposed to leave the desk.
The stamp is the release. Builds are prepared, notes are written, and both trays go out under the same plan. One platform is not held back as a silent draft.
After release the file stays open. Fixes and later changes use the same slip, so an update does not quietly become a second product with a second set of rules.
Drawer labels
The scope of the studio, written as labels. Each one is a piece of the work, not a slogan beside it.
Every product is built for iOS and Android. There is no single-tray release. The shared plan names both systems from the behavior mark onward, and the stamp does not come down until both trays are filled.
Behavior, design, build, testing, release, and updates stay on one list so the trays do not drift apart over a long build.
The in-app assistant can talk with a person inside the app. It is not a human, and it is not professional advice.
The apps build no personal profile. People do not send personal data to each other. The drawer does not keep a name.
Attribution uses Singular. The only identifying item sent for that purpose is a unique id.
Push notifications use OneSignal, addressed with that same unique id. A notification does not need a personal profile to arrive.
Route card
Two doors leave the device. Nothing passes between people.
A record leaves an install by two doors only. Attribution goes to Singular. Push notifications go to OneSignal. Both doors use a unique id, and that id is the only identifying item. The apps do not build a personal profile. They do not take a name, an email address, a phone number, a contact list, or a precise location and store it as who someone is.
There is no path between users. What one person writes is not handed to another. A message to the assistant is used only to answer that person, and it is not passed on. The drawing is the whole route: the install, the two services, and a closed gap where a second user receives nothing.
Ledger line
Four figures this desk will stand behind. No invented totals.
2 platforms
1 shared plan
0 user-to-user data
1 unique id
In the app
An assistant that can talk. It is not a person, and it is not professional advice.
Inside the product, a person can talk with an assistant. It can answer questions about how the app works. It is not a human at this desk. It does not give professional advice of any kind. What someone writes is used only to answer that person. The message is not passed to other users, and it is not turned into a profile.
The clerk does not know a name, because the app does not ask for one. It does not read a contact list. It does not trade notes with another install. A confident reply is still software, and it is still not a professional opinion. If you need a person, write to the studio. The clerk cannot take that letter.
You Can you pull up my account?
Clerk I can talk through how this app works. I am not a person, and this is not professional advice. There is no profile to open.
You Will another user read what I write?
Clerk No. Your message is used to reply to you. It is not passed to anyone else.
Privacy, short
A unique id, a route to Singular, a route to OneSignal. Not a profile of a person.
The apps do not collect a name, email, phone number, contact list, or precise location in order to describe who someone is. There is no account page that stores a person.
Users do not send personal data to each other. The assistant’s words stay with the person who asked. Singular and OneSignal are not a channel between installs.
Attribution uses Singular. Push uses OneSignal. The only identifying item for those two jobs is a unique id. It is not a name, and it is not shared from one user to another.
The in-tray
Write to the developer. The note goes by email, from your own mail app. Read the privacy note and the terms if you want the long version before you send anything.
OFFICE CRAP PTY LTD