Augmented reality software for schools: a teacher's guide

Choosing augmented reality software for schools is a different problem from choosing it for a marketing team. The demo always looks brilliant on a sales rep's flagship phone. The real question is whether it survives contact with thirty mixed devices, a filtered network, students who cannot install apps or hand over personal email addresses, and a teacher who has forty minutes and no IT support on call.

This guide is written for that reality. It covers what schools genuinely need from AR software, a procurement checklist you can put in front of any vendor, an honest account of what works on which devices, and a classroom workflow that holds up in a real lesson. If you are after lesson ideas rather than tooling, start with our companion piece on augmented reality in education and come back here when you are evaluating platforms.

What schools actually need from augmented reality software

No app installs, ever

The fastest way to kill an AR lesson is an app install. School devices are usually managed, app store accounts are locked down, and even where installs are possible, walking a class through one eats the lesson. Browser-based AR sidesteps all of it: a published experience is a link, students open it by scanning a QR code, and the camera view starts in the browser that is already on the device. When you evaluate software, treat "opens from a link with nothing to install" as a hard requirement, not a nice-to-have.

Coverage on the devices you actually have

School hardware is rarely uniform: a trolley of ageing iPads, a set of mid-range Android tablets, students' own phones on a bring-your-own-device day. Be sceptical of any capability claim that is not broken down by device type. As a rule of thumb for browser AR: image tracking - content anchored to a printed picture, worksheet or poster - works on recent iOS Safari and Android Chrome, which makes it the mode that covers a whole class. Markerless world tracking is patchier: the full surface-detection, tap-to-place experience needs Android Chrome on a device with ARCore, while iPhones, iPads and other devices without that support get a reduced fallback at best. Our image tracking vs world tracking guide covers the difference in depth; the short version for schools is that image-tracked scenes are the dependable default for mixed fleets.

Student accounts without personal email addresses or billing

Most consumer sign-up flows are wrong for a classroom. Students under thirteen often cannot consent to accounts themselves, many do not have school email addresses, and no student should ever be one click from a payment form. Good school-oriented AR software inverts the model: the teacher owns the accounts, creates or invites students under their own umbrella, and the student experience contains no billing at all. If a platform's only path to a student account is a public sign-up page with an email field and a pricing link, it was not designed for schools.

Teacher visibility and control

In a classroom, the teacher needs to see and manage everything: which students exist, which class group they belong to, and what they are building. The practical test is whether a teacher can open a student's project directly - to fix a broken scene, to mark work, or to remove something inappropriate - without asking the student to share anything. Bulk operations matter too; at the end of a school year you want to move or remove a whole class in a few clicks, not one account at a time.

Choosing augmented reality software for schools: a procurement checklist

Before any pilot, put these questions to the vendor in writing. They separate education-ready platforms from consumer tools with an education landing page.

1. Distribution: Can students view published AR from a link or QR code in the browser, with no app install and no viewer account?
2. Device coverage: Which features work on iOS Safari and which on Android Chrome, stated separately? What exactly happens on devices that do not support a feature - a graceful fallback, or a blank screen?
3. Student accounts: Can teachers create and manage student accounts without personal student email addresses? Are student accounts completely free of billing and payment prompts?
4. Oversight: Can teachers organise students into class groups, open and edit student projects, and remove accounts in bulk?
5. Data protection: What personal data is collected about students, where is it stored, and who is the legal entity you would name in your data processing records? Ask for the privacy policy and a named contact before the pilot, not after.
6. Cost model: Is pricing per student, per teacher or per school? What happens when you go over the included seats mid-year - a forced plan upgrade, or a small top-up?
7. Exit: If you stop paying, what happens to student work and published links?

None of these questions require technical knowledge to ask, and the speed and clarity of the answers tells you a lot about how much the vendor works with schools.

How AR Works handles the classroom

AR Works for schools was built around the checklist above. The editor runs in a normal desktop browser with no software to deploy, and everything students publish opens from a link and QR code in the phone or tablet browser - no installs, no viewer accounts.

On the management side, teachers get their own student roster: they can create student accounts directly - assigning each student a sign-in username in email format, with no working inbox required and nothing ever emailed to students - or share a class invite link that students use to join, with joins capped by the seats the teacher actually has. Students are organised into class groups, can be moved or removed in bulk, and their accounts have no billing surface at all - there is nothing for a student to buy or subscribe to. Teachers can open and edit any of their students' projects directly, which turns marking and rescuing a stuck project into a thirty-second job rather than a screen-sharing session.

On cost, the entry point is genuinely free: the free plan includes the full editor, both tracking modes, and publishing to a shareable link and QR code, so a single teacher can pilot AR in one class without a purchase order. For whole-school use there is an invitation-only Education plan at 99.99 GBP per month, which includes up to 100 student seats, with one-time top-ups available for extra seats rather than a forced jump to a bigger contract. Individual teachers who outgrow the free plan can also use the standard Pro plan at 29.99 GBP per month or 299 GBP per year. Details are on the pricing page, and the Education plan starts with a conversation rather than a checkout - which, for school procurement, is usually how it needs to work anyway.

A classroom workflow that survives a real lesson

Here is a pattern that works for a student-built AR project across two or three lessons, using any browser-based platform with teacher-managed accounts.

1. Before lesson one: The teacher creates a class group and either pre-creates student accounts or generates an invite link to share on the board. They also build a small example project - one image target, one 3D object, one tap interaction - to demonstrate and to set the scope.
2. Lesson one - build: Students work in the browser editor on the school's laptops or desktops. Keep the brief narrow: one printed target image, two or three objects, one interaction. Narrow briefs finish; open-ended ones do not.
3. Between lessons: The teacher opens each student project directly, checks content, and fixes anything broken. This is where teacher edit access earns its place on the procurement checklist.
4. Lesson two - publish and view: Students publish, print or display their QR codes, and the class does a gallery walk with tablets or phones, scanning each other's work. Because viewing is just a browser link, one shared trolley of devices covers the whole room.

Two practical notes from the field: print target images at a decent size with good contrast (A5 or larger works well), and check the AR viewing step on the school network and the actual class devices before the lesson - camera access in the browser requires a secure HTTPS connection, and a two-minute corridor test beats discovering a filtering issue live.

Where to start

Start smaller than the vendor demo suggests. Pick one class, one subject and one image-tracked project, run it end to end on your own devices, and use the procurement checklist above on whatever you pilot. If you want to try that pilot on AR Works, you can create a free account and build the example project yourself in an afternoon - and if it holds up in your classroom, the school conversation about seats and rollout can follow from evidence rather than a brochure.