Enterprise app development

Enterprise app development built for your IT team’s review and your staff’s workday

We build apps for employees, field teams and partners with single sign-on, device management and offline use designed in, then roll them out one group at a time.

Get your enterprise app scoped in writing
Trusted by the world's fastest-growing brands

What an enterprise app is

An app that lives on managed phones and has to pass a review

Enterprise app development builds the mobile apps a company’s own people use, such as technicians, drivers, sales reps and store managers, or that its partners use. The work is mostly about what the phone is allowed to hold, who is allowed to sign in and what happens when the signal drops.

9:41TodayManaged deviceJob 4471Katy, TXJob 4472Spring, TXDevice planCompany iPhoneSecurity pack8 MASVS groupsPilot group25 people firstthen 75 and 108

Built for the device plan

We ask first whether the phones are company-issued or personal, and how IT installs apps on them. The answer shapes the design, from sign-in to what is stored on the device.

Ready for the security team

Your reviewers get written answers: what the app stores, how users authenticate, what the log records and how a lost phone is handled.

Rolled out to one group first

A pilot group installs the build first. The next group joins once you approve each stage.

Two ways to get there

Build a dedicated app, or extend what you have

Some jobs are served well by a mobile view of an existing system. Others need an app of their own. The facts below decide which.

Existing system on mobileThe vendor’s mobile app or a responsive web viewDedicated appA purpose-built mobile app
Fit to the jobScreens laid out by the vendor for all customersScreens drawn around one role and its short list of tasks
Without a signalSet by the vendor’s app; ask for its offline behavior in writingWork is stored on the phone and sent when the connection returns
Device featuresLimited to the features the vendor exposesCamera, barcode scanning, signature capture and location are built in as needed
Time to first useAvailable once licenses are assignedA first milestone built and piloted before wider rollout
Cost shapeA per-user subscription that grows with headcountA build cost, then store and hosting upkeep
Who changes itYour administrators configure what the product allowsYour team asks, and the change is made in code you own
Best whenThe job matches what the vendor’s product already doesThe job is specific to your company and used all day
How we decide

The recommendation comes after we watch the job being done. If the vendor’s mobile app covers it, we say so in the written scope. If the gap is a handful of screens, we price those. If the job needs its own app, the first milestone builds the one screen your pilot group needs most.

Ownership

What your company holds from the first day

Your IT group can check each item below before the first build. The written scope lists them, and the contract states that you own the code.

The repository

The source code sits in a repository under your company’s name. Your IT group decides who can read it, and each change stays in its history.

The store accounts

The Apple Developer and Google Play accounts are registered to your company, so the app listing and its signing keys are yours.

Our access

Our engineers log in with accounts your IT group issues. Removing them is one change in your directory, and the app’s code and store listings stay with you.

Buyer review

Six things a mobile security review and a rollout touch

What IT, security and procurement teams put in front of an app supplier. Sources under each.

  1. Device managementNIST

    NIST publishes guidance on securing mobile devices in the enterprise.

    NIST SP 800-124 Rev. 2 covers the devices, the central systems that manage them and endpoint protection, for company-owned and employee-owned phones. It is guidance and carries no legal force of its own. We use that scope as the outline for the device plan, so your reviewers read the app against a document they know.

  2. App securityOWASP

    OWASP publishes a verification standard for mobile app security with eight control groups.

    The Mobile Application Security Verification Standard, MASVS, groups its controls under storage, cryptography, authentication, network, platform, code, resilience and privacy. We hold no third-party certificate against it. We use the groups as the headings of the security pack, so each answer sits under a name your reviewer recognizes.

  3. Sign-inIETF

    The IETF says native apps should sign users in through the system browser instead of an embedded web view.

    RFC 8252, “OAuth 2.0 for Native Apps”, advises external user-agents because an embedded view lets the host app capture credentials, and because the system browser lets single sign-on carry over between apps. That is the pattern we use with your identity provider.

  4. Private distributionApple

    Apple lets a company publish an app that only its own organization can see.

    Custom apps are distributed through Apple Business Manager to the organizations the developer names in App Store Connect. The organization can then push the app through its device management tool. They never appear in the public App Store. We recommend this route when the app is for your staff or dealers alone.

  5. Device controlApple

    Apple documents what device management lets an organization do on its phones.

    According to Apple’s deployment guide, a device management service lets IT teams remotely configure devices, update software and settings, monitor compliance with policies, and remotely wipe or lock a device. Our device plan lists which of those controls your app relies on and which it leaves to IT.

  6. AccessibilityW3C

    WCAG 2.2 is the current W3C standard for accessible content, and the app’s screens can be built against it.

    W3C published WCAG 2.2 as a Recommendation and updated it December 12, 2024. It sets levels A, AA and AAA, and it was written for web content, so mobile platforms add their own accessibility tools. We take AA as the target for the app’s screens, check them with VoiceOver on iOS and TalkBack on Android, and list any exception in the review notes. Whether a rule applies to your company is a question for your counsel.

