B2C customer journeys
Loyalty, cart, order-status notifications.
What is a mobile application? Native, hybrid, and PWA
A mobile application is software built to run on a smartphone or tablet, using device sensors, notifications, and offline capabilities. It may be native (Swift/Kotlin), cross-platform (Flutter, React Native), or an installable PWA. For organizations, the choice hinges on offline needs, hardware access, and the cost of maintaining both iOS and Android.
In one sentence
A mobile app lives on the phone and uses its sensors, notifications, and offline mode.
Key points
- Native maximizes performance and system APIs; cross-platform shares one codebase for iOS and Android.
- App stores require review, privacy policies, and ongoing updates.
- A PWA can be enough when deep hardware access is not required.
- True cost includes maintenance, certifications, and privacy compliance.
Term at a glance
- Mobile application
- Mobile app · Native app · Smartphone app
- English term
- Mobile application
- Domain
- Software development
- Category
- Applications
- Level
- Beginner to intermediate
What does “mobile application” mean exactly?
Unlike a responsive site opened in a browser, a mobile app is installed (or added to the home screen), can work with limited connectivity, and can receive push notifications. iOS and Android expose distinct SDKs for camera, GPS, biometrics, and secure storage.
Cross-platform frameworks reduce duplicated business logic. Trade-offs include access to the newest APIs and binary size. For a Montreal SME, the question is less “app or not” than “which channel truly carries the customer journey.”
An app is not a shrunk website: you design short flows, offline states, and strict permission handling—especially under Quebec privacy rules and store policies on location and tracking.
How do you deliver a mobile app project?
- 01
Frame usage and constraints
Map offline scenarios, required sensors, user roles, and compliance needs before picking a stack.
- 02
Choose native, cross-platform, or PWA
Balance timeline, maintenance budget, and dependency on system APIs (Bluetooth, NFC, background work).
- 03
Design API and security
Authentication (OAuth, biometrics), encryption at rest, token handling, and data retention policy.
- 04
Ship via stores and iterate
CI/CD, TestFlight/Play Internal testing, crash telemetry, and short release cycles.
A concrete mobile app example
A field-services firm in Laval equips technicians with an Android/iOS app: photos, customer signatures, and work-order sync when connectivity returns. Data flows through a secured REST API; drafts stay local offline. The measurable win is fewer paper handoffs and end-of-day entry errors.
What are mobile apps used for?
Field tools
Inventory, inspections, geolocated interventions.
Employee portals
HR, time tracking, secure access to internal docs.
SaaS companion
Mobile view of a dashboard already served on the web.
Benefits and limits of mobile applications
- Access to sensors and native notifications
- Often smoother than a browser tab
- Controlled offline work is possible
- Store presence as a distribution channel
- Cost of dual platforms or a framework to maintain
- Store review delays
- Updates depend on user adoption
- Larger attack surface and stricter privacy duties
How does a mobile app differ from a web app?
| Mobile application | Web application | |
|---|---|---|
| Install | Store or sideload; device icon | URL in the browser; no required install |
| Hardware access | Broad (camera, Bluetooth, system push) | Limited to browser web APIs |
| Distribution | Bound by App Store / Play rules | Immediate server-side deploy |
| Maintenance | iOS + Android builds plus backends | One web front-end to maintain |
Why mobile apps matter for Quebec SMEs
In Quebec, a growing share of customer and employee interactions happen on phones. An app pays off when it removes operational friction (field work, critical alerts) or anchors a product. Otherwise a strong mobile site or PWA can deliver most of the value without store overhead.
Frequently asked questions
Do we always need a native app?
No. Without advanced push, Bluetooth, or robust offline needs, a PWA or mobile site may be enough.
Flutter or React Native?
Both cover iOS/Android. Choose based on team skills, required native libraries, and UI roadmap.
What does yearly maintenance cost?
Budget for major OS releases, security patches, dependency updates, and store resubmissions—often a meaningful fraction of build cost.
How do we handle privacy (Law 25)?
Minimize collected data, document purposes, encrypt sensitive local storage, and obtain clear consent for tracking and location.
Related terms
Sources and references
Torn between native, cross-platform, and PWA? We frame the right channel for your journeys and maintenance budget.
Scope your mobile project