--- title: "Technology in the classroom: How schools are using app development to support education" description: How schools use app development to support education, why so many classroom tools fail, and what better design and teacher involvement can change. image: https://weareaffective.com/hubfs/learning-centre-images/technology-in-the-classroom-how-schools-are-using-app-development-to-support-education.webp --- [Skip to content](https://weareaffective.com/learning-centre/technology-in-the-classroom-how-schools-are-using-app-development-to-support-edu#main-content) [![we\_are\_affective\_logo\_200](https://weareaffective.com/hs-fs/hubfs/we_are_affective_logo_200.png?width=175&height=48&name=we_are_affective_logo_200.png "we_are_affective_logo_200")](https://weareaffective.com) - [Home](https://weareaffective.com) - About Us - [Our Story](https://weareaffective.com/about) - [How We Work](https://weareaffective.com/how-we-work) - Our Services - [App Planning & Strategy](https://weareaffective.com/app-planning-strategy) - [App Design](https://weareaffective.com/app-design-agency) - [App UX Design](https://weareaffective.com/app-ux-design) - [App UI Design](https://weareaffective.com/app-ui-design) - [App Technical Architecture](https://weareaffective.com/app-architecture) - [Existing App Audits](https://weareaffective.com/app-audit) - [Case Studies](https://weareaffective.com/case-studies) - [Pricing](https://weareaffective.com/pricing) - [Learning Centre](https://weareaffective.com/learning-centre) - [Get Started](https://weareaffective.com/get-started) Expert Guide Series # Technology in the classroom: How schools are using app development to support education Table of Contents Schools have always adapted to new tools. Chalk gave way to whiteboards, textbooks gave way to tablets, and now purpose-built apps are sitting alongside lesson plans in classrooms from primary school through to sixth form. The speed of that shift has been remarkable. Within a decade, app-supported learning has moved from a novelty to an expectation, with teachers, pupils, and parents all assuming that technology will play some role in how learning happens. > The gap between what an app is supposed to do and what users actually experience opening it is particularly wide in education. But speed and quality are different things. The fact that apps are now present in classrooms does not mean they are working particularly well. A lot of what gets built and deployed in educational settings is functional in the narrow sense, it loads, it stores data, it produces a report, without doing the harder thing, which is actually getting pupils to engage with it, and helping teachers use it without adding to an already significant workload. At We Are Affective, we work on the behavioural and emotional layer of digital products. That means we think a lot about the [gap between what a product is supposed to do](https://weareaffective.com/user-psychology-app-design) and what users actually experience when they open it. That gap is everywhere in consumer apps, but it is particularly wide in educational technology, where the [emotional states of the people using the product](https://weareaffective.com/learning-centre/5-things-that-make-the-difference-between-so-so-apps-and-stellar-apps-what-your-) are rarely the ones the product was designed for. This article looks at how schools are using app development to support education, where that effort is falling short, and what better design would look like in practice. ## How Schools Are Currently Using Apps in the Classroom The range of apps now used in schools is wide. At the most straightforward end, there are administrative tools: registration systems, homework submission platforms, parent communication apps, and timetabling software. These exist primarily to reduce friction around logistics, and most of them succeed at that in a basic way. Further along the spectrum are learning tools proper, apps designed to support curriculum delivery. These include reading programmes that adjust text complexity based on progress, maths tools that generate practice problems, language learning apps, and science simulations that would be impractical or impossible to run in a physical classroom. Some schools also use apps to support pupils with additional needs, offering text-to-speech, visual timetables, and communication aids. #### Where Apps Sit in the Lesson In practice, apps in the classroom tend to occupy a few distinct roles. They are used as warm-up or consolidation activities, as independent work tools when a teacher is working with a smaller group, and increasingly as the primary mode of delivery for certain subjects or units. Some schools use them as assessment instruments, gathering data on pupil performance that feeds back into lesson planning. The ambition behind all of this is real. Schools want to personalise learning, to give pupils immediate feedback, and to free teachers from repetitive marking. The technology makes those things possible in principle. Whether any given app delivers them in practice is a different question entirely. ## The Gap Between Curriculum Goals and Classroom Reality Curriculum goals are written in ideal conditions. They describe what pupils should know and be able to do, and they assume a learning environment where attention is available, motivation is present, and teaching time is sufficient. Classrooms operate under none of those assumptions reliably. Attention is contested, motivation varies by pupil and by period, and teaching time is always shorter than it looks on paper. Apps built to support curriculum delivery often inherit the same idealism. They are designed around the capable, motivated learner who arrives at the product ready to engage. That learner exists, but they are not the only learner in the room, and they are not the learner who determines whether an app succeeds or fails in a school setting. #### The Teacher's Position Teachers are managing complexity that no app currently models well. They are tracking the emotional state of twenty or thirty pupils simultaneously, responding to behaviour, differentiating instruction in real time, and making dozens of small decisions per lesson. When an app adds to that cognitive load rather than reducing it, when it requires configuration, produces confusing outputs, or behaves inconsistently, teachers stop using it. The decision is rational. The app was supposed to help, and it isn't. The gap between curriculum goals and classroom reality is a design problem. Apps that understand the actual conditions of use, rather than the ideal ones, stand a much better chance of being used at all. ## UX/UI design built around *real* psychology We design app interfaces around how people actually think and behave. User research, psychology-driven UX/UI design and technical specs delivered as one complete package. [See how we work](https://weareaffective.com/how-we-work) [Get started](https://weareaffective.com/get-started) No commitment ## Why So Many Educational Apps Fail to Get Used According to [The Standish Group's CHAOS Report 2015](https://www.studocu.com/da/document/erhvervsakademi-aarhus/systemudvikling/chaos-report-2015-the-standish-group/19026719), 70% of app projects fail due to misaligned expectations and market misunderstanding. Educational apps are not immune to that pattern, and in some ways they are more exposed to it, because the people who commission them are rarely the people who will use them. School procurement works through budget holders, senior leaders, and sometimes local authority advisors. These are not the same people as the class teacher trying to run a lesson on a Friday afternoon, or the Year 8 pupil who has already decided the app looks boring before they have even created an account. The app gets bought based on a demonstration to one group and used by a completely different one. > The app gets bought based on a demonstration to one group and used by a completely different one. [Design that treats emotional experience as an afterthought](https://weareaffective.com/learning-centre/how-to-tell-whether-your-digital-problem-is-a-format-problem-or-a-brief-problem) compounds the problem. You can usually tell when emotional considerations came late in a product's development. Features feel bolted on rather than integrated. The marketing language mentions engagement and motivation, but the design brief was written around functionality and data capture. The result is a product that reports on learning without actually encouraging it. There is also a gap between stated interest and actual behaviour. [AppTweak's research on app market behaviour](https://www.apptweak.com/en/aso-blog/app-market-research) puts this clearly: when users are asked whether they would use an app, 60 to 80% say yes, but actual usage sits at 10 to 20%. Schools see this pattern regularly. Pilots generate enthusiasm, then the app quietly disappears from lesson plans within a term. ## The Emotional and Behavioural States Teachers and Pupils Actually Bring to Class A pupil opening an educational app at 9am on a Monday morning is in a very different state from the one the app was designed for. They might be tired, anxious about something social, disengaged from the subject, or simply carrying the residue of whatever happened before they walked into school. None of those states are unusual. They are the normal conditions of childhood and adolescence. Teachers bring their own states. A teacher managing a difficult class while covering for an absent colleague, or marking at 7pm before the next day's preparation, is not arriving at a digital tool with patience and curiosity to spare. They are arriving with a specific, bounded need: get this done, do it quickly, do not let it create new problems. #### What Emotional State Does to Engagement Emotional state shapes behaviour in products in ways that are measurable and consistent. Users who are anxious move through products more slowly, dwell on individual screens, and abandon tasks at higher rates. Users who are confident and energised move quickly, explore more features, and return more often. An app that presents the same interface to both types of user is effectively presenting two different experiences, and only one of them is likely to produce the engagement the product promised. Designing without accounting for this range is a decision to optimise for the best-case user and leave everyone else to manage on their own. ## How Emotional Framing Shapes Whether Users Engage at All The way a product frames its first moments of contact has a disproportionate effect on whether a user continues. This is true across all digital products, but it matters especially in educational settings where motivation is already variable and the cost of disengagement is real. We worked on a financial application where the core challenge was anxiety. The product was functional and information-heavy, and the team recognised that financial information produces significant anxiety in users depending on their situation, whether they are saving, spending, or uncertain about their balance. The solution was not to simplify the information or reduce the product's scope. It was to use education and framing to prepare users for what they were about to see, to situate them within the product before surfacing data, and to reduce the emotional shock of encountering financial information without context. That shift transformed the product from a functional experience into something that felt genuinely supportive. The same principle applies directly to educational apps. A pupil who opens a maths tool and is immediately presented with a difficulty level they find threatening will disengage, and that disengagement will look like avoidance or lack of effort rather than a design failure. The [framing of the first screen](https://weareaffective.com/learning-centre/what-curiosity-looks-like-in-a-first-session-and-why-most-products-design-past-i), the language used to describe tasks, the way progress is shown or withheld, these are all emotional design decisions, and they all shape whether the pupil continues. Frame the first screen of any educational app around what the user is about to achieve, not what they are about to be tested on. The difference is small in words and significant in how it lands. ## Designing for the Moment of Use, Not the Ideal User There is a design habit that produces a particular kind of failure: building for the user who is already motivated, already oriented, and already capable of handling a full information set on first contact. This habit is understandable because that user is easy to design for. They will explore, tolerate friction, and push through confusion. But they are a minority in most educational contexts, and designing for them leaves the majority of users behind. Simon's observation about meditation apps applies with equal force here: [nobody opens a product for the first time](https://weareaffective.com/learning-centre/what-a-development-team-actually-needs-to-know-about-the-user-before-sprint-one) because they are already in the ideal state for it. They open it because they need something. A pupil opening a reading app often does so because reading is already difficult for them. A teacher opening a behaviour tracking tool does so because something in the classroom is already stressful. Designing as though those users arrive calm, curious, and ready to configure their settings is a significant misread of the moment. #### Reducing Load at the Point of Entry The practical implication is that educational apps should do less in the first session, not more. Progressive disclosure, where information and options are introduced gradually as the user becomes comfortable, reduces cognitive load and keeps anxiety from rising to the point of disengagement. This is about sequencing what the user needs to know in the order that serves them emotionally as well as functionally. An app that gives a new pupil a full menu of modules, a difficulty selector, an avatar customisation screen, and a tutorial all before they have completed a single task has prioritised the product map over the user's actual experience of arriving. Introduce one goal on the first session, not a full feature set. Let the second session reveal what the first made relevant. ## How Adaptive Design Responds to Different Learner States Adapting a product to the user's emotional or behavioural state in real time is not a speculative idea. We did this on a travel app, and the approach is directly transferable to educational contexts. The logic is straightforward: [behavioural signals within the product](https://weareaffective.com/learning-centre/how-to-read-a-user-session-recording-for-emotional-signal-rather-than-task-compl), how quickly a user moves through it, how long they dwell on individual screens, whether they are completing tasks or abandoning them, are indicators of their current state. On that travel app, users who were moving slowly and dwelling on content received a narrowed view of gamification rewards, showing only the next achievable goal and one or two beyond it. Users who were moving quickly and confidently received the full reward window, so they could see all available rewards and track their progress across the whole range. The same gamification system produced two different experiences based on what the user's behaviour was communicating. #### What This Looks Like in a School App In an educational app, the equivalent might look like this. A pupil who repeatedly attempts the same type of problem without completing it receives a simplified version of the next task and a short piece of contextual support, rather than another identical attempt. A pupil who is moving quickly and completing tasks with ease receives an extension challenge or a harder variant, without being asked to self-select into it. The product is responding to what the pupil's behaviour reveals, not what the pupil's self-reported confidence level claims. This kind of adaptive response requires behavioural data to be read and acted upon in the product itself, not just reported to a teacher at the end of a session. That is a design decision, not just a technical one. ## What Schools and Developers Get Wrong When Collaborating The relationship between schools and the development teams building their tools is frequently misaligned in ways that produce predictable problems. Schools bring deep subject matter knowledge, strong opinions about what pupils need, and almost no experience of how software development actually works. Developers bring technical capability and process knowledge, and often very little understanding of what a classroom actually feels like to be in. The result is a collaboration that tends to go wrong at the handover points. Schools specify requirements in terms of educational outcomes. Developers translate those into features. Neither side spends enough time on the emotional experience of the person who will actually use the product, because that experience is not easily expressible as a requirement or a feature. #### The Risk of Building Everything at Once We see another consistent failure mode in educational app projects that resist iterative development in favour of launching a complete product. The logic feels sensible to a school: we need the whole thing to be useful, so build the whole thing. But a product that tries to launch all at once accumulates complexity, pushes back its release date, and often never launches at all. The alternative, building a minimal version that is genuinely useful, testing it in real classrooms, and iterating based on what teachers and pupils actually do with it, produces better products and reduces the risk of the whole project stalling before it reaches anyone. Agree on one thing the app must do well before the first term ends. Ship that. Everything else is the roadmap, not the product. ## The Role of Teachers in Successful App Adoption Teachers are gatekeepers, advocates, and in many cases the deciding factor in whether an app becomes embedded in practice or fades out after the initial rollout. An [app that works beautifully in isolation](https://weareaffective.com/learning-centre/why-do-some-apps-feel-like-they-were-made-just-for-you) but creates additional work for the teacher will be quietly set aside, and no amount of pupil engagement will prevent that. This means teacher experience has to be a primary design concern, not something addressed in a separate admin dashboard bolted on at the end. The teacher needs to be able to understand what the product is telling them, act on it quickly, and hand it to a class without a lengthy explanation. If setting up a session takes more than two minutes, many teachers will stop doing it. #### Trust as a Design Variable Teachers also need to trust the product before they will advocate for it. Trust in a digital tool is built through consistency, transparency, and accuracy. An app that produces results which do not match what a teacher observes in the classroom will lose credibility fast. When a product tells a teacher that a pupil is performing well in an area where the teacher knows they are struggling, the product stops being a useful source of information and starts being something to work around. Building teacher trust means designing for teacher scrutiny. The product should show its reasoning, make its outputs interpretable, and never present data in a way that contradicts obvious classroom reality without explanation. ## What Successful Educational App Adoption Looks Like in Practice Successful adoption has some consistent features across the educational apps that actually get used. The product fits into an existing routine rather than replacing it. It produces outputs that are immediately actionable rather than requiring interpretation. It reduces something the teacher was already doing rather than adding a new obligation. On the emotional side, successful educational apps tend to make progress visible to pupils in ways that feel earned rather than automatic. A review of 20 articles on emotional design in multimedia learning, published between 2016 and 2021, found a clear positive impact of emotional design on learning outcomes ([Rodrigues and Silva, 2022](https://link.springer.com/article/10.1007/s10639-024-12823-8#ref-CR70)). The feeling of progress, and the emotional experience of being capable, matters alongside the actual measurement of performance. #### What Adoption Requires from the Design The design decisions that support adoption include: - [Onboarding that takes less than five minutes](https://weareaffective.com/learning-centre/what-makes-app-tutorial-content-that-people-actually-want-to-watch) and produces something useful immediately - Feedback that is specific enough to act on, not just a score - Visual progress that the pupil controls the meaning of, not just a percentage bar - A teacher view that surfaces the three most relevant things, not everything at once - Consistent behaviour across devices and connection speeds None of these are technically complex. They are design decisions, and they require someone to have thought carefully about the moment of use before the moment of development. ## Conclusion Educational apps occupy a genuinely important position in schools now, and the ambition behind them is rarely the problem. The problem is the distance between that ambition and the emotional reality of the people who open the product every day: a tired pupil on a Monday morning, a teacher with seventeen other things to manage, a school that bought a licence and now needs the tool to deliver. Closing that distance is a design problem. It requires understanding what state users actually arrive in, building for those states rather than ideal ones, and treating the emotional experience of the product as a primary concern from the very beginning, not something to address after the features are built. When emotional design is bolted on at the end, it shows. The product functions but does not connect, and connection is what determines whether a pupil opens it again tomorrow. The schools and developers who get this right tend to share one habit: they spend time in the actual moment of use before they make decisions about the design. They watch what teachers do with two minutes to spare and what pupils do when they are confused and no one is watching. That observation changes what gets built, and what gets built changes whether the product works. If you are building or commissioning an educational app and want to think through the emotional and behavioural layer of the design, [let's talk about your product](https://weareaffective.com/get-started). ## Frequently Asked Questions What types of apps are schools currently using in the classroom? Schools use a wide range of apps, from administrative tools such as registration systems and parent communication platforms, to curriculum-focused learning tools like reading programmes, maths practice apps, and science simulations. Some schools also use apps specifically designed to support pupils with additional needs, offering features like text-to-speech and visual timetables. How do teachers typically integrate apps into their lessons? Apps tend to occupy a few distinct roles within lessons, including warm-up activities, consolidation tasks, and independent work tools used when a teacher is focused on a smaller group. Increasingly, some schools also use apps as the primary mode of delivery for certain subjects, as well as assessment instruments that feed data back into lesson planning. Are educational apps actually effective, or are they just widely used? Widespread use and genuine effectiveness are not the same thing. Many apps deployed in schools are functional in a narrow sense, they load and store data, but they often fail to meaningfully engage pupils or reduce teacher workload in practice. What is the main design problem with educational apps? The core issue is that most educational apps are built around what they are supposed to do, rather than how users actually feel when they open them. The emotional states of pupils and teachers are rarely considered during the design process, which creates a significant gap between the app's intended purpose and its real-world impact. How quickly has app-supported learning become standard in schools? The shift has been remarkably fast, with app-supported learning moving from a novelty to an expectation within roughly a decade. Teachers, pupils, and parents now broadly assume that technology will play some role in how learning takes place. What goals are schools hoping to achieve by using apps? Schools are primarily hoping to personalise learning, provide pupils with immediate feedback, and reduce the burden of repetitive marking on teachers. The technology makes these outcomes possible in principle, though whether any individual app actually delivers them is a separate question. Why do curriculum goals not always translate well into app-based learning? Curriculum goals are written under ideal conditions, assuming that attention, motivation, and sufficient teaching time are all reliably present. Real classrooms rarely operate under those conditions, which means apps designed around curriculum goals alone often struggle to function as intended in practice. What would better-designed educational apps look like? Better-designed educational apps would account for the behavioural and emotional realities of the people using them, rather than focusing purely on functional delivery. This means designing for the actual experience of a pupil or teacher opening the app, not just for what the app is meant to achieve on paper. ## Related Articles [![Should My App Look the Same on Every Screen?](https://weareaffective.com/hubfs/learning-centre-images/should-my-app-look-the-same-on-every-screen.webp)](https://weareaffective.com/learning-centre/should-my-app-look-the-same-on-every-screen) ### [Should My App Look the Same on Every Screen?](https://weareaffective.com/learning-centre/should-my-app-look-the-same-on-every-screen) A mobile gaming studio launches their new puzzle game with identical interfaces across every... by [Simon Lee](https://weareaffective.com/learning-centre/author/simon-lee) [![Can I Manage App Customer Support by Myself or Do I Need a Team?](https://weareaffective.com/hubfs/learning-centre-images/can-i-manage-app-customer-support-by-myself-or-do-i-need-a-team.webp)](https://weareaffective.com/learning-centre/can-i-manage-app-customer-support-by-myself-or-do-i-need-a-team) ### [Can I Manage App Customer Support by Myself or Do I Need a Team?](https://weareaffective.com/learning-centre/can-i-manage-app-customer-support-by-myself-or-do-i-need-a-team) Running app customer support on your own feels manageable right up until it doesn't. In the early... by [Simon Lee](https://weareaffective.com/learning-centre/author/simon-lee) [![Logistics App Success Stories Learning From the Companies That Got It Right](https://weareaffective.com/hubfs/learning-centre-images/logistics-app-success-stories-learning-from-the-companies-that-got-it-right.webp)](https://weareaffective.com/learning-centre/logistics-app-success-stories-learning-from-the-companies-that-got-it-right) ### [Logistics App Success Stories Learning From the Companies That Got It Right](https://weareaffective.com/learning-centre/logistics-app-success-stories-learning-from-the-companies-that-got-it-right) The logistics app that works in the real world looks very different from the logistics app that... by [Simon Lee](https://weareaffective.com/learning-centre/author/simon-lee) [![We Are Affective](https://weareaffective.com/hubfs/we_are_affective_logo_mark.svg)](https://weareaffective.com) 20-22 Wenlock Road London, N1 7GU United Kingdom +44 20 4572 8062 [hello@weareaffective.com](mailto:hello@weareaffective.com) Services [App planning & strategy](https://weareaffective.com/app-planning-strategy) [App design](https://weareaffective.com/app-design-agency) [App UX design](https://weareaffective.com/app-ux-design) [App UI design](https://weareaffective.com/app-ui-design) [App technical architecture](https://weareaffective.com/app-architecture) [Existing app audits](https://weareaffective.com/app-audit) Legal [Privacy policy](https://app.termly.io/policy-viewer/policy.html?policyUUID=b8fa9921-7518-4fb5-8ddd-9dc7f5977ed2) [Terms](https://app.termly.io/policy-viewer/policy.html?policyUUID=8b6a6ad5-91bd-4176-a5f7-6d36b0398f70) Case studies [TravAI](https://weareaffective.com/case-studies/travai) [Meditech](https://weareaffective.com/case-studies/harley) [WorkingWeight](https://weareaffective.com/case-studies/workingweight) [SkinSync](https://weareaffective.com/case-studies/skinsync) [Three Lochs](https://weareaffective.com/case-studies/three-lochs) [Drift](https://weareaffective.com/case-studies/drift) About us [Our Story](https://weareaffective.com/about) [How We Work](https://weareaffective.com/how-we-work) Guides [Creating an app](https://weareaffective.com/how-to-create-an-app) [Building an MVP](https://weareaffective.com/building-an-mvp) [Cost and budgeting](https://weareaffective.com/app-development-cost) [App technology](https://weareaffective.com/app-development) [Planning and strategy](https://weareaffective.com/app-planning-strategy) [User research](https://weareaffective.com/app-user-research) [Onboarding design](https://weareaffective.com/app-onboarding-design) [User psychology](https://weareaffective.com/user-psychology-app-design) [Launch and growth](https://weareaffective.com/app-launch-growth) Copyright © 2026, weareaffective.com. All rights reserved.