What this package is
Manage adds a web console so the office can run the app itself. Everything the app sends in shows up straight away, and notifications can go to every user or a chosen group from one page, without waiting for a developer.
The app gains maps and location while people are working, recorded only between the moment a user starts a job and the moment they finish it. Screens go up to fifteen, followed by 60 days of support after handover.
It suits businesses with someone in the office who directs the work or talks to users directly. If nobody will sit in front of a console yet, Device is enough and costs less.
See it working
Nothing is open yet. Send the urgent job from the office and watch the phone screen.
This package also sends to a group from the web console, with a confirmation that states how many people will receive it before anything goes.
This is the one thing a website genuinely cannot do. Once someone closes the tab, a website can reach nobody. It has to wait for them to come back. An app that is closed, in a pocket, still lights up the lock screen. If your work depends on telling someone right now, that is the reason to build an app, not because an app looks better.
This mirrors the screens of the delivered app. Everything here lives in this page and is connected to nothing. The real thing is built with React Native and Expo: native screens on iPhone and Android from one codebase.
The working proof is mobile-ai-chat, a chat app I wrote in React Native and Expo that keeps the AI key on the server rather than inside the app. The whole codebase is open to read. Read the code on GitHub
Everything you get
This list is the entire scope of the package. Nothing is hidden in a contract.
- Everything in Device
- Up to 15 screens
- Web admin console for reading everything the app sends in
- Send notifications to every user or to chosen groups from the console
- Maps and location while people are out working
- Technical handover doc in English: how it is built, where data goes, how to build it again
- Replies inside the working hours written into the contract, counted in your time zone
- 60 days of support after handover
- Developer account fees: Apple charges 99 US dollars a year and Google Play a one-time 25 US dollars, paid under your own company name so the app belongs to you and not to me.
- Pressing submit in the stores for you. I prepare every file and document, but the submission should happen inside your own accounts. I will walk you through it while you do it.
- The time Apple and Google take to review the app. It is not counted in the delivery window, and approval is the store's decision.
- Running costs for your backend, maps, and other outside services, billed to your own accounts by what you actually use.
- Ads and getting people to install it. That is marketing, a different line of work from mine.
- A registered company on my side. I am one developer working under my own name in Thailand, and the contract is with me personally, not with an agency.
Questions about this package
Are maps expensive to run?
It depends on how often maps are opened. Map providers include a free monthly allowance, and small to mid-sized businesses usually stay inside it. I estimate usage from your user numbers before we start and set a usage cap inside your own account.
Does it track location all the time?
No. Location is recorded only between a user starting a job and finishing it, and both iPhone and Android require the app to ask permission anyway. Tracking outside working time is a risk under data protection law and for staff trust alike.
Can the console be used on a phone?
Yes. It is a web page that adapts to the screen, but it is designed mainly for a computer, because reading data and sending group notifications is easier on a large screen.
How often can we send notifications from the console?
Whenever you like, without going through me. There is one safeguard: a confirmation step showing how many people will receive the message before it sends, because a message to the wrong group cannot be recalled.
What does support after handover cover?
Fixing problems that show up once the app is live and answering questions about using it during the 60 days after handover, which is when real users find the things nobody thought of in testing. New features outside the specification are not included, and I price those separately before any work starts.