Consumer and marketplace apps
Onboarding, payments and notifications built for retention.
App Development
App development services
You need an app on the devices your users carry, and the native, hybrid or web decision has to be right the first time. Agnotic Technologies designs, builds and releases iOS, Android, web and IoT companion apps as a service, backend included.
iOS and AndroidReact Native and FlutterWeb apps and PWAsIoT companion apps
Trusted by global innovators
App development
What is app development?
App development is the design, build and release of applications that users install or open on a device: iOS and Android apps, web apps that run in the browser, hybrid apps built with React Native or Flutter, and companion apps for connected devices. Agnotic Technologies builds them as a service, from a fixed-scope first release to store launch.
Most apps are two products: the app the user sees and the backend that holds accounts, data and integrations. Both are in scope on every engagement, together with the store listing, privacy disclosures and release process.
The decision that matters most comes first: native, cross-platform or web. The table below is how we make it with you.
Decision table
Native, cross-platform or web: which should you choose?
The honest answer depends on the hardware access you need, the budget for two codebases and how the app will be distributed.
| Approach | Choose it when | Trade-offs | Typical stack |
|---|---|---|---|
| Native (separate iOS and Android apps) | You need deep hardware access, Bluetooth devices, background processing or platform-specific UI, and the app is core to the business | Two codebases to build and maintain; the highest cost but the fewest platform limits | Swift and SwiftUI; Kotlin and Jetpack Compose |
| Cross-platform (React Native, Flutter) | You need both stores from one team and one codebase, and the hardware needs are standard | Native modules are still needed for some device features; framework upgrades become a maintenance item | React Native with TypeScript; Flutter with Dart |
| Web app or progressive web app | Users work on desktop as well as mobile, you need instant updates without store review, or distribution is through a link | Limited access to device hardware and notifications on iOS; no store presence | Next.js or React with a REST or GraphQL backend |
| IoT or device companion app | The app exists to pair with, configure or read a connected device | Pairing, firmware updates and offline sync drive the design; usually native for Bluetooth reliability | Native with Bluetooth Low Energy, or cross-platform with native modules |
Many products start as a web app plus one native app and add the second platform when usage justifies it.
Services
Which app development service do you need?
Each card opens the detailed service page for that platform or integration.
Mobile app development
The full mobile scope: native or cross-platform apps with their backend.
iOS app development
Swift apps built for iPhone and iPad and released through the App Store.
Android app development
Kotlin apps for the Android device range, released through Google Play.
Web app development
Browser-based apps and progressive web apps for desktop and mobile.
Bluetooth medical device integration
Companion apps that pair with Bluetooth Low Energy health devices and sync their data.
What does an app build include?
Every app engagement covers the app, its backend and the release.
Authentication and accounts
Sign-in with email, social or enterprise identity, with sessions and roles handled on the backend.
Backend API and data
The API, database and background jobs the app depends on, designed for offline use where needed.
Integrations
Payments, maps, messaging, CRMs, EHRs or your own systems, tested against real sandboxes early.
Device and sensor features
Camera, location, Bluetooth Low Energy and health data, with the permission prompts users expect.
Notifications and analytics
Push notifications and product analytics that respect the platform privacy rules.
Store release
Privacy policy, Data safety and App Privacy disclosures, screenshots, review notes and the release pipeline.
How we work
How do we take an app from idea to the stores?
Four steps, with the platform decision made before any code is written.
1.
Scoping call and platform decision
We agree who the users are, which devices they use and whether native, cross-platform or web fits, using the table above.
Decide2.
Prototype the key screens
Clickable prototypes of the busiest flows are tested with real users before production code.
Test3.
Build the first release
App and backend are built together with weekly demos on real devices, and integrations are wired in the first sprints.
Build4.
Release and iterate
We prepare the store listings and disclosures, handle review, and then ship updates in agreed phases.
ReleaseStore and platform rules
What do the app stores require before release?
Store review is a scope item, not an afterthought. These requirements are built into the first release.
- A privacy policy linked from the App Store Connect listing and inside the app, as Apple's App Review Guidelines require
- Google Play's Data safety form, completed to match what the app actually collects and shares
- Permission prompts that explain why the app needs the camera, location, Bluetooth or health data, requested at the moment of use
- Account deletion available inside the app wherever accounts can be created
- Accessibility checked against WCAG 2.2 and the platform accessibility tools
- Test builds distributed through TestFlight and Google Play internal testing before public release
What we build
Apps we build
Six kinds of app we are asked for most often.
Patient and health apps
HIPAA-ready apps with device pairing and EHR integration.
Field and operations apps
Offline-first apps for inspections, deliveries and site work.
Enterprise and internal apps
Apps behind single sign-on that connect to your internal systems.
IoT companion apps
Pairing, configuration and data sync for connected devices.
AI-assisted apps
Apps with assistants, summaries or image features and human review.
Scope and cost
What drives app development cost?
We do not publish prices. These drivers decide the scope; the scoping call turns them into a fixed first release.
Platforms
Two native apps cost more than one; cross-platform narrows the gap when hardware needs are standard.
Backend scope
A new backend with accounts, data and integrations is often half of the work.
Device features
Bluetooth pairing, offline sync and background processing each add design and testing time.
Integrations
Each external system adds mapping, testing and error handling.
Data sensitivity
Health, financial or children's data adds disclosure, consent and security work.
Store presence
Listings, disclosures, review and release pipelines for each store.
Facts and sources
Facts and sources behind app releases
Platform rules and standards that every app we release is checked against, each linked to its primary source.
Apple's App Review Guidelines require every app to include a link to its privacy policy in the App Store Connect metadata field and within the app in an easily accessible manner (Guideline 5.1.1).
Source: Apple, App Review GuidelinesGoogle Play's Data safety section is where a developer shows users whether and how the app collects, shares and protects user data, before the user installs it.
Source: Google Play Console Help, Data safety sectionWCAG 2.2 is the W3C Recommendation commonly used as the technical benchmark for accessible web and mobile interfaces.
Source: W3CThe Bluetooth SIG publishes adopted GATT service specifications for health devices, including the Blood Pressure, Glucose, Health Thermometer, Pulse Oximeter and Weight Scale services.
Source: Bluetooth SIG specifications
Platform rules
Platform rules and standards
What we build against, by platform.
App Review GuidelinesPlay policiesWCAG 2.2OAuth 2.0 / OIDCBluetooth LE GATTNIST SP 800-218
Frequently Asked Questions
It depends on the platforms, the backend scope and the device features. We agree a fixed first release on the scoping call, usually one platform first, and plan the schedule from that scope.
Build native when you need deep hardware access or platform-specific UI. Build hybrid with React Native or Flutter when one team needs both stores and the hardware needs are standard. The decision table above gives the full comparison.
Yes. We build companion apps that pair with, configure and read data from connected devices over Bluetooth Low Energy or Wi-Fi, including health devices that follow the Bluetooth SIG health service specifications.
Yes. The backend connects to your CRM, payments, identity provider, EHR or internal APIs. Those integrations are scoped in the first release and tested against real sandboxes in the first sprints.
Yes. Most apps start as a fixed-scope first release on one platform, often a web app plus one native app, with the second platform added when usage justifies it.
We do, using your developer accounts. You own the accounts and the listings; we prepare the builds, disclosures, screenshots and review notes and respond to review feedback.
Engineers use AI tools for drafts, tests and reviews. Every change still goes through human code review, automated tests on real devices and the store release checklist before it ships.
A scoping call, a prototype of the key screens, then a fixed first release on the platform your first users actually use. The backend is designed so the second platform can share it later.