Most edtech teams make the same mistake early: they try to support every LMS at once. Canvas, Moodle, Blackboard, Brightspace, Schoology — the list grows until the integration work buries the product work. Six months later, nothing works well anywhere.
You don't need to support every LMS. You need to support the right two, in the right order.
Start with your customer, not the LMS market share chart
The most common mistake is picking LMS platforms based on overall market share instead of where your actual customers are.
Canvas has the largest share in US higher education. Moodle dominates internationally and in K-12 outside the US. Brightspace is strong in Canadian K-12 and corporate learning. Blackboard is common in large US universities.
None of that matters if your first 10 customers are all on Moodle.
Before you write a line of integration code, answer two questions: who are the first schools or institutions you're selling to, and what LMS are they on? One conversation with a potential customer answers this faster than any market research report.
The decision framework
If you're targeting US higher education — start with Canvas. It has the largest share in that segment and its LTI implementation is clean and well-documented. Add Blackboard second if your target customers are large universities.
If you're targeting international schools or K-12 outside the US — start with Moodle. It's open source, widely deployed globally, and has an active developer community. The setup is more involved than Canvas but the audience is large.
If you're targeting corporate learning or Canadian institutions — start with Brightspace. It's the platform of choice in those segments and D2L has strong LTI 1.3 support.
If you're targeting US K-12 — this is the hardest segment. Canvas and Schoology split most of the market, but Google Classroom has roughly 24% share and doesn't support LTI at all. You'll need both an LTI integration and a Google Classroom API integration to cover this segment properly.
The platforms you can defer
Blackboard and Schoology are safe to defer unless a specific customer requires them. Both support LTI 1.3, so adding them later is straightforward once your core integration is solid.
Open edX is worth considering if you're targeting MOOCs or large-scale online courses — but it's a niche segment and the integration is more involved than standard LMS platforms.
One rule that saves months
Build your LTI integration cleanly against the spec, not against one LMS's quirks. Every LMS implements LTI slightly differently — Canvas handles deep linking differently from Moodle, Blackboard has specific behaviors around grade passback. If you build for one LMS's implementation and assume it's universal, you'll rebuild every time you add a new platform.
Test against the 1EdTech reference implementation first. Then test against each LMS separately. Treat each platform's quirks as configuration, not code changes.
FAQ
How long does adding a new LMS integration take?
If your LTI integration is built cleanly against the spec, adding a new LMS is mostly configuration and testing — typically 2 to 4 weeks. If your integration has platform-specific assumptions baked in, expect 6 to 10 weeks of rework per platform.
Should we support LTI 1.1 for older LMS deployments?
No. Build on LTI 1.3 only. LTI 1.1 is deprecated and major platforms are dropping support for new integrations. If a customer is on an older LMS version that only supports 1.1, that's a conversation about their upgrade timeline, not yours.
What if our first customer is on a platform we haven't supported yet?
Build it. One real customer is worth more than theoretical market share. Just build it cleanly so the second and third platforms don't require starting over.
Top comments (0)