01
Record information on location
Give people a clear way to record a field visit or update assigned work while they are there.
Mobile app development · Edmonton + remote
Mobile apps for your customers and your team.
I can build an iPhone and Android app around the work people need to do on the go, with a companion web application and shared backend where useful. Start with the essential journey and one useful first version.
Work directly with Brad Conklin, Featherply’s founder and product engineer.
Start with a free fit review.
If I can’t give you a fixed quote yet, the first paid phase is capped at $500 USD.
Pricing and process →
Platform needs, device features, and release requirements are part of the scope.
Where mobile helps
Make the next step practical on a phone.
A mobile app should earn its place by making an important task easier to complete. We start with who uses it, where they are, and what they need to finish.
02
Check progress and take action
Help a customer follow a request, review its details, or complete the next step.
03
Use device features when they help
Notifications, camera capture, and offline access can support the task when they are part of the agreed scope.
A responsive web application may be enough when people mainly need to view information and complete forms in a browser. We choose the approach around the task and the device capabilities it needs.
One visit, from assignment to recorded outcome.
An employee opens an assigned visit, records the outcome, and sees whether it has reached the office. The web view gives the team a consistent record to work from. Notifications, camera capture, and offline behaviour are options to scope.
Illustrative example
01 / Assigned visit
Visit 104
Example Site
Assigned visitNext step: record the outcome.
02 / Outcome entry
Outcome recorded
Visit completed; notes attached to the record.
When offline
Saved on this device; waiting to sync.03 / Office record
Received by office
After connection returns, the office can see the recorded outcome.
Conflicting update
Needs review.
What I can build
The app and the services behind it.
01
Customer apps
Give customers a practical way to follow their account or approve a request from a phone.
02
Field tools
Help a technician open assigned work and record a visit, with device and connection needs considered from the start.
03
Companion web applications
Give office staff a larger-screen view for reviewing results and managing the work behind the app.
04
Shared accounts and business rules
Connect mobile and web interfaces to the same accounts, permissions, and business rules. Payments and external connections can be included where the project needs them.
Share the useful parts. Plan for each platform.
For iPhone and Android apps, I use React Native, with shared code where appropriate and platform-specific work where needed. A companion web application can share the backend while using an interface suited to a larger screen.
01
Permissions and device behaviour
Agree on which device features are useful, how permission requests work, and what happens when a person declines them.
02
Connection and offline needs
Decide what must work without a connection, what can wait, and how conflicting changes should be reviewed.
03
Accessibility and distribution
Include accessibility, supported devices, release distribution, and platform review requirements in the scope. Store submission can be agreed as part of that work.
How projects start
Start with the journey people need most.
Start with a free fit review. If the requirements are clear enough, I provide a fixed quote directly. If important questions need investigation first, I’ll propose a small planning phase with an agreed scope and price of no more than $500 USD.
Understand the mobile task
Talk through who uses the app, where they are, and what they need to finish.
Choose one meaningful journey
Agree on the first user journey, the backend it needs, intended devices, and what the finished work needs to do.
Build and check on the intended devices
Review the app’s main journey and the relevant permissions, connection states, and accessibility.
Prepare the agreed release
Hand over the application and agree on distribution arrangements and operating responsibilities.
You keep the documented requirements, findings, recommended approach, scope boundaries, and acceptance criteria. When the build is viable and sufficiently defined, the handoff includes a fixed proposal for the first implementation, with timing and operating responsibilities. If the right answer is not to proceed, you receive the reasons and alternatives instead. You can use the handoff with Featherply, another developer, or nobody.
Start a conversation
What should someone be able to do in the app?
I’ll review your message and reply within two business days with any initial questions and a suggested next step. This initial fit review is free.
No paid work starts until its scope and price are agreed and you explicitly approve it.
Privacy and your enquiry
I treat what you share as private and use it only to review your enquiry unless we agree to use it for a project. Share only what you are comfortable sending; a short description or anonymized example is enough to start.
This page may use MaxMind to estimate your country or province from your IP address and adjust its wording. We don’t request precise device location or attach the inferred location to your enquiry. Campaign links can select regional wording independently of your location.