Mobile & .NET Applications
Enterprise-grade mobile and desktop applications — from duty-of-care and traveler tracking platforms to .NET backend systems and cross-platform mobile apps that power critical business operations.
Book a Free ConsultationWhat does enterprise mobile app development include?
Enterprise mobile app development is building the iOS and Android apps and the backend they depend on as one product, with authentication, push notifications, location services and monitoring designed in from the start. Mantiqi builds cross-platform apps (Flutter by default) on .NET backends, tests the Arabic right-to-left layout in every build, and handles App Store and Play Store submission.
Typical timeline: Scope in weeks 1–2, backend and APIs in weeks 3–8, mobile builds in weeks 6–14.
Why this matters
Most agencies will quote you a mobile app and ship a thin wrapper around an off-the-shelf template that breaks at scale. Real enterprise mobile work — duty-of-care for travelers in conflict zones, location-tracked field operations, .NET backends serving millions of requests, App Store / Play Store listings that survive review — needs people who've shipped this before. Mantiqi has built mobile platforms that ran traveler-tracking for global enterprises, .NET services backing high-volume payment flows, and Arabic-RTL apps that work the way Saudi users expect.
What We Deliver
How we deliver
- 01
Product + tech scope
Weeks 1–2We pin down the user stories, decide native vs cross-platform (Flutter / React Native vs Swift + Kotlin), pick the .NET backend architecture (Azure App Service, Functions, AKS), and produce a written scope with milestones tied to demoable builds.
- User stories + acceptance criteria
- Platform recommendation (cross-platform vs native)
- .NET backend architecture diagram
- Milestone-based delivery plan
- 02
Backend + APIs
Weeks 3–8.NET backend ships first so the mobile team has stable APIs to build against. Authentication, push-notification infra, geofencing logic, real-time alerting, and observability are in before the mobile UI starts.
- .NET backend with typed APIs
- Authentication + role-based access
- Push notifications + real-time alerts
- Observability + APM integration
- 03
Mobile builds
Weeks 6–14 (overlapping)Bi-weekly TestFlight + internal Play Store releases. Arabic RTL is tested every release, not at the end. App Store + Play Store submission with all required metadata, privacy policies, and review responses handled by us.
- iOS + Android builds (TestFlight / internal track)
- Arabic RTL + English support
- App Store + Play Store submissions
- Crash reporting + analytics
- 04
Launch + iterate
OngoingProduction launch with crash-rate + adoption monitoring. We handle iOS / Android version-update compatibility (annual platform releases break things — we patch them), App Store review pushback, and feature iterations from real user feedback.
- Production app + monitoring
- Annual iOS / Android compatibility patches
- Feature iteration sprints
- App Store / Play Store ongoing maintenance
Frequently asked questions
Default: cross-platform with Flutter for new builds (one codebase, near-native performance, Material + Cupertino covered). We go native when the app needs heavy platform-specific APIs (CarPlay, watchOS / Wear OS, deep ARKit / ARCore use) or when you have an existing native codebase that's worth extending. We make the call together in week 1.
It's where our deepest enterprise experience is. .NET 8 / 9 on Azure App Service or Container Apps is fast, type-safe, integrates cleanly with Microsoft identity, and your in-house team can hire for it in Saudi Arabia. We also ship Node.js backends when the project's stack already runs there — we're not religious about it.
Yes. We own the full submission flow including App Store Connect / Play Console setup, app review responses (the hard ones — payment policies, location permissions, kids-data handling), screenshots in Arabic + English, and ongoing version-release management. Most clients hand us their developer accounts and we do the rest.
Yes. Arabic RTL is tested every TestFlight build, not at the end of the project. Layout, fonts (we use Tajawal or your brand-specified Arabic typeface), date / number formatting, and right-to-left navigation gestures all work natively. We've built Arabic-first apps for Saudi government and enterprise clients.
We include annual platform-update compatibility in our managed-services tier. When Apple drops a new iOS in September, we test against the betas in July, ship compatibility patches in August, and your app is review-clean on launch day. Same for Android. Without that tier, plan on a 1–2 week patch cycle each major OS release.
Still have questions?
Our team is ready to help. Reach out and we'll get back to you as soon as possible.
Free offer
Free mobile + backend architecture review
Send us your current app (or a description of what you want to build). We'll send back a written architecture review covering platform choice, backend pattern, infra cost estimate, and the top 3 risks we see — with concrete remediation steps.
Get the review