In this post, I'll be pulling together some models for the use of devices in schools and making some comparisons. This is a complex area of school management, so for the sake of clarity and brevity, I'll be restricting myself specifically to devices, not to other pieces of hardware. Although I will need to refer to software, I'll only do so in so far is it is tied into some devices.
Since I rolled out BYOD at Oswestry back in 2012, a lot has changed. Technology has moved on and many schools have moved on to the second or third iteration of their chosen solution. Some schools have made expensive mistakes, betting on solutions which quickly became superseded. Some, through accident or design, have avoided costly hardware solutions and remain blank canvasses. I hope this post will be useful to senior leaders weighing up the pros and cons of different device solutions for their schools.
Jargon-buster
Unfortunately, like most things IT-related, there are some acronyms it's useful to know about before diving into the detail. In relation to device-use in schools here are the ones you're likely to come across:
BYOD - bring your own device. Pupils (and/or teachers) may bring their own device into school to connect to the network.
CYOD - choose your own device. Pupils/teachers may choose their own device from a range of school-ordained options.
DNBYOD - do not bring your own device. Schools provide pupils/teachers with a device which they use for the duration of their time in school. There are two variations of DNBYOD (also, confusingly, sometimes dubbed YWYT - use what you are told!):
COPE - company owned, personally enabled
COBO - company owned, business only
The spectrum of control
In terms of a school's control over the devices, there is a spectrum along which the solutions above fall, best visualised diagrammatically:
Who are the main players?
Essentially there are three main 'ecosystems' which schools can choose to inhabit. Alternatively, they can choose to hedge their bets and allow for all three (or any combination thereof) to co-exist. Each ecosystem has its own quirks, as summarised below:
Apple | Microsoft | |
---|---|---|
👍🏽 Seen as premium. | 👍🏽 The ecosystem works on any device. |
👍🏽 The ecosystem works on any device. |
👍🏽 Proprietary devices are of high quality. |
👍🏽 Proprietary devices are Surface Books which as both tablets and laptops. |
👍🏽 Proprietary devices are Chromebooks, most of which are relatively low-cost. |
👍🏽 If embraced in its entirety probably the 'slickest' of the options. iPads have advantages in primary settings - simple to use, light etc. |
👍🏽 Familiar to most people, particularly to those who've been using computers for a long time. |
👍🏽 Built for the cloud, probably still the best solution for leveraging the cloud’s advantages. |
👎🏽 Locked down ecosystem – only Apple Devices can be used (iPads, MacBooks etc.) | 👎🏽 Familiarity breeds misuse. Old-school computer types are too easily able to stick to bad habits. |
👎🏽 Chromebooks are a bit cumbersome for the very youngest children. Android tablets are another possible solution, but this means (cf Apple) multiple devices. |
👎🏽 A steep learning curve for most schools. | 👎🏽 Devices tend to be lower-quality - ‘plasticky’ would best describe them. |
👎🏽 Some of the more advanced functionality of the Apple/Microsoft suite of programmes is not available in G-suite. |
👎🏽 No single device solution if you want inkability users need both a MacBook and an iPad plus a stylus etc. | 👎🏽 Less popular as a solution for very young children as there is a degree of complexity in getting set up etc. | 👎🏽 Not the best solution for computer scientists (complicated workarounds needed for programming in certain languages etc.) |
👎🏽 Expensive. |
👎🏽 Moderately expensive. |
Some people will want to point out that there are other alternatives and that this table is not exhaustive. It is true that if you object to the commercialisation of education, or to the concentration of power in the hands of just three American Tech companies, then you could take the red pill and opt for entirely open source software run on any machines of your choice. There are schools that have done this - here for example - but I suspect it's fraught with technical and logistical problems. Also, in its own way, it is just as loaded with contentious political and moral judgement as is deciding to stay mainstream. Open source enthusiasts will roll their eyes, but for the purposes of this post, I'm discussing mainstream options only.
Practicalities
There are multiple solutions to the device conundrum in schools. The more I've researched this, the more I've realised most schools have hybrid systems: some have BYOD for pupils, but not for staff; some have CYOD for younger children, but BYOD for older ones; some insist on Apple devices in one part of the school, but not in others, and so the permutations go on, ad infinitum...
The schools where the neatest solutions exist (i.e. one platform all the way through) tend to be those with limited age categories. It is relatively easy to introduce the Microsoft Surface, say, in a 13-18 school. Making this decision would be harder in a K-12 school where the needs of younger children are different and handing them a Surface to use for their school work might not be appropriate. As most international schools are K-12, most have hybrid systems. But if simplicity's your thing, it is probably the Apple solution (MacBook + iPad) which best caters for the needs of children of any age.
In Thailand, were you to go down the CYOD/DNBYOD route, these are the main contenders. I've included some models and prices to aid comparison:
Metric | Dell | Apple | MS Surface |
---|---|---|---|
Price/unit - staff | Dell 5300 13-inch ฿35,500 or Dell 5300 13-inch tablet ฿42,000 |
MacbookPro 13-inch ฿55,900 | Surface i5-8250U/128GB/8GB ฿39,990 or Surface i5-8250U/256GB/8GB ฿51,990 |
Price/unit - pupils | Dell 5300 13-inch ฿35,500 | Macbook 12-inch ฿46,100 | SurfaceGo with keyboard ฿19,680 |
Service agreement | Onsite service with spare parts (4 years) | No onsite service, 1-year warranty for spare parts | No onsite service, 1-year warranty for replacement |
Inkable? | Yes | No | Yes |
Pros | Excellent service agreement Inkable - saves paper Excellent MDM solution - a one-stop-shop Cost-effective Not locked into any software Ecosystem The closest thing that exists to a single solution for everything Staff already likely to be familiar with MS-Windows |
Seen as flagship/top of the range Ties in with iPads where these are already used Good for high-end users (artists etc.) | Lightweight, fast More of a 'statement' than Dell machines Familiarity with Microsoft Inkable - saves paper |
Cons | Some students will still want Apple machines(!) Not a 'cool' flagship Relatively low build quality |
Service agreement not as good as Dell The most expensive option Most staff would need retraining Apple does not provide onsite support |
Needs separate MDM solution at additional cost Ties students into Microsoft a little more than a 'Vanilla PC' Have poor reliability record Most staff would need retraining Microsoft does not provide onsite support |
The model we have in place at the moment at Harrow Bangkok is a hybrid. As if often the case with these things in schools, it has evolved organically. What we've arrived at is as follows:
- Ages 9 and below (UK Year 4 and below) - DNBYOD, school iPads and desktop PCs available for teachers and pupils to use in the classroom as required.
- Ages 10 to 14 (UK Years 6 to 9) - CYOD, choose an iPad whilst desktop PCs are available for teachers and pupils to use in the classroom as required. Desktop Macs are provided in the Art and Design Departments and for Music Technology.
- Ages 14 and above (UK Years 10 and above) - BYOD, bring a device with a keyboard to school for using in lessons as required. Desktop Macs are provided in the Art and Design Departments and for Music Technology.
- Teachers are supplied with a Dell laptop, the newest versions of which (Latitude 7390) are inkable.
Over the past few years we've mulled over becoming an Apple school and we've toyed with the idea of rolling out Microsoft Surfaces etc. But when it has come down to the nuts and bolts, no one solution has been the right fit for the whole school. As a result, we've made a strength out of not having committed ourselves too firmly to any particular platform. Although the array of choices can be bewildering at times, pupils leave our school not having had any particular system foisted on them. They go out into the world with the flexibility to embrace whatever computer system best fits the projects they find themselves working on.
I'd love to hear how things work in your school, particularly if you work in a K-12 international school. Do you have a similar setup? What have you found that works?