What we build

Six parts of an enterprise app, and what each produces

Every part below closes with a document or a working piece, and the written scope says which.

Single sign-onSystem browserDirectory groupApp rolehvac-techniciansTechnicianhvac-dispatchDispatcherhvac-branch-mgrsManagerRemoved from directoryAccess ends

Single sign-on and roles

Sign-in through your identity provider in the system browser, with the user’s role taken from their directory group. Accounts removed from your directory lose access to the app. You receive: the sign-in configuration, the role list and the test results.

Device planSample · Lone Star HVACField techniciansCompany iPhone · device management160Install crewsCompany Android · Managed Play48DispatchersOffice computer · web, no install12Branch managersPersonal phone · private link8

Device management plan

How the app is installed, configured and removed on company-issued and personal phones, and what it holds on the device. You receive: the device plan, the configuration keys your management tool needs and the private distribution steps.

OutboxAirplane modeJob 4471 · 3 photos10:14 a.m.Job 4471 · signature10:21 a.m.Job 4472 · parts used11:02 a.m.Sends when the signal returnsConflict rule · same job, two peopleBoth edits kept, dispatch chooses one

Offline use and sync

Work saved on the phone when there is no signal and sent when the connection returns, with a rule for what happens when two people change the same job. You receive: the sync rules and a test script for airplane mode.

Interface log3 systemsAllField serviceCRMERPTimeToCallResult10:14:02FSMPOST /jobs/4471/close20110:14:03CRMPATCH /accounts/881220010:14:05ERPPOST /parts-usage503 · retry10:14:35ERPPOST /parts-usage201

System connections

The app reads from and writes to the systems that hold the records, such as your CRM, field service or ERP, through their APIs. You receive: the interface list and a log your team can read.

Security review packOWASP MASVSStorageCryptographyAuthenticationNetworkPlatformCodeResiliencePrivacy7 answered1 marked for your teamIndependent attestationNone held

Security review pack

Written answers to your questionnaire, set out under the eight MASVS control groups, with a data-flow diagram and a dependency scan. You receive: the answers, the diagram, the scan results and a list of findings with proposed fixes.

Staged rollout208 people2575108PilotHouston techniciansApprovedSecond wave55 Houston, 20 DFWTo approveThird wave60 DFW, 48 installWaitingPull back: a group returns to paper formsIT runbook4 IT administrators

Staged rollout

A pilot group first, then wider groups, with a check written for each stage and a way to pull the build back. You receive: the rollout plan, the guides for each user group and the runbook for your IT team.

How it runs

Watch, plan, pilot, hand over

The next stage begins after you sign off on the one before.

device-plan.csv

Device and access plan

Sample · Lone Star HVAC Services, Houston and Dallas–Fort Worth, TX
GroupPeopleDeviceHow the app is installed
Field technicians160Company-issued iPhonePushed through device management
Install crews48Company-issued AndroidManaged Google Play
Dispatchers12Office computerWeb view, no install
Branch managers8Personal phonePrivate store link, sign-in required
Personal phones get fewer stored records. The plan lists what each group may keep on the device.

Our stack

The tools behind the app

What the screens, the code and the testing would be made with. Your IT team gets access to the repository, the error log and the design files. Pick a tool to see where it is used.

Figma
Why Figma

Figma is a design tool that produces screens and a prototype you can tap through on a phone.

How we use it

Each user group tries the prototype on a phone, so technicians and dispatchers see their screen before it is built.

Real-timeDev handoffTokens
FigmaYes
SketchSome
Static mockupsNo

Questions

Enterprise app development, answered

Start here

Get your enterprise app scoped in writing

Tell us who will use the app and where they will be. We’ll send a device plan, the contents of the first milestone and its price.