Push
Orbit note
Both builds are ready to test. The notice goes out through OneSignal.
KEPLER & VALE LTD
Mobile apps for iOS and Android, plotted as one orbit. The name ticks like a planet on a clock, then settles into a vale. The work follows that same measured path.
Push
Orbit note
Both builds are ready to test. The notice goes out through OneSignal.
Assistant
I can describe this screen. I am not a human, and this is not professional advice.
Paired release
iOS and Android stay on one plan.
On for both platforms.
Path 04 / 05
Testing the same tasks on both builds.
02 — Platforms
iOS and Android are two frames around one product. Navigation, type, and the way a screen closes follow the habits of the phone in your hand. The plan behind those screens is shared. A task you can finish on one platform exists on the other. A release is cut for both.
We have built mobile apps for years, and every product is made for both platforms. Behavior, design, build, testing, release, and the updates that come after are decided together. We do not keep a full product in one store and a thinner copy in the other. The assistant, the notifications, and the attribution path are part of both builds.
The studio’s job is the whole arc: what the app does, how it looks, how it is built, how it is tested, how it ships, and how it stays in step after people install it.
iOS
Shared orbit
Assistant: I can walk through this setting. I am not a person.
Same plan as the Android build.
Android
Same plan
OneSignal
Update ready on both platforms.
Paired release
Singular counts the install. The address is a unique id.
03 — Method
Six stations, kept in order, so the two platforms do not drift apart.
Plotting starts with behavior. Before a layout exists, we write what a person can do, what the app does in reply, and what happens with no network. Design comes next, as screens that can be built twice without splitting the idea. The build is where iOS and Android diverge in code and meet again in the result.
Testing walks the same tasks on both phones. Release is a paired event. Updates return to that same list, so a later version does not quietly become two products. We would rather hold a screen than ship a behavior only one platform understands.
04 — Release rhythm
A single product, counted out loud. Each tick is a gate both platforms pass.
Write the tasks, the replies, and the offline state before any pixel is treated as final.
Draw the interface in the language of each platform, still describing one product.
Implement both clients so a setting, a notice, and the assistant exist on each.
Run the same path on iOS and Android, including first launch and a dead network.
Ship the pair, then keep later updates on that same orbit instead of letting them fork.
05 — Notes
Plain answers about platforms, the assistant, and the little the apps keep.
Yes. A product from this studio is planned, designed, built, tested, released, and updated for both platforms. We do not ship a complete app on one and a reduced copy on the other.
No. The assistant is software. It can talk with you inside the app. It is not a human reading the thread and typing back.
No. A reply is not legal, medical, financial, or any other professional advice. It responds to what you wrote about the product. Decisions stay with you.
No. What you write is used only to answer you. It is not passed to other users. The apps are not a way for people to send personal data to each other.
No. The apps do not collect your name, email address, phone number, contacts, or precise location. There is no profile to attach them to. Leave those details out of the chat.
Singular attributes an install. OneSignal delivers a push notification if you allow one. The only identifying item either service receives from the app is a unique id. That id is not your name, and it is not shared with other users.
Email the developer, or use the contact page, which opens your own email app. [email protected] Privacy and terms are linked from the footer.
06 — Practice
Six checks we repeat on every product, on both platforms.
Controls, type, and navigation follow the platform you are holding. The shared plan is the behavior, not a costume of identical pixels where the phone expects something else.
Text can scale. Contrast is checked. Tap targets are sized for fingers. Screens are labeled so a screen reader can move through them in order.
Screens should open quickly on ordinary phones. We test on modest hardware, not only on the newest device in the room. Motion is kept for changes that need it.
If the network drops, the app should say so and keep the last safe state. A task that cannot finish is marked, not silently lost.
When behavior changes, the update ships for iOS and Android together. Notes for the two builds describe the same change.
The same task list runs on both platforms before release: first launch, the assistant, a notification, and the path with no network.
07 — Assistant
The in-app assistant can talk with the person using the app. It explains screens, settings, and the next step in a task. That is the size of its job.
It is not a human. It does not give professional advice. What someone writes is used only to answer that person. The words are not passed to other users, and they are not stored as a personal profile. The apps do not collect a name, an email address, a phone number, contacts, or precise location to build one.
If you need the studio, write to us. The assistant cannot take that letter, and it should not be given secrets it has no reason to hold.
Can you walk me through this setting?
I can describe how it works in the app. I am not a human, and this is not professional advice.
Will another person see what I wrote?
No. Your words are used to answer you. They are not passed to other users.
The reply stays with the person who asked.
08 — Privacy
Attribution, notifications, and the assistant each have a narrow job. The privacy note spells them out. This is the map.
No path carries personal data from one user to another.
No name, email, phone number, contacts, or precise location is collected to describe you.
Users do not send personal data to each other. The assistant answers you and stops there.
Singular and OneSignal see a unique id, not a dossier. Read the full note before you write to us.
09 — Contact
Write to the developer about a product, a release, or this site. The contact page opens your email app and does not keep a copy here.
KEPLER & VALE LTD