iOS and Android app development for Australian businesses
Cena Advisory designs and builds mobile apps for iOS and Android. Staff tools, customer apps, and products that need to work well on a phone. New apps are welcome, not only extras on software you already run. We work across Australia. We take meetings and calls.
Product
What we build
Mobile app development in Australia, for us, means iOS and Android that people will actually use. Staff apps for the day list, notes, photos, and a clear done button. Customer apps when the product needs to live on a phone. Apps that are the product itself.
We will use one codebase for iOS and Android when that is the honest choice, usually Ionic and Capacitor, and native when it is not. Buyers comparing stacks often ask about Flutter or React Native; when one codebase is honest for us, the shared path is usually Ionic and Capacitor, and we will say so before we quote rather than default to a framework we do not ship as our day-to-day stack. One codebase is often right for a staff app with a handful of screens. Native is the better path when the product needs heavy camera work, tight platform APIs, or a store listing that will not forgive a shared shell. We will say which we would take before we quote. Push, camera, and offline-tolerant field work sits under Offline and field apps.
Buyers often call a shared iOS and Android codebase a hybrid or cross-platform app. That is the same choice as one codebase above: usually Ionic and Capacitor when a shared shell is honest, and native when the product needs heavy camera work, tight platform APIs, or a store listing that will not forgive a shared shell. We will say which path we would take before we quote. The Buyer question Do you build iOS and Android from one codebase… restates it in plain language. Tell us about the project.
A new app is a normal job. An app that sits with software you already run is also a normal job. The web side of that work is custom software development.
See our case studies for real examples of mobile and web work built together. A published healthcare booking example sits under Appointment booking apps.
- Staff apps: the day list, notes, photos, and a clear done button
- Customer apps when the product needs to live on a phone
- iOS and Android from one codebase when that is the honest choice (Ionic / Capacitor), native when it is not
- Offline and field apps: jobs, photos, and notes when coverage drops
- Progressive web apps when a browser surface is enough
- A new app, or a mobile layer on software you already run
A conversation
Start with a call.
We take calls and meetings with Australian business owners who have a real iOS or Android app to build. Melbourne based, we work across the country.
Audience
Staff app or customer-facing app
A staff app is for people you already know: your team, your contractors, a clinic floor, a warehouse. Sign-in, a few jobs they do every day, talking to a system you already have. A customer-facing app is for the public: app stores, accounts, support, and the extra surface that comes with that. Cost is usually lower on the staff side because the audience and the feature set are smaller. The right first version is the one that matches who will actually open it. See What is the difference between a staff app and a customer-facing app? on the FAQ.
Workflow
Appointment booking apps
When booking is a real workflow problem, not a feature checkbox, we build the flow that matches your rooms, staff, and rules. One published example is a healthcare booking app for a regional practice: patients book online and the front desk sees the day at a glance, so double-booking stops being a daily fight with the phone.
The same shape shows up in other service businesses that still run the day from a diary or inbox. We do not sell a one-size booking product. We sit on top of a calendar you already pay for when that is the honest path. See the healthcare booking case study.
Staff tools versus a public app, and sitting with software you already run, are covered on the FAQ. Tell us about the project if the day still lives on the phone.
Fit
When a phone is the right surface
People work away from a desk. They need an app that fits a few minutes between jobs, not a desktop website squeezed onto a phone. We also build apps that are the product itself.
If the honest answer is a well-made web app in a browser, we will say so. That work lives on custom software development.
See how we work, or tell us about the project.
Field
Offline and field apps
When the phone is the work surface away from a desk, the app has to keep going when coverage drops. Cena Advisory builds staff apps that capture jobs, photos, and notes on the device, then sync when the network returns. Push notifications, camera capture, and offline-tolerant flows are normal parts of that job, not extras bolted on later.
Sometimes the honest path is a staff tool that talks to software you already run in the office. Sometimes it is a first version that proves the field loop before a wider build. We will say which path fits after a conversation. The steps are on How we work.
Staff tools versus a public app, and one codebase versus native when the hardware needs it, are covered on this page and the FAQ. Sitting with tools you already run is there too. Tell us about the project if paper and patchy signal still run the day.
Browser
Progressive web apps (when the browser is enough)
A progressive web app (PWA) is a web app that can feel installable and offline-tolerant in the browser, without an App Store or Play listing. Choose a PWA when a browser surface is the honest product: staff tools, portals next to software you already run, or a first version that should not wait on store review.
Choose iOS and Android (one codebase or native) when the job needs camera depth, tight platform APIs, or a public store listing. Cena Advisory builds both shapes and will say which fits after a conversation.
One codebase and store rules are covered on this page. Offline field capture sits under Offline and field apps.
Starting
How a project starts
Tell us about the project. You do not need a long brief. Who will use the app, what they need to do in a few minutes, and any systems it should talk to is enough. We will get on a call.
Some work is clear enough to quote a build from that conversation. When it is not, a two-week discovery gives you a spec and a fixed-price quote. The steps are on How we work.
First slice
A first version (MVP)
An MVP, or minimum viable product, for a mobile app here is a first version that real users can run on a phone, not a slide deck or a clickable prototype alone. A prototype or proof of concept (POC) can prove a flow looks right; an MVP proves people can finish the job with real data and the integrations that matter, with a clear list of what is out of scope. For a staff app that is often a handful of screens. For a customer-facing app it is usually larger because accounts, stores, and support land earlier. Cena Advisory gets there through a conversation, or through a two-week discovery when the scope is still fuzzy. The longer answer is on the FAQ. The steps are on How we work.
A pilot is the same idea on a phone: a limited first run with real users, one team or one site, and a written out-of-scope list, not a clickable prototype alone. What comes after the MVP is usually the next slice of the same app. The longer framing is on How we work and the FAQ. Tell us about the project when you want that conversation on a real job.
Distribution
App stores and the rules that come with them
A customer-facing app means the Apple App Store Review Guidelines and Google Play policies. We build to them from the first screen so a launch is not held up by a rejection. Staff apps that stay inside your organisation are a different surface, and usually a calmer one. The web side of the same work is custom software development.
Experience
Twenty-plus years of mobile
Our team has spent 20+ years shipping software and mobile apps, including ones that have to work on a mid-range Android in the afternoon.
Cena Advisory is an experienced Australian software and mobile team based in Melbourne. We work with businesses across Australia. We take meetings and calls. The people you speak to are the people who design and build the work. Who you will meet is on the About page.
The team
You talk to the people who build.
You talk to the people who quote the work and write it. If you want to start, use the Contact page.
Melbourne
Custom mobile app development in Melbourne
A custom mobile app development company designs and builds iOS and Android apps for a specific business, not a one-size store template. Cena Advisory is that offer from Melbourne: staff tools, customer apps, and products that need to live on a phone.
Custom mobile app development in Melbourne, for us, means a Melbourne software and mobile studio that meets in person when that helps and works Australia-wide on calls. The people you speak to are the people who design and ship the work. Searching "custom mobile app development companies", "mobile app development company Melbourne", or "app development companies in Melbourne" usually returns directories and cost guides; this page is the build offer itself.
See About for where we work, and who we are as a partner. The short studio answer is Who builds the app, and where are you based?. Then Contact when you have a real app to ship.
Questions
Buyer questions
Do you build iOS and Android apps in Australia?
Yes. Cena Advisory designs and builds iOS and Android apps for Australian businesses. Staff tools, customer apps, and products that need to work well on a phone. Tell us about the project and we will get on a call.
Do you build iOS and Android from one codebase, or do you write two native apps?
We use one codebase for iOS and Android when that is the honest choice, usually Ionic and Capacitor. We do not default to Flutter or React Native. We write native when the product needs it: heavy camera work, tight platform APIs, or a store listing that will not forgive a shared shell. A staff app with a handful of screens is often a good fit for one codebase. A consumer product with deep iOS or Android behaviour may not be. We will say which path we would take before we quote.
What is hybrid app development?
Hybrid (or cross-platform) app development usually means one shared codebase for iOS and Android, rather than two fully native apps. At Cena Advisory that is the same one-codebase path above, usually Ionic and Capacitor when it is honest. Native is the better path when the product needs deep platform behaviour. Read What we build above, or Do you build iOS and Android from one codebase…, for how we pick. Tell us about the project.
Can a mobile app sit with software we already use?
Yes. A greenfield app is a normal job. An app that talks to a diary, CRM, portal, or other tool you already run is also a normal job. That join is API and system integrations. Custom software development often sits next to the app.
Do you build appointment booking apps?
Yes, when booking is a real workflow, not a checkbox. A published example is the healthcare booking app for a regional practice. We do not sell a generic booking product. We build the flow that matches your rooms, staff, and rules, and we sit on top of a calendar you already pay for when that is the honest path. Read Appointment booking apps above, or the case study.
Do you build offline or field apps?
Yes. Staff apps that capture jobs, photos, and notes when coverage is weak, then sync when the network returns, are a normal Cena Advisory job. Push and camera are part of that shape when the work needs them. We sit with software you already run in the office when that is the honest path. Read Offline and field apps above.
Do you build progressive web apps (PWAs)?
Yes, when a browser app is the honest product. A PWA can be installable and offline-tolerant without a store listing. When the work needs deep device APIs or a public App Store or Play release, we build iOS and Android instead. Read Progressive web apps above.
How does a mobile app project start?
Use the contact form or email felix@cenaadvisory.com. We will get on a call. Some work is quoted from that conversation. Some work starts with a two-week discovery, described on How we work.
Who builds the app, and where are you based?
Cena Advisory is an experienced Australian software and mobile team based in Melbourne. The team has 20+ years of development experience. We work with clients across Australia. We take meetings and calls. The people you speak to are the people who build the work. See About.
Are you a custom mobile app development company in Australia?
Yes. Cena Advisory is an experienced Melbourne software and mobile studio that builds custom iOS and Android apps for Australian businesses. One codebase when that is honest, usually Ionic and Capacitor, and native when the product needs it. Read Custom mobile app development in Melbourne above, and Who builds the app, and where are you based? for the short studio answer. See Looking for developers to hire? on About, then Contact.
Do we own the app code?
Yes. Clients own the source code Cena Advisory writes for a paid mobile app engagement, including the repository. Process: You own the code. FAQ: Who owns the source code?.
Start here
Tell us about the mobile app.
If you have a real app in mind, we will get on a call. Some work is quoted from that conversation. Some starts with a two-week discovery.