Flutter & React Native Apps in Canada

About Flutter & React Native Apps

Our React Native and Flutter development services take a cross-platform iOS and Android app from first screen to store release. We use Flutter when polish and 60fps animations matter, and React Native when speed-to-market and shared code with the web matter more. From MVP launches to enterprise apps with 100k+ users, we handle the full lifecycle: design, native module integration, App Store and Play Store submission, push notifications, analytics, and ongoing version updates.

What the engagement includes

• Flutter app development (iOS + Android)
• React Native app development (iOS + Android)
• Native module development for platform-specific features
• Push notifications (FCM, APNS, OneSignal, Firebase)
• In-app purchases and subscription billing (RevenueCat, native IAP)
• Real-time features via WebSockets or Firebase
• Offline-first apps with sync (SQLite, WatermelonDB, Realm)
• Maps and location services (Google Maps, Apple Maps, Mapbox)

Background location, Quebec's rules on children's advertising and tips, and accessibility feedback in a Canadian app

The Canadian case every location feature is measured against is the joint investigation into the Tim Hortons app by the federal Privacy Commissioner and its counterparts in Quebec, British Columbia and Alberta, published on 1 June 2022. The app collected granular location through a third-party SDK, as often as every few minutes and when the app was not open, while its Android permission prompt asked for location while the user was using the app; one user found more than 2,700 location records in under five months. The commissioners found the purpose disproportionate, since the data was never used to tailor marketing to anyone, and the consent invalid, and the remedies included deleting the data, requiring the SDK provider to delete it too, and a privacy management program with privacy impact assessments for future apps. They also faulted a clause in the vendor contract loose enough to allow the provider other uses of the data. In a Flutter or React Native app the same exposure sits in places a code review of the shared layer never sees. Location reaches the app through a plugin or a vendor SDK whose native side runs outside the Dart or JavaScript, and on Android a foreground service holding location permission keeps collecting with the screen off. So we inventory every native module that can request location or run in the background, keep the wording of each permission prompt true to what the code actually does, and treat background location as a separate feature with its own request and its own justification rather than something a library switches on. iOS helps where you let it: for an app with Always authorization, the blue status bar indicator appears in the background only if the app turns it on, and we turn it on. The data processing terms of every SDK that touches location go into the contract review rather than being accepted at sign-up. Whether your purpose for collecting location is proportionate is for your own counsel.

Quebec's Consumer Protection Act reaches into in-app monetization in two places that templates rarely handle. Section 248 forbids commercial advertising directed at persons under thirteen, and section 249 decides whether a message is directed at them from its context, in particular the nature and intended purpose of what is advertised, the manner of presenting the message, and the time and place it appears. The Office de la protection du consommateur's guide says every medium is covered, mobile phones among them, that a section of a website counts as a place, and that themes of fantasy, magic, adventure or virtual worlds and characters such as animated creatures are among the techniques that point to children. For a game or a family app that puts the upsell interstitial, the rewarded video and a shop screen with a mascot squarely in question, and the prohibition reaches whoever prepares, publishes or broadcasts the message as well as the merchant, so an ad network SDK serving into a children's section is part of the analysis. In the build, every ad and promotion surface knows whether the section it sits in is meant for children and can switch off there for Quebec users. The second rule is tipping. Since 7 May 2025 a merchant that suggests tip amounts has to calculate percentages on the price before GST and QST, offer only the suggested amounts plus a way for the customer to set their own, and present them in a uniform way that does not steer the choice. The Office gives payment terminals as its example, and delivery, booking and ride apps that copied a tip screen from an American template usually break all three requirements: the percentage is taken on the taxed total, the middle option is highlighted, and the custom amount hides behind an extra tap. So the tip component takes the pre-tax subtotal as an explicit input and gives every option equal weight. How either rule applies to your app is for your own counsel.

For a bank, telecommunications company, airline or other federally regulated organization, the Accessible Canada Act brings a duty that can land in the app itself. The Accessible Canada Regulations require a regulated entity with ten or more employees to run a feedback process that accepts feedback by mail, telephone, email and any other means the entity uses to communicate with the public, allows feedback to be given anonymously, and acknowledges receipt by the same means it arrived, unless it was anonymous. If the app is one of those means, the feedback route belongs inside it, reachable with a screen reader, with the acknowledgment coming back in the app rather than by an email the person never asked for. The technical standard to build against is CAN/ASC-EN 301 549:2024, which Accessibility Standards Canada published in May 2024 and which covers software and mobile apps as well as the web. Federal accessibility regulations made in 2025 (SOR/2025-255) now adopt it for covered organisations, with obligations phasing in from December 2027, so whether and when it binds you is a question for counsel, but it is the yardstick a federal buyer will hold up. This is where the two cross-platform frameworks differ most. React Native renders native views, so its accessibility labels and roles map onto controls that VoiceOver and TalkBack already understand. Flutter draws its own pixels and hands screen readers a semantics tree instead, and its documentation is plain that custom widgets and anything drawn with CustomPaint need explicit Semantics to be read at all, so a custom chart, signature pad or seat map in a Flutter app is silent until someone writes those annotations. Both have to stay usable at very large text scale factors, and French strings, which already run longer than their English equivalents, make the bilingual screens the first ones to test at maximum size. Whether your organization is regulated under the Act is for your own counsel.

How we work with Canadian clients

Two things shape Canadian projects more than anything technical. The first is language: if you serve Quebec, French is a legal requirement rather than a nice addition, and the rules tightened considerably under Bill 96. The French version has to be available on equal terms with the English one, which is a design constraint from the first wireframe rather than a translation task at the end.

The second is anti-spam law. CASL is stricter than most teams expect, and the penalties are real. Consent has to be express or clearly implied, records of it have to be kept, and every commercial message needs a working unsubscribe and accurate sender identification. We build those into the product rather than leaving them to whoever configures the mailing tool later, because that is where the exposure usually sits.

Indicative pricing in CAD

Converted from our published Indian rates and rounded. Exchange rates move, so the figure on your quote is calculated on the day it is issued.

Questions Canadian clients ask

Flutter & React Native Apps: common questions

Other markets we work in