App developers in Canberra

A cross-platform app is a good fit when the main work involves accounts, forms, bookings, payments or content. We usually use React Native, sharing a codebase across iOS and Android while adding native modules where a feature needs them. That gives you a shared foundation to build and maintain, while the app still uses each platform’s interface components.

A native app is worth considering when the product depends on deep device features, heavy graphics, complex background work or new platform features at launch. The trade-off is a separate codebase for each platform, with each one needing its own development and maintenance. That gives you a different level of access to the device, alongside more work to manage.

Start with what people need to do on their phones and which device features those tasks require. You talk directly to the people designing and building your product, so we can discuss the trade-offs with you before deciding how to build it.

Australian guidance recommends WCAG 2.2 Level AA for digital goods and services. We design and review your app screens against that level, so accessibility is considered in the screen work instead of being left until the store submission.

For card checkout, the Australian rule removes surcharging on debit, prepaid and credit card payments on the eftpos, Mastercard and Visa networks. We set up the relevant checkout settings without those surcharges; the payment flow needs to reflect that rule in the app.

Bring the details that will help us define the first release.

• User tasksList what people must do, in the order they will do it.
• Connected systemsNote your website, booking system, payment provider or other software, its API and who holds admin access.
• Developer accountsStart registering the accounts in your company’s name and check the D-U-N-S requirement for organisation accounts.
• Privacy policyPrepare a policy that matches the data the app collects; it needs links in the listing and the app.
• Account deletionIf users can create accounts, plan an in-app deletion path and a web request link for Google Play.

• !

  Wrapping a website in an app shell

  Give people useful app features. Apple’s guidelines ask for more than a repackaged site, and a shell risks rejection.

• !

  Making everyone sign up immediately

  Let people see useful content first where the app does not need significant account-based features.

• !

  Requesting notification permission on first launch

  Ask when the benefit is clear, such as after an order. On Android 13 and later, notifications stay off until the user allows them.