The iOS face
Sheets, system type, and the back gesture stay familiar. Navigation, spacing, and the assistant are drawn for this face before a line of interface code is treated as done. The plan is shared. The finish is not borrowed from Android.
Mobile apps for iOS and Android
One ridge, two faces.
S PAYNE SERVICES LTD cuts one product for both slopes. Behavior, design, build, testing, release, and the updates that follow are planned as a single span, then finished for iOS and for Android.
- iOS
- Android
- One shared plan
In-app assistant
YouAre you a person?
GuideNo. I am the in-app assistant. I am not a human.
YouIs this professional advice?
GuideNo. What you write is used only to answer you. It is not passed to other users.
iOS and Android
Both faces of the ridge
Every product is made for both platforms. The faces are not a phone-shaped copy of each other. Each one uses the habits of its system, and both follow the same plan.
The Android face
Material patterns, predictive back, and notification channels are respected. The same screens and the same assistant script land here, rebuilt so the app feels at home on the device people already use. Nothing is a shrunk export of the other build.
How the studio works
Setting the span
The studio has built mobile apps for years. The work is the whole trail: what the app does, how both faces look, the build, the testing, the release, and the updates after people install it.
The left peak is the iOS face. The right peak is the Android face. The arch is the shared plan: one behavior, two finished builds.
Behavior comes first. We name every action a person can take, including the empty screen, the failed send, and the sentence the assistant is allowed to say. Design starts only after that list can be read without guessing.
Design is drawn twice. Type, touch targets, motion, and the places a task can stall are decided for iOS and for Android from the same plan. A screen that exists on one face and not the other is a decision, written down, not an accident of the schedule.
The build follows those drawings. Each face is implemented so system controls still feel like the platform. The checklist is shared, which is how the two builds stay one product when the stores are separate.
Testing uses real devices, a slow network, large type, and the assistant's script. Release means both listings. Updates mean the studio stays: a fix on one face is matched on the other unless the platforms themselves differ.
From first note to the update
Five stakes
Five marks, in order. Each one has to hold before the next is trusted.
Behavior
Write what a person can do, what the app does in return, and what must never happen. The assistant's limits belong in this list, not in a footnote after launch.
Design
Draw both faces. Spacing, type, and the path through a task are settled on screen before code freezes them into the wrong shape.
Build
Implement each face against the shared checklist. Platform habits stay. The product underneath them does not fork into two different apps.
Testing
Run the builds on devices, with large text, on a weak connection, and through the assistant line by line. A pass on a simulator is not the last word.
Release and updates
Ship to both stores. Then keep the span: fixes, store changes, and later additions land on iOS and Android from the same decision.
Questions
Asked at the col
Straight answers about the two faces, the assistant, and what the apps do with information.
Do you ship every product on both iOS and Android?
Yes. A product from this studio is made for both platforms. The shared plan covers behavior and the assistant. Each face is then finished with the controls and patterns of its own system.
What work sits inside a project?
Behavior, design, build, testing, release, and updates. The studio has done that mobile work for years. A launch is the fifth stake, not the end of the trail. Fixes after release are part of the same span.
Is the in-app assistant a person?
No. The assistant can talk with people inside the app. It is not a human, and it is not someone from the studio typing in a hidden window. If you want a person, write to the studio from the contacts page.
Can the assistant give professional advice?
No. It does not give legal, medical, financial, or any other professional advice. It answers inside the limits of the product. For licensed counsel, ask a qualified person.
Are my messages passed to other users?
No. What you write is used only to answer you. It is not passed to other users, not posted for them to read, and not used as a way for one person to reach another.
Do the apps build a profile of me?
No. They do not collect your name, email, phone number, contacts, or precise location as product data. There is no personal profile sitting behind the install.
What are Singular and OneSignal for?
Singular handles attribution, so the studio can tell which listing led to an install. OneSignal handles push notifications. The only identifying item for those two jobs is a unique id. It is not your name, and it is not a channel between users.
How do I reach the studio?
Use the contacts page. The form opens your email app with the subject and message filled in. You can also write directly. The privacy note and the terms are linked there and in the footer.
Engineering
Cuts in the rock
Six checks that sit on the shared plan. They apply to both faces.
Native feel
Gestures, type, and back behavior stay recognizable on each platform. The shared plan does not sand both faces down into one foreign skin.
Accessibility
Labels, contrast, focus order, and large type are part of the build. A control that only makes sense if you can see a color is sent back.
Performance
Screens open without a stall, and the assistant does not freeze the rest of the interface while it replies. Weight is watched on both builds.
Offline
The last screen a person reached should still open without a signal. Anything that needs a network says so in words, not with a spinner that never ends.
Updates
A change to behavior is written once, then applied on iOS and Android. Store updates are how the span stays true after release.
Testing
Devices, slow networks, interrupted sessions, large type, and the assistant's script are on the list before either listing goes live.
In-app assistant
Voice on the ridge
The apps include an assistant people can talk to. It answers inside the product. It is not a member of the studio, it is not a human, and it is not a stand-in for professional advice.
Text a person writes is used only to form that reply. It is not shown to other users. It is not stored as a portrait of who they are. The apps build no personal profile, and users do not send personal data to each other.
If you want a human answer, write to the studio. The assistant will not pretend to be that letter.
Sample exchange
YouDo you keep a file on me?
GuideNo. There is no personal profile. No name, email, phone, contacts, or precise location.
YouWhat identifies the install?
GuideA unique id. Singular uses it for attribution. OneSignal uses it for push. It is not shared with other users.
Privacy, in short
Nothing crosses the col
The full note is on the privacy page. This is the shape of it.
PhoneThe app on the device
Unique idThe only identifier
SingularAttribution
OneSignalPush notifications
User — no path — User. People do not send personal data to each other.
Attribution uses Singular. Push notifications use OneSignal. Both are tied to a unique id, not to a name you typed. That id is the only identifying item.
There is no personal profile: no name, email, phone number, contacts, or precise location in the product data. Messages to the assistant stay in that reply. They are not handed across to someone else.
Contact
Signal from the pass
Write to S PAYNE SERVICES LTD. Mail goes to [email protected]. The privacy note and the terms sit beside this page if you want the limits in full before you write.