E-learning app development: a practical UK guide (2026)

In the UK, a first useful version of an e-learning app is a matter of several months rather than weeks, and it falls into our simple-to-mid-range bracket of £10,000 to £150,000, depending on how much of the learning experience you build yourself and how much you buy in. That covers courses, lessons, assessments, progress tracking and the reporting behind them. The hard part is rarely the video player. It is content authoring, progress data, accessibility and the reporting that whoever pays for the app actually wants to see.

We have built learning platforms, portals and training tools, and in our experience teams come to us when a spreadsheet or an off-the-shelf LMS has stopped bending to how they teach. This guide sets out what we have found matters, and where budgets tend to disappear.

Should you build at all?

Be honest about this before you spend anything. Moodle, Canvas, Thinkific and LearnWorlds already solve course delivery, payments and certificates. If your requirement is “sell courses online” and nothing more, a platform will beat a bespoke build on cost and time.

Building your own makes sense when at least one of these is true:

• Your teaching model does not fit a course-and-quiz structure: simulations, practical assessment, coaching workflows, apprenticeship evidence portfolios.
• The learning content is inseparable from your own data or systems: your compliance rules, your equipment, your product.
• You are selling the platform itself, in which case you are building a SaaS product with a learning module.
• Per-learner licence costs have become the largest line in your budget as you scale.

We have a companion piece on how to build an e-learning platform covering the platform side in more depth.

The parts of an e-learning app nobody budgets for

Most briefs we receive describe the learner app. That is usually the smallest of the four builds. A functioning e-learning product has four audiences, and three are usually missing from the first estimate.

Audience	What they need	Commonly forgotten
Learners	Courses, lessons, progress, offline access, certificates	Resuming exactly where they stopped, on a different device
Authors and tutors	Content creation, versioning, marking, feedback	A usable authoring tool, which in our experience is badly underestimated
Managers and buyers	Cohort progress, completion, compliance reporting	The reporting that justifies the purchase
Administrators	Users, roles, permissions, billing, integrations	Bulk enrolment and single sign-on

If you sell to employers rather than individuals, the manager dashboard is the product. Learners use the app; the training manager renews the contract on the strength of a completion report.

Core features worth building first

Keep the first release tight. These are the features we would argue for, roughly in this order.

Content delivery and structure

A course, module and lesson hierarchy with mixed media: video, text, images, downloadable resources. Decide early whether you support SCORM or xAPI packages. If you sell to corporate training departments, they will ask, and retrofitting xAPI later is genuinely painful.

Progress and state

Resume points, completion rules, streaks if they suit your audience. This sounds trivial and is not: progress must sync across devices, survive offline use and reconcile sensibly when the same learner works on a phone and a laptop within an hour.

Assessment

Quizzes, submitted work, marking, plus question banks and randomisation if there is any incentive to cheat. Timed and proctored assessment is a large separate project; do not slip it into version one by accident.

Offline access and reporting

In our experience, downloadable lessons matter more than founders expect at the outset, particularly for field workers, commuters and learners on constrained data. It shapes your whole data architecture, so decide before you build. For reporting, build a small honest set you can defend: completion rates, time spent, assessment outcomes, CSV exports.

Things that can wait: AI tutoring, gamification leagues, social feeds, live classes. Each is defensible in year two, once you know how the product is genuinely used.

Native, cross-platform or web?

Media-heavy learning apps expose the trade-offs clearly.

• Progressive web app. Cheapest path, one codebase, no store approval. Reasonable for desktop-first corporate learning. Offline video and background downloads remain awkward on iOS.
• Cross-platform (React Native or Flutter). Our usual recommendation for mobile-first learning products: one team, both stores, native download and notification behaviour. See our notes on cross-platform app development and mobile app development frameworks.
• Native iOS and Android. Justified when you need heavy on-device processing, AR or the tightest accessibility integration. It materially increases the mobile build cost, because you are funding two codebases rather than one.

Most products we scope end up as a web application for authors and administrators plus a cross-platform mobile app for learners, which avoids cramming an authoring tool into a phone screen. We build both sides, including the web application behind it.

Accessibility and data protection are not optional

If you sell to UK schools, colleges, universities or the public sector, accessibility is a procurement requirement. The Public Sector Bodies Accessibility Regulations 2018 require public sector websites and mobile apps to meet WCAG 2.1 level AA and publish an accessibility statement. Private providers are not directly covered, but the Equality Act 2010 duty to make reasonable adjustments still applies, and buyers increasingly ask for evidence.

Practically, that means captions and transcripts for video, proper heading structure, keyboard operation, sensible colour contrast, adjustable text size, and screen reader testing on real devices. Retrofitting is expensive; designing for it costs very little.

