Apps
One codebase, both app stores. iOS and Android apps built together so features ship at the same time and cost less to maintain.
Superstack builds iPhone and Android apps from a single codebase, so both versions ship together. It is cross-platform app development NZ gyms, hospitality groups and start-ups choose when their customers are split across both stores and the budget is not. We also say plainly when native is the better call.
paying twice for one app
cross-platform app development from one codebase
One codebase, iOS and Android, is the whole idea: write the app once, ship to both stores, fix a bug in one place. The modules below make it work.
01 of 8
React Native app development runs on the same language as most websites, so one team owns both. Flutter app development draws every pixel itself, so brand-heavy designs stay consistent. We pick one per project and explain why in plain terms before design starts.
02 of 8
Buttons, forms, colours and spacing live in one shared library, so each screen looks the same on iPhone and Android. When your brand changes its green, one edit updates every screen. A member sees the same booking flow on either phone.
03 of 8
Expo app development includes over-the-air updates: a fix to a screen, a price or text goes out without a store review. A checkout typo is gone by lunchtime. Changes to native code still go through the stores, and we say which is which.
04 of 8
When the shared code needs something only the phone can do, we write a small native piece and bridge to it. The camera scans a membership QR code, Bluetooth talks to a gym turnstile, and Face ID or fingerprint unlocks the app.
05 of 8
Both apps talk to one backend and one database, so a booking made on Android appears on the iPhone and the front desk screen. Your website and portal use the same API. Add a feature once and every platform gets it.
06 of 8
One build produces both store packages, and we submit them together. Apple and Google review on their own schedules, so we hold the release until both approve, then switch it on the same day. Nobody asks why the other phone got it first.
07 of 8
Every change runs through automated tests on real and simulated devices: an old iPhone, an Android tablet, a budget phone. A booking flow that breaks on one screen size fails the test, and the fix ships before a customer finds it.
08 of 8
The same code also builds a web version, so customers without the app book and pay from a link. For a cafe group, that is the online ordering page, sharing menu screens with the app. We say when it is worth doing.
Scoping decides whether cross-platform fits, and we say so if not. Then we choose React Native or Flutter and explain why. Design happens once, for both platforms. The shared build goes through the device lab automatically on every change, and your team tests it. Both stores go live on the same day. From then on, most fixes reach customers over the air.
Your accounting software receives invoices and returns payment status. Stripe takes card payments in both apps. Google and Apple sign-in mean no new password. Twilio sends SMS confirmations. Firebase handles push notifications. Your CRM and job system connect via API, once, for both platforms.
Any system with an API connects. Click a logo to visit them.
Xero
MYOB
Stripe
Google Workspace
Microsoft 365
Twilio
Shopify
HubSpotAI is optional, and earns its place only by saving a real person real time. What changes here is the cost, because one implementation serves both platforms. See how we use AI and where it fits in business process automation.
Smart search across your menu or class list, drafted replies to customer messages and document capture that reads a licence from a photo, built once and shipped to both stores together.
The office and the front desk run the web app: managing classes, menus, bookings and customers, and pushing an over-the-air update when something changes. It runs in any browser with nothing to install.
Customers and staff get one app in both stores, identical on iPhone and Android, with the camera, Bluetooth and Face ID working natively. Same features, same day, on either platform.
The optional web build doubles as the portal: booking and payment in a browser for anyone without the app. All three share one database, so a class booked anywhere takes the same spot.
Class bookings, memberships and check-in on any member's phone.
HospitalityTable bookings, ordering and loyalty in both stores.
RetailLoyalty, click and collect and stock lookups, released together.
BookingsAppointments, reminders and payments for any business booked online.
Staff apps for multi-platform teamsOne roster app for a team split across both.
SaaS start-upsA product in both stores from launch without funding two builds.
Quickest start
We customise an existing Superstack cross-platform module, such as bookings or loyalty, with your brand and rules.
Most common
We combine modules, such as bookings, payments, loyalty and a staff view, into one shared codebase with a web admin.
Fully bespoke
A fully bespoke product, usually a start-up or a customer app with its own look, on a shared codebase made to last.
React Native if your website is built in React or you have web developers in-house, because the skills carry over. Flutter if the design is unusual and must look identical on every phone, because it draws its own interface. Both are mature and reach both stores, and we recommend one per project.
No, not for the apps most businesses need. Bookings, ordering, loyalty and forms feel identical, since the backend does the heavy lifting. The hybrid app development NZ businesses remember wrapped a website in a shell, hence the sluggish reputation. React Native and Flutter draw native screens. Video editing or games: native.
Yes, for most changes. Anything in the shared code, such as a price, wording or a bug fix, goes out over the air, and customers have it when they next open the app. Apple and Google allow this as long as the app's purpose stays the same. A new Bluetooth feature still goes through both stores.
It struggles where the app is the hardware: heavy video, complex Bluetooth accessories, games, or the newest iPhone feature on launch day. Watch apps and widgets need native code. For a booking, ordering, loyalty or staff app, none of that matters, and we say at scoping if your list crosses the line.
Most of a second build, and part of every update after it. Design, backend and store listings cost the same either way, so the saving sits in app code written once instead of twice, and in maintenance, where one fix covers both platforms. Native bridging costs extra, and the proposal shows both figures.
Yes. React Native with Expo and Flutter both produce a web build from the same code, so the booking or ordering screens work from a link for customers who never install the app. If a full web app is the goal, our progressive web app page is the place to start.
Built around the way you work.
Your business shouldn’t have to fit someone else’s software. Tell us how your business works. We’ll show you what Superstack can build around it.
Not sure if cross-platform fits: send us your feature list and we'll tell you straight.
We use cookies to see which pages help people. Nothing runs until you say yes. Read the privacy policy.