SkieHow does a branch add its own app, and how long does approval take?
If the owner allows it, a branch pastes the Google Play link into the app store, the details fill in, and the app shows as waiting for Skie. Once approved it can be published and put on lists. Approval can be turned off per organisation for trusted ones. No timing is promised here.
A branch rarely has the same needs as head office. One centre teaches a regional language with a particular app, another prepares for a different exam. Skie lets branches add apps without handing them the keys to the whole school.
The flow is short. In the app store, the branch admin pastes a Play Store link. The name, icon and other details fill in automatically. You set a category and an age band, and then the app is submitted. Your own apps wait for Skie approval, and the screen shows Waiting for Skie until it is decided. After that, you publish it from draft and attach it to the lists you want.
Whether a branch can do this at all is a choice made by the owner and the organisation. Where head office wants control, only the organisation admin adds apps and branches ask. Where trust is high, the owner can switch approval off for that organisation so new apps are available straight away.
A global catalog also exists, so an app another organisation has already added may be there to choose. Deleting a catalog app that organisations use is blocked unless it is forced, so lists in use do not break overnight.
All apps come from Google Play. Private APKs are not available yet, so a custom app needs a Play listing.
A practical tip: make the request process visible. A shared sheet where branches note the app, the reason and the grade lets head office approve in batches and spot duplicates. Approve apps in the weeks before term, not on the morning a teacher needs one.