An employee app is not a shrunken website. The floor opens a phone to close today’s tickets, not to read culture. Once IA stacks by department—attendance, news, mall, votes, directory—reporting sinks to a fourth-level menu. People in gloves stay on paper. The gap with and without an entry is in Field work with a mobile entry versus without. Design it as a work tool. See Brochure mini program versus a work tool.
Fewer features so submit becomes the only habit
Phase one lists the three to five phone actions and cuts decoration. Finish patrols on site and rework drops. See Finish patrols on site, cut rework. Whether you need offline is in No network on site—do you need offline. If nobody uses it after launch, check dual tracks and heavy login first. See Launched, unused: how to diagnose. Do not give employees, customers and stores the same home.
DaXi walks a crew first, sees whether evidence lives in a notebook or a group, then draws four bottom tabs. To plan it, go to the Apps & Mini Programs and name the roles. APP or mini program as the main entry is in Mini program or APP as the main entry.
IA follows tasks, not departments. Process, warehouse and QC all report work. Do not ship three entries and three homes. Tasks aggregate by person, scan loads the object, submit hits one ticket model. Culture, votes and a mall can live under Discover. They should not be the first screen. Shipping an employee shell just to “have an APP” is the failure in Why shipping an APP just to “have one” fails.
Four bottom tabs are a ceiling, not a floor. A fifth “More” hiding twelve gray icons is no architecture. Phase one lets one crew finish today’s patrol, then copy to the next. Copy objects and permissions. Do not change nav if the habit is to travel.
Permissions, reports and killing accounts matter more than another feature
Isolate permissions by crew and warehouse so stores do not see each other’s tasks. A data leak is worse than missing a feature; people snap back to private sheets. Admin reports stay on the web. Do not stuff them into the employee APP. Charts on open tell the floor “this is not for me.” The day a badge is disabled, the mobile session dies. A leaver who can still report is more dangerous than a missing feature. Accounts and the back office must be one. See Why one back office keeps multi-end data from forking.
Training is not a feature list. Walk a new hire through submitting today’s document. If they can submit, the architecture is right. If they still ask “where is reporting,” the entry is still too deep.