An Internal Employee App: When the Phone Is Required, and When a Mobile Website Is Enough
31 Oct 2026
A desk employee does not need an app to open a policy once a month. An app is warranted when the work repeats away from a desk and an approval cannot wait for email. This guide covers approvals, announcements and what to leave out of the first release.
A company asks for an employee app because WhatsApp has mixed an office announcement with a private chat, or because a leave approval sits in an inbox the manager does not open while standing on a site. The request is clear. The answer is not always an app on a public store. Sometimes a signed-in page on the phone closes the need. The difference is how often the action repeats, whether a prompt must be opened today, and whether the network and the device can carry a browser.
Ask about the employee day, not about a wish list. A guard, a site technician, a driver or a shift supervisor has the phone as the only device. An accounts clerk at a large screen opens a form once. An app for the first person may be the right build. The same app for the second person adds an install and an update with no use. Design the internal tool for the person who moves, then invite the desk employee if a screen is truly useful to them.
When a mobile website is enough
- Use is once a week or less, such as reading a policy or sending a form that is rare.
- Nothing has to arrive within the hour, and email or a message from the manager is enough.
- The employee is on a stable office network, and the page is checked on a real phone before launch.
- The form does not need to be saved when the network drops in a basement or on a site.
- Sign-in uses a company account, and the page is not a public link with no password.
When an app is warranted
An app is warranted when the action repeats several times a day away from a desk: an approval, a fault report, or a confirmation that a shift started. A prompt on the phone arrives where email gets lost. Saving on the device and sending later matters for someone who works on a site with a weak network. The install itself reminds the employee that this is a work tool, not a tab lost among headlines. Those are operational reasons. Copying a competitor because they published an app is not a brief that can be estimated.
An internal app may never be offered to the public. A distribution list for staff, or a private store when the company manages the devices, is a different path from a customer page on Google Play. Say at the start that the user is an employee only. The public store path, and the paperwork that comes with it, should not be forced onto a tool no customer will search for. If you do choose a store, the account that publishes still belongs to your company.
Approvals
- A leave request shows the dates and the balance, when that balance comes from a source you trust.
- An expense request attaches a photo of the receipt, the amount and the cost line.
- A purchase under an agreed limit reaches the manager who owns that limit, not every manager.
- The log stores who asked, who approved, when, and who refused, with a reason the employee can see.
- The request does not vanish if a manager is slow: a reminder, then a step up to a second person you name.
An approval on the phone with no log is the same as an approval on WhatsApp. The value is the trace: the employee sees the state, accounts can see that the receipt arrived, and a deputy can finish if the first manager is away. Do not build a chain of five approvals in the first release if the real life of the company is one approval. A long chain is copied from a larger firm and then blocks your own staff. Start with the approval that is actually late today.
Announcements
An office announcement has one place the employee opens: the text, the date and who published it. If you must show that a shift read a safety instruction, store a seen mark. If the announcement is news with no action, the mark annoys and adds nothing. Keep the work channel apart from personal WhatsApp so nobody can say the message was lost among social posts. Open comments under an announcement turn the channel into another group. Keep them off at the start. A question goes back to the line manager outside the app, or as a limited direct message.
Leave these out of the first release. Salary detail for every employee on a phone, before HR has decided who may see what. A chat room for the whole company. A replacement for the accounting program. A file library with nobody named to update it, which will be stale within a month. All-day location of desk staff. Location, if it is required at all, belongs to a field role, with the employee informed, and during the shift rather than around the clock. An internal tool built on silent monitoring will be refused in daily use even if the design was finished.
Who keeps the app alive?
After launch an announcement needs someone to publish it, an approval needs a manager who opens it, and a defect needs a person who receives the note. An app with none of those roles sends the employee back to WhatsApp within weeks. Whether you hire inside the company or contract a team to deliver and support is a separate decision from the shape of the screen. Read that choice before you lock a build budget and then discover that nobody holds the key to the next update.
What makes the estimate drawable
Name the daily action that happens away from a desk, who approves it, how many people use it on a shift, and whether the network drops at the workplace. A paper form or a WhatsApp thread that is this action teaches more than the sentence we want an HR app. Human resources is a wide world. One action can be estimated. The world cannot.
The employee screens are mobile app design and development, and the rules a manager approves are custom software development. Who builds and who supports after launch is discussed in an in-house developer or a software company.
Describe the daily action and who approves it from start your project. The WhatsApp button at the bottom of the page can take a photo of the paper form or a short description of the shift, which is more useful than a long message with no example.
