Both decksnow
iOS and Android share this plan. The release is prepared for both stores, not one.
CIRRUS AERO LTD
One flight plan, drawn for both platforms.
The studio has built mobile apps for years, for iOS and Android. Behavior, design, build, testing, release, and the updates that follow are written as one plan, then carried out on both platforms. There is not a second, thinner app waiting on the other store.
Cabin assistantnow
The in-app assistant can reply. It is not a person, and your words are not passed to other users.
Unique idnow
Attribution uses Singular. Push uses OneSignal. The only identifier is a unique id.
02 — Platforms
Both decks
Every product is made for both platforms. iOS and Android are two decks of one aircraft, not a main cabin and a leftover seat. The shared plan names behavior, design, build, testing, release, and updates once, then each platform receives that work in its own habits.
iOS
The same route, iOS habits
Sheets, type, and navigation follow the system a person already knows. The specimen below is a layout study, not a client product: a route line, an assistant reply, and a control that stays easy to reach.
Specimen09:41
Today’s route
Both stores stay on one plan.
Assistant
Android
The same route, Android habits
System navigation, the back path, and inputs sit where Android expects them. The build is not an iOS screen stretched onto another phone. Testing, release, and later updates follow the same plan.
Specimen09:41
Today’s route
The assistant replies only to you.
Push
03 — Approach
The altitude brief
The altitude brief is the working order. It has been the order for years, on both iOS and Android. The page you are reading is the studio’s public chart of that order, not a catalogue of invented launches.
Behavior is written first. We name the actions a person can take, the states a screen can be in, and what must remain true if the network drops. Design follows that brief. The visual system is drawn once, then adjusted so iOS habits and Android habits each feel at home: sheets and navigation on one, the back path and system patterns on the other.
The build keeps a native feel. We do not wrap one foreign interface and ship it twice under two icons. Testing sits on the route rather than after a scramble at the end: on-device checks for both platforms, including the assistant, push, and the screens that have to stay readable. Release hands the build to the stores. Updates stay on the same plan, so a fix on one platform does not quietly become a different product on the other.
A feature that exists on one store and not the other is an unfinished route. When an update ships, it ships against the shared plan, with the same assistant limits and the same unique id.
04 — Process
Five marks on the route
Five steps, in the order the work actually happens. Each mark is done for iOS and for Android before the route moves on.
-
01
Behavior
The actions and states are written before the visual. We list what a person can do, what the app must remember, and which moments have to stay clear offline.
-
02
Design
One visual system, two platform habits. Type, spacing, and navigation are drawn so each deck feels native instead of borrowed.
-
03
Build
Implementation follows the brief. Inputs, back behavior, and motion match the platform. The shared plan is not an excuse for a single foreign shell.
-
04
Testing
On-device passes for both platforms cover the assistant’s limits, the push path, readable type, and the screens that must hold their state without a network.
-
05
Release and updates
The store release is a handoff, not the end. Later fixes stay on the same plan so the two decks do not drift apart.
05 — Questions
From the ground
Is every product made for both iOS and Android?
Yes. Every product is made for both platforms. We do not finish one store and treat the other as optional. Behavior, design, build, testing, release, and updates are carried out for iOS and for Android from the same plan.
Is the in-app assistant a person?
No. The assistant can talk with users inside the app, and it is not a human. There is no staff member typing on the other side of that chat. If you want the studio, use the email on the Contacts page.
Can the assistant give professional advice?
No. It is not professional advice. It is not legal, medical, financial, or any other licensed counsel. It answers inside the product. Do not treat a reply as a specialist’s opinion.
Are messages passed to other users?
No. What someone writes is used only to answer that person. It is not passed to other users, and it is not placed where another person can read it.
Do the apps build a personal profile?
No. The apps build no personal profile. They do not collect a name, email, phone number, contacts, or precise location in order to describe a person. Users do not send personal data to each other.
What is the unique id for?
The only identifying item is a unique id. Attribution uses it with Singular. Push notifications use it with OneSignal. It is not your name, and it is not shared so that other users can find you.
What do Singular and OneSignal do?
Singular is for attribution: which route led to an install. OneSignal is for push notifications to the device. Nothing in either path is a channel between users. The privacy note describes both in full.
How do I reach the studio?
Write from the Contacts page, or use the email address shown there and in the footer. Privacy and Terms are linked beside it. The form opens your own email app and does not post the note to a server.
06 — Build notes
Instruments that stay steady
Six checks that stay on the plan for both platforms. They are working rules, not slogans.
Native feel
Navigation, type, and input follow the platform. An iOS build should feel at home on iOS. An Android build should feel at home on Android. The shared plan does not mean one foreign shell copied twice.
Accessibility
Type stays readable, controls stay large enough to tap, and focus stays visible. Platform accessibility tools are part of testing, not a note added after release.
Performance
Screens open without a stall, and lists stay steady while they move. The build avoids extra work that would spend the battery for no reason a person can see.
Offline
Paths that must work without a network are named in the brief and tested that way. If the connection drops, the app says so and keeps the last stable state.
Updates
A release is not the last mark. Fixes and later versions stay on the same plan for both platforms, so one deck does not drift into another product.
Testing
We test behavior, the assistant’s limits, push, and the store path on both platforms. A screen that only looks right in a desktop preview is not finished.
07 — Assistant
The voice in the cabin
The in-app AI assistant can talk with users. It is there to answer questions about the product while someone is holding the phone. It is not a human, and it is not a channel to the studio’s mailbox. That mailbox is the email on this site.
It is not professional advice. A reply can describe what a screen does. It cannot act as legal, medical, financial, or any other licensed counsel. If a decision needs a qualified person, the assistant is the wrong instrument.
What someone writes is used only to answer that person. The words are not passed to other users. They are not shown on another phone, and they are not used to build a personal profile. The apps build no personal profile, and users do not send personal data to each other.
Attribution uses Singular. Push notifications use OneSignal. The only identifying item is a unique id, shared with those two roles and not offered to other users as a way to find someone.
08 — Privacy
Nothing crosses between cabins
The short chart: your device may speak to Singular for attribution and to OneSignal for push. The only identifying item is a unique id. There is no path that carries personal data from one user to another, and the apps build no personal profile — no name, email, phone, contacts, or precise location gathered to describe a person.
Name, email, phone, contacts, and precise location are not collected to describe who you are.
Users do not send personal data to each other. Assistant text stays with the reply, not with another person.
A unique id is the only identifier. Singular uses it for attribution. OneSignal uses it for push.
Device
Your phone
Holds the app. The only identifying item on the route is a unique id.
Attribution
Singular
Learns which route led to the install. Not a profile, and not a bridge to another user.
Push
OneSignal
Addresses the device for a notification. Not a channel between people.
Stopped
Other users
No line runs from your data to another person. That gap is part of the product.
09 — Contact
Radio the studio
CIRRUS AERO LTD
Write about a product, the assistant’s limits, or the privacy note. The Contacts page has a form that opens your email app with the subject and message prepared on the page. Nothing is stored on a server.