“The APP is done; nobody downloads it” is called a marketing miss too early. Download is not step one. People must first know it exists, be willing to open a store, find the right name, wait for install, register and tap Allow. Any layer at zero looks cold in store stats. Draw the funnel first. Then decide whether to change the icon, the login—or stop forcing a download.
A customer-facing APP is harsher. Nobody downloads a use-once client to check logistics. Low-frequency lookup belongs on H5 or a mini program. Compare Is H5 enough on its own. Mini program or APP as the main entry. See Mini program or APP as the main entry. If push is why you listed an APP, confirm people allow notifications. Store installs will not buy approval speed otherwise. See How push and tasks keep approvals from dying unread.
Measure the break first. Then decide whether to keep the client
Download counts without a “heard-of-it” count mislead. Ask the floor: how many were required to use it last week? How many can say the exact store name? How many stuck on SMS? How many installed and still use paper? Numbers beat ratings. If the break is “will not install,” move the main path to a no-install container and leave the APP for people who need push or device features. If the break is login, do SMS or WeCom SSO first. Do not redraw the icon.
Listing itself is a funnel: Apple review, Android channels, expired enterprise signing can make a “finished” APP uninstallable. Write those into the release list. Do not discover them after launch. The full path is in From brief to launch: how a mobile build runs. DaXi will ask who is required to use it and how many times a day before deciding to list. To review current download data together, go to the Apps & Mini Programs and describe the current state.
Forced internal install still needs a funnel. An onboarding email “please go to the store yourself” versus enterprise distribution on the IT checklist differs by an order of magnitude. If the floor must use a personal phone, explain data, privacy and what happens after uninstall. If layer four (register / login) binds a badge, IT must resolve the badge to a person first or the floor will call the system broken. Pretty downloads and ugly logins mean the store is not the bottleneck—accounts are.
On the consumer side, store ratings feed back into layer two. Old crashes, contacts permission, slogan-only screenshots—new users walk away. Fix permissions and the first-screen job. Do not buy more ads. Put “the one job you must finish” in the first sentence of store copy. That beats a new icon for conversion.
The store name must match what the floor can search
Do not name the app with an internal project code. The floor searches “Report” and never finds “Xingchen Smart Mfg V3”—the funnel dies at layer two. Store screenshots should show real work, not only slogans. Android channel packages must not each sign a different name: a poster name that does not match the store looks like a fake app. Accept the channel list with the poster copy.
Forced hard passwords turn installs into waste
Forced download plus a forced hard password is the least friendly pair for the floor. If they can scan to log in, scan. Installs up and DAU still low—follow Launched, unused: how to diagnose and keep going. Do not stop at download counts.