Best learning apps for NZ schools

Individual teachers can trial an app in an afternoon. Choosing tools for a whole kura is a different exercise — one wrong pick means retraining staff, migrating data, and explaining to a board why last year's subscription is being replaced. Whole-school app evaluation needs a repeatable framework, not a single champion's enthusiasm.

This article sets out what a defensible, whole-school evaluation of learning apps looks like in Aotearoa, and where LearnSpace fits when a school is weighing options.

What "best" means at whole-school scale

An app that suits one classroom is not automatically ready for a whole kura. At school level, the criteria shift toward things individual teachers rarely need to check themselves:

Criterion	Why it matters for leadership
Curriculum alignment across year levels	Consistency from new entrants through to Year 8, not just one syndicate
Privacy and NAG 5 compliance	Vendor must meet NZ student data expectations, not just generic terms of service
SSO and rostering integration	Staff time is not consumed re-creating accounts every term
Total cost of ownership	Licence cost plus admin time plus training, not sticker price alone
Vendor stability and support	A local or responsive support channel, not an offshore ticket queue
Reporting that leadership can use	Dashboards useful at syndicate and board level, not only classroom level

For the curriculum dimension specifically, Tāhūrangi remains the reference point — tools that map cleanly to its learning areas are far easier to justify to staff and whānau than ones requiring your own translation layer.

Start with a documented evaluation process

Ad hoc adoption — a syndicate leader finds something they like and it spreads by word of mouth — creates exactly the fragmentation that later costs a school time and money to unwind. A lightweight, repeatable process protects against this:

1. Define the gap the app fills (a specific curriculum or workflow need, not "more digital learning")
2. Shortlist two or three options against the criteria table above
3. Run a bounded pilot with a defined start and end date and a named owner
4. Review pilot data — usage, staff feedback, learner outcomes — before committing school-wide
5. Confirm privacy and procurement sign-off before rollout, not after

If your school already runs formal procurement, vendor questions for an RFP gives a ready-made question set to send suppliers, and how NZ schools evaluate edtech covers the broader decision-making context this process sits inside.

Privacy, data, and NAG 5

Any app handling student data needs scrutiny beyond "is it free." Ask vendors directly:

• Where is data hosted, and does that meet NZ expectations?
• What happens to student data if the school ends the subscription?
• Is there a documented privacy policy specific to child users, not a generic adult ToS?
• Does the vendor support data minimisation — only collecting what is needed?

Schools already juggling privacy questions across multiple systems may find it efficient to review these alongside broader compliance work — see the student data stewardship checklist for a structured approach that extends beyond any single app.

Categories worth standardising school-wide

Most kura get the most value from standardising on one tool per core area rather than letting every syndicate choose independently:

Literacy

A single, curriculum-aligned literacy tool used consistently from junior to senior primary lets progress data follow a learner through the school, rather than resetting each time they change class.

Numeracy

The same logic applies to numeracy — a shared strategy-based tool, aligned to mathematics Years 0–8 progressions, gives leadership a consistent view of number sense development across the school.

Assessment and reporting support

Tools that feed into your existing reporting-to-whānau process are worth more than ones that create a second, disconnected data source. If reporting consistency is a live issue, reporting to whānau covers the wider picture this fits into.

Red flags at procurement stage

• Pricing that is only available after a sales call, with no published tiers
• Reluctance to answer direct data-hosting or NAG 5 questions in writing
• No option for a bounded, no-obligation pilot
• SSO/rostering integration described as "on the roadmap"
• Case studies exclusively from overseas systems with no NZ curriculum reference

A vendor unwilling to answer these plainly at the enquiry stage is unlikely to improve once a contract is signed.

LearnSpace for whole-school rollout

LearnSpace is designed with whole-school adoption in mind, not just individual classroom trials:

• Curriculum-aligned sequencing informed by the Te Mātaiaho rollout, consistent from new entrants to Year 8
• No ads in any ākonga-facing experience
• School-level dashboards for leadership alongside classroom-level views for kaiako
• SSO and rostering support designed to reduce admin overhead at scale
• A structured trial pathway — start with /schools to scope a whole-school pilot, or /signup for an initial trial

We are transparent that LearnSpace is our product, and we expect schools to run it through the same evaluation process outlined above rather than take our word for it. See how we compare directly in LearnSpace vs Education Perfect if you are weighing us against an incumbent.

Budgeting realistically

Whole-school licences rarely cost only the sticker price. Factor in:

• Staff time for initial training and ongoing PLD
• Admin time for account management each term
• Any hardware or connectivity gaps the tool assumes are already solved
• Renewal timing against your annual budget cycle, so decisions are not rushed in Term 4

A moderately priced tool with low admin overhead often costs less over a year than a cheaper one that consumes staff time in workarounds.

Bringing staff along

Even a well-chosen app fails if kaiako were not part of the decision. Share the shortlist and pilot results with staff before finalising, and be explicit about what problem the tool solves — time saved, a curriculum gap filled, or better visibility of progress. Staff who understand the "why" adopt tools faster and raise issues earlier, before they become embedded workarounds.

Handling multi-campus and area schools

Kura with multiple campuses, satellite classes, or a wide year-level span face an extra layer of complexity: a tool that works well for a single-site primary may not scale cleanly across sites with different connectivity, device fleets, or local IT support arrangements. Before signing a whole-school agreement, confirm the vendor has actually supported multi-site NZ rollouts before, not just single-school ones, and ask for a reference site of comparable size and structure to your own. A short call with another NZ school's leadership team about their real rollout experience is worth more than any vendor case study, and it often surfaces implementation issues — timetabling clashes, uneven connectivity between sites, staff training gaps — that a sales conversation alone will not.

Reviewing after twelve months, not just at renewal

Set a calendar reminder to review each whole-school tool properly at the twelve-month mark, independent of the renewal date. Renewal timing pressures a decision; a standalone review does not. Ask the same questions you asked at procurement — is it still meeting the original gap, is usage still active across syndicates, has support been responsive — and be willing to discontinue a tool that has quietly stopped earning its place, even if switching costs something in short-term disruption.

Where to start

• Explore the LearnSpace catalogue: /apps
• Scope a school-wide pilot: /schools
• Start an initial trial: /signup
• More leadership-focused reading: /blog/schools

The best learning apps for a NZ school are not simply the ones with the most classroom fans — they are the ones that survive a documented evaluation, meet privacy obligations, and still make sense on the budget line a year after the trial ends.