Learning apps also collect a great deal about individuals, including performance. Under UK GDPR you need a lawful basis, a retention policy and a clear position on where data lives. If you handle learners under 18, the ICO’s Age Appropriate Design Code applies and shapes defaults, profiling and data minimisation. Settle all of this during design, not during a procurement questionnaire.

What e-learning app development costs in the UK

UK agency rates sit around £75 to £150 per hour, and our published app development ranges are a reasonable guide:

Scope	Typical range	What that buys
Simple	£10,000 to £50,000	Learner app, courses, lessons, basic progress, one platform
Mid-range	£50,000 to £150,000	Plus authoring, roles, assessments, reporting, integrations
Complex	£150,000 to £1,000,000+	Multi-tenant, SSO, SCORM/xAPI, live sessions, accessibility conformance

The variables that move the number most are the authoring experience, offline behaviour, assessment integrity, integrations with existing HR or student systems, and the depth of reporting. Video hosting and transcoding is an ongoing cost rather than a build cost, and it scales with viewing hours rather than with users.

Budget separately for content: a polished app with thin content fails, whilst adequate software with excellent content generally does not. Plan for maintenance too. Our cost estimator will give you a starting range in a couple of minutes.

A sensible build sequence

1. Define the learning outcome, not the feature list. What must a learner be able to do afterwards, and how will you know?
2. Map the four audiences and write down what each one must be able to do on day one.
3. Prototype the authoring flow first. If content creation is painful, the product dies quietly. It is the step we see skipped most often.
4. Build a narrow, real slice: one complete course, start to finish, in front of real learners.
5. Test on the devices your learners own, including older Android handsets and poor connections.
6. Launch to a single cohort, then expand, guided by completion data rather than feature requests.

If you already have an AI-generated prototype that demonstrated the idea but will not survive real learners, that is a fixable position rather than a wasted one. Our vibe code rescue work exists for exactly that situation.

Frequently Asked Questions

How much does it cost to develop an e-learning app in the UK?

A focused e-learning app with courses, lessons and progress tracking typically costs between £10,000 and £50,000. Adding an authoring tool, assessments, role-based access and reporting moves it into the £50,000 to £150,000 range. Multi-tenant platforms with single sign-on, SCORM or xAPI support and formal accessibility conformance start around £150,000. UK agency rates generally run from £75 to £150 per hour. Our app development cost guide breaks down where the money actually goes across a build.

How long does e-learning app development take?

Expect several months rather than weeks to reach a first version that real learners can use, assuming clear requirements and prompt decisions. A single-platform learner app with a small feature set sits at the shorter end of that. A platform serving learners, authors, managers and administrators, with integrations into existing HR or student systems, takes materially longer before its first proper cohort, so treat the four-audience build as the schedule you are actually funding.

Should I build a native or cross-platform e-learning mobile app?

Cross-platform frameworks such as React Native and Flutter suit most e-learning products, because one team can serve iOS and Android with proper offline downloads and notifications. Choose native when you need heavy on-device media processing, augmented reality or the deepest accessibility integration, and accept a materially higher mobile build cost, since you are funding two codebases. A progressive web app works well when your learners are desktop-first.

Do I need SCORM or xAPI support?

You need it if you sell to corporate training departments, colleges or public sector buyers, because their existing learning management systems expect standards-compliant content and reporting. SCORM handles packaged course content; xAPI records richer statements about what a learner did, including offline and outside the app. If you sell directly to individual consumers, you can usually skip both. Retrofitting either is expensive, so decide before you build.

What accessibility standards must a UK e-learning app meet?

Public sector bodies must meet WCAG 2.1 level AA and publish an accessibility statement under the Public Sector Bodies Accessibility Regulations 2018. Private providers are not covered by those regulations directly, but the Equality Act 2010 duty to make reasonable adjustments applies, and most institutional buyers ask for evidence of conformance anyway. In practice: captions, transcripts, keyboard operation, contrast, adjustable text and real screen reader testing.

Should I use an existing platform instead of building?

Usually, yes, at first. If your requirement is selling structured courses online, Moodle, Thinkific or a similar platform will get you there faster and cheaper. Build your own when your teaching model does not fit a course-and-quiz structure, when the content is inseparable from your own systems or data, or when per-learner licence costs have become your largest cost as you grow.

Where to start

If you are weighing up an e-learning app, the most useful next step is a short conversation about your learners, your content and who signs the cheque. We are happy to say when an off-the-shelf platform would serve you better, because a project that should never have been built helps nobody.

You can see how we work, read about our app design approach, or get in touch with an outline of what you have in mind.