The one-sentence test
Write the app's job as one sentence with a person, a verb and an outcome: "A technician scans an asset tag and records that the check is done." If you need "and also" twice, you are describing two apps, or one app and a later release. The sentence becomes the first line of the brief and the yardstick for every feature request after it. This guide covers scope, cost drivers and tradeoffs; the page on custom utility app development shows how we build one.
- Good: "A shop assistant scans a product barcode and sees the stock count in the back room."
- Good: "A carer gets a reminder for each client visit and marks it done."
- Too wide: "An app for our team to manage stock, schedules, timesheets and messages." That is an operations platform; see the inventory app guide for how to split it.
Scanner, reminder and tracker: the same scope questions
Most custom utilities are one of three shapes. Each one costs more or less depending on the same three questions: how many workflows, whether data syncs, and what the app is allowed to touch.
| Example | Core workflow | Sync | Permissions | Where scope grows |
|---|---|---|---|---|
| Scanner | Scan a barcode or QR, look up or log the item | Lookup against your data; logs sent to a server | Camera; staff sign-in if logs matter | Offline scanning, batch mode, lookups in another system |
| Reminder | Schedule a task, notify at the right time, mark done | None if personal; server if a manager assigns tasks | Notifications | Recurring rules, escalation if missed, manager view |
| Tracker | Log an entry, see history and a simple chart | None if personal; server for shared or multi-device | Optional: location, health data, photos | Exports, sharing, health or location data, reports |
Our custom utility app page has a worked workflow and the version-one feature list for this kind of tool.
Count workflows, not screens
A workflow is a path a person follows from start to finish: scan and log, review today's list, correct a mistake, export last month. Screens follow from workflows, and so does testing. A utility with two workflows and eight screens is usually simpler than one with five workflows and the same number of screens, because each workflow carries its own edge cases.
Sync and permissions are the hidden cost
The moment data has to appear on more than one phone, the app needs a backend, accounts and a plan for conflicts. That is often the largest jump in a utility quote. If the tool is for one person on one device, keeping data on the phone is a real option; the local or cloud guide works through the same workflow both ways.
| Permission or role | What it adds to the build |
|---|---|
| Camera | Scanning library, low-light and damaged-code handling |
| Notifications | Permission prompt, scheduling, behaviour when the user declines |
| Location | Store privacy disclosures, background rules, battery testing |
| Health or fitness data | Platform health APIs and extra privacy review |
| Photos and files | Upload, storage and size limits |
| User roles | Sign-in, role checks on the server, an admin to manage people |
Check for an existing app first
The app stores already hold thousands of scanners, reminder apps and trackers. If an existing one does your job and you can live with its data staying in the vendor's account, use it. A custom utility makes sense when the job touches your own data or systems, when the rules are particular to your business, or when you want the tool under your brand and in your control. If your team is currently doing the job in a spreadsheet, read turning a spreadsheet into an app first; sometimes a better sheet is the right answer.
What to send for a utility app quote
Utility app brief
- The one-sentence job
- Who uses it, and how many people
- Each workflow, start to finish, in plain steps
- Where the data lives now and where it should live
- Which phone features it needs: camera, notifications, location
- Whether different people need different permissions
- What happens when there is no signal
- What is explicitly out of scope for version one
Send it through the app quote form. The written scope that comes back lists the workflows, assumptions and integrations the quote covers.
Frequently asked questions
How much does a utility app cost?
It depends on the number of workflows, whether data syncs to a server and which permissions and roles it needs. DFY sends a written scope and quote rather than a fixed price.
Does a utility app need a backend?
Only if data must be shared between people or devices, or backed up outside the phone. A single-user tool can often keep data on the device.
Can a scanner app work offline?
Yes. It can store scans on the phone and send them when the connection returns, which adds sync and conflict handling to the scope.
Should I use an existing app instead?
If an existing scanner, reminder or tracker does the job and you are comfortable with its data terms, yes. Build when the job depends on your own data or rules.
Written and reviewed by the DFY Games team. Published ; facts checked . Prices and store rules change: check the linked sources before you rely on a figure.