Services / Mobile App Development
An app your customers or staff use, looked after by one person.
I build the mobile app, usually alongside the web system behind it. Your accounts are in your name from day one, and every project ships with a handover pack, as agreed in the scope.
Does this sound like you?
This is usually where the conversation about an app starts.
- “Our team can’t check anything unless they’re sitting at a desk.”
- “Customers keep asking if there’s an app, and we don’t have a good answer.”
- “We built something quickly, and now nobody wants to touch it.”
- “We don’t need a big app. We need the one thing our team actually uses.”
- “Someone quoted us for an app before they understood what we already have.”
What I’d do.
Tell me what needs to go mobile.
Describe the web system, the people who’ll use it, and the one thing they need to do from their phone.
See the first screen working on your system.
Not a mockup. A real screen connected to your actual information, so you can check it does what your team needs.
Ship it, then keep it running.
The app goes to the App Store and Google Play when it’s ready, and I stay the person you call after that.
Proof.
In the store, and on the website, from one build.
Customers checked local water contaminants on an in-store tablet, compiled as an Android app. The same results were available to dealers as a web tool on the company site.
See the water-quality project →Other mobile and tablet work.
- Companion appsA mobile version of a system you already run, using the same information, not a separate copy of it.
- Field and reporting appsFor staff away from a desk: capturing data, running inspections, tracking deliveries.
- Customer-facing toolsA donation app built for tablets, so a person could pick a good cause and pay securely without help.
“Anton took his time to really understand the project and took care to make sure that all the steps were followed as laid out. 10/10 would hire again.”
Rebecca MoralesDeveloper
How it starts, and what it costs.
You’re never committed to more than one piece.
- A free conversation.Tell me about the web system you already have, or don’t have yet, and the one thing your customers or staff need to do on their phone.
- The written plan.What the app must do, what it connects to, and a fixed quote for the first version. Fixed fee, agreed in writing before it starts, and credited against the first piece. The plan is yours to keep.
- One working piece, at a fixed price.What I quote is what you pay for the agreed scope. Every piece after it is quoted before it starts, and you can stop after any piece and keep what’s built.
Mobile apps are usually scoped alongside, or right after, the web system behind them.
If the system behind the app isn’t clear yet, that’s the first thing the written plan sorts out, so you only pay to build what the app actually needs.
Not sure where to start? Answer seven short questions →For your technical person
Why this exists
You have a web application, a dashboard, a booking system, or an internal tool that works well on desktop. But your customers or team need access from their phone or tablet: to check status, submit data, receive notifications, or use a key feature while away from their desk.
You do not need a separate app company. You need the same developer who understands your web system to extend it to mobile. Basic mobile application development, React Native when the project calls for it, not a large studio team.
What I build
- Companion Apps: mobile versions of an existing web application or specific high-use features, connected to the existing backend and database, not a separate system.
- Field & Reporting Apps: apps for teams in the field, data collection, reporting, inspections, delivery tracking, built to work with existing web infrastructure.
- Customer-Facing Mobile Apps: self-service apps for customers, booking, ordering, account management, notifications, extending the web platform to mobile.
Tech stack
- React Native, Expo, TypeScript
- Node.js (companion backend work)
- iOS, Android
- Xcode, Android Studio
- RNReact Native for iOS & Android
- 1codebase, both platforms
- APIcompanion apps for web systems
- Directsenior developer review
Both platforms at once
With React Native, both Android and iOS can be developed simultaneously. One codebase, two platforms, so there is one app to build and look after instead of two, with a native experience on both.
Important note
Mobile apps work best as companion apps to an existing web system. If there is no backend or web application yet, that may need to be built first. See Cloud Applications and API services.
Typical engagements
Mobile companion apps are typically scoped alongside or after the primary web system build.
- Focused companion app: one useful mobile workflow connected to the existing system.
- Feature-rich mobile app: a privately quoted first outcome with written acceptance.
- Combined mobile and web build: the written plan (paid discovery) first when the shared backend and platform scope remain uncertain.
Specialist terms and job titles
Also described as: mobile app development, React Native developer, iOS app developer, Android app developer, mobile app developer Cape Town, companion app development, cross-platform mobile app, mobile app for business, mobile app South Africa.
More background
- About Anton, the full story.
- Full project portfolio.
- Client reviews.
- General site FAQ.
Questions owners ask.
Do you build for both iPhone and Android?
Yes. I use a toolkit that creates both the iPhone and Android versions from one build, so you get both apps from one project.
Does the app need to connect to anything else?
Usually yes. Most apps need to talk to a server for information, logins and the rules your business runs on. If you already have a web system, the app can connect to that. If you don’t, I can build that too.
Can you build an app that stands completely on its own?
Yes, but apps that extend something you already have are where I’m most useful. If you want a fully standalone app, we’ll check during the first call whether it’s the right fit.
Do we need a big app, or can it be small?
Small is usually right. Most of the value comes from doing one job well on a phone, not rebuilding your whole system as an app.
How much does an app cost?
I give a private quote once I understand what the app needs to do, what it connects to, and what counts as finished. If that’s still unclear, the next step is the written plan. You’ll know the price of each piece before it starts. See how a project with me works →
Do you handle getting the app into the App Store and Google Play?
Yes. I handle the submission process, and work through anything Apple or Google ask for along the way.
Related help.
Tell me what the app has to do. I’ll tell you honestly if it needs to be one.
+27 87 150 9305Monday to Friday, 09:00 to 20:00 SAST. Or email info@antondevilliers.com.