Mobile app development company in New Brunswick

For an app built around accounts, forms, bookings, payments or content, a cross-platform build is often a practical choice. We usually use React Native, sharing a codebase across iOS and Android and adding native modules when a feature needs them. That gives you both platforms without maintaining a separate full app for each.

A native build suits an app that depends on deep device features, heavy graphics, complex background work or new platform features at launch. The trade-off is more code to build and maintain: Swift for iPhone and Kotlin for Android. Choose this route when those device capabilities are central to what people will do in the app.

A progressive web app is another option for a staff tool. It skips store review, although it will not appear in the app stores unless packaged for them. On iPhone, it can ask to send notifications only after someone adds it to the Home Screen. Decide how staff will open the tool and whether store distribution and notifications are part of the job.

For private-sector commercial activity, PIPEDA sets federal rules for collecting, using and disclosing personal information. That affects the account and data flows you ask us to build. We set up the relevant account and data screens around the information your app collects and the choices it gives users.

Payment setup depends on what you sell. Apple requires in-app purchase for digital content, features and subscriptions used in the app; physical goods and services used outside it need another payment method. Stripe lists Canada as a country where businesses can sign up to accept payments. We set up the purchase or subscription flow for the product being sold.

Bring the intended user task and any account details you already have.

• Write a short list of first-release tasks in the order people will do them.
• Start registering Apple and Google developer accounts in your company’s name; organisation accounts need a D-U-N-S number.
• For a new personal Google Play account, plan a closed test with at least 12 testers opted in for at least 14 days.
• Have a privacy policy that matches the data the app collects; Apple requires links in the listing and app.
• If the app has a login, prepare a working demo account and live backend for Apple’s review, with room for fixes and resubmission.

• !

  Wrapping a website in an app shell

  Apple expects more than a repackaged site. Define what people will use the installed app to do before choosing that approach.

• !

  Putting sign-up first

  People can leave before seeing value. For an app without significant account-based features, let them use it without logging in.

• !

  Adding an analytics or advertising SDK without updating privacy answers: Check the data collected by third-party SDKs against Google Play’s Data safety form whenever the app changes.