# Apps your customers keep on their phone.

Source: https://cruxlabs.com.au/services/mobile-apps

A mobile app earns its place when customers open it every week to order, pay, book or collect loyalty. We build native iOS and Android apps, or an installable web app when that is enough, wired to your till and sharing one back end with your system. Built in Melbourne, working Australia-wide.

## The problem: The app exists. It just does not work for you.

- **Loyalty runs in someone else's app.** Your regulars collect points in an app that belongs to someone else, and so does the relationship.
- **The till and the app do not talk.** Orders placed on a phone are keyed into the till by hand, and loyalty lives in a third place.
- **A website in a wrapper.** It installs like an app and behaves like a slow web page, so nobody opens it twice.

## What we build: One app, wired to your till and your system.

We pick native or installable by how often your customers will open it, then connect it to everything behind the counter.

- **Native or installable.** Native iOS and Android for an app used every week; an installable web app when that is enough.
- **Orders and payments to the till.** Apple Pay and card orders land straight on your point of sale, Square today.
- **Wallet passes and push.** Loyalty cards in Apple and Google Wallet, and notifications people asked for.
- **One back end.** The app shares its records with your system, so a customer is one record everywhere.

Set up for: [Food and franchise](https://cruxlabs.com.au/industries/food-beverage-franchise), [Transport and chauffeur](https://cruxlabs.com.au/industries/transport-chauffeur), [All industries](https://cruxlabs.com.au/industries).

## What we have built: Apps on real phones, wired to real tills.

- **Loyalty and ordering for cafés and restaurants** (Hospitality, iOS and Square, Live). A native iOS app with Apple Pay orders straight to the Square till, loyalty, push and wallet passes. The back end took live orders four days after the first line of code. [Read the case](https://cruxlabs.com.au/case-studies/cafe-loyalty-and-ordering)
- **An installable web app for a chauffeur business** (Transport, Melbourne, Live). It sits on the same system that runs the bookings, Stripe invoicing and SMS reminders, so the phone and the office see one record. Close to $300K: revenue in under 10 months, with the system, the ads and our advice. [Read the case](https://cruxlabs.com.au/case-studies/chauffeur-business-system)

## Questions

**Native or cross-platform?**
Whichever the job needs. Native when customers open the app every week and it needs the wallet, payments or push. An installable web app when they use it now and then: one build for every phone, with no app store in the way.

**How much does an app cost in Australia?**
Every build gets a fixed price before work starts, sized to your business. You can start with one fix, such as quoting or bookings, or build the whole system. The Blueprint, a short paid mapping stage, ends with that fixed quote, and its fee comes off the build.

**Can the app talk to our till or our system?**
Yes. Our café app sends orders and Apple Pay payments straight to the Square till, and every app we build shares one back end with your system.

**Who owns the App Store account?**
You do. The app is published under your own Apple and Google developer accounts, and the code is yours.

## What would your customers open every week?

[Book a call](https://cruxlabs.com.au/contact) · [Build or buy? Take the checker](https://cruxlabs.com.au/tools/build-vs-buy)
