A school app earns its place when it shortens the distance between a person and the next useful action. It should not be a smaller copy of the school website, and it should not force staff to ask a developer for routine updates.
The strongest evaluation question is not “How many features are listed?” It is: “Can a family, teacher, or school leader reach the right current information quickly, and can authorized staff keep that information correct?”
1. A real mobile front door
The home screen should prioritize what changes and what people use repeatedly: urgent notices, today’s events, high-use forms, common resources, and a clear way to find more. Navigation labels should use school language rather than vendor terminology.
- Branded iOS and Android presentation
- Push notifications that lead to useful destinations
- Calendars and events
- Forms, documents, handbooks, links, directories, and contacts
- Search or approved-information assistance
2. A management console is part of the product
Content changes daily. A responsible app offer therefore includes the browser-based tools authorized staff use to update navigation, resources, events, alerts, and knowledge sources. If this layer is missing or priced as an unexpected add-on, the school should ask who is expected to keep the app current.
For Auzi, the Admin Console is included with every branded app. The school manages day-to-day information; Auzi maintains the reusable software.
3. Public information should remain easy
Do not put every useful resource behind a login. General calendars, policies, enrollment information, contacts, public forms, and family resources should remain easy to reach unless there is a clear privacy reason to authenticate.
When private information is needed, the product should explain the school, tenant, and role boundary in plain language. “Secure portal” is not enough detail on its own.
4. Notifications need governance
Push notifications are valuable because they reach a carried device. That same reach creates responsibility. Schools should decide who can send notices, which audiences can receive them, where each notice links, and how expired information is handled.
SMS should be priced separately when it carries carrier costs or high-volume usage. A vendor should not call both push and SMS “unlimited messaging” without defining the delivery channels.
5. Accessibility is part of everyday usefulness
Mobile interfaces need readable text, strong contrast, meaningful labels, comfortable touch targets, predictable focus, zoom and reflow, and alternatives to motion. The W3C recommends WCAG 2.2 as the current accessibility target, including criteria for focus not being obscured and minimum target size.
Schools should also ask how the vendor handles accessibility of school-provided documents and content. Product accessibility cannot repair an inaccessible PDF automatically.
6. School-specific AI needs a defined source boundary
An assistant should tell the school what sources it uses, who approves them, whether the context is public or authenticated, and what happens when the information is incomplete. Generic web search is not the same as an answer grounded in school-approved content.
AI allowances, premium models, and high-volume use should be defined in scope. “Unlimited AI” is not a credible substitute for a usage model.
7. The app should have an expansion path
A school may begin with public communication and later need family accounts, teacher resources, approvals, SSO, SIS connections, or multi-campus administration. Ask whether those needs fit a shared product model or require a separate custom application.
The healthier model is usually configurable branding, content, roles, permissions, and standard modules inside a reusable platform, with unique software work scoped separately.
A short evaluation checklist
- Can a family reach the top five destinations in one or two taps?
- Can authorized staff update the app without a developer?
- Is the management console included?
- Are public and private information clearly separated?
- Are AI sources and audiences defined?
- Are annual, launch, usage, and custom costs visible?
- Does the product support keyboard, touch, zoom, and reduced motion?
- Can the school add secure roles and workflows without replacing the app?
Make the comparison concrete.
Auzi publishes its starting price, launch cost, standard scope, and common add-ons before a sales call.