PlayPosit, now part of WeVideo, wraps a video in a lesson it calls a bulb: multiple choice, free response, fill in the blank, polls, reflective pauses, hotspots and overlays, delivered into Canvas and other LMS platforms over LTI with grades passing back.
Annoto covers those question types and adds the parts a question layer leaves out. Students answer each other on the timeline, submit and review video work, keep notes with AI recaps, and generate attention and comprehension data per learner. Annoto also hosts and streams the video itself, or overlays the platform you already run.
WeVideo acquired PlayPosit in 2022, pairing a video creation and editing product with an interactive question layer. The combination suits teams whose main problem is producing video and checking that someone watched it. Institutions whose main problem is teaching with video they already have tend to need something wider.
It builds a structured lesson around a video. An instructor places questions at chosen points, mixes in hotspots and media overlays, sets multi-versioned questions, and posts the result as an LMS assignment that grades itself. Question variety is genuinely broad, and the Canvas integration is mature.
Conversation and evidence. Discussion threads anchor to the exact second, so a cohort's confusion clusters visibly around particular moments rather than arriving as separate answers. Peer review and video assignments handle student-produced footage. Notes with AI session recaps give learners something to revise from. And the analytics report attention and comprehension across the video, not only scores on the questions you happened to place.
No. Annoto overlays the player your institution already uses, including Panopto, Kaltura, YouTube and Vimeo, so an existing lecture library becomes interactive in place. It also hosts and streams natively, which covers departments with no video platform of their own.
This is the honest limit of the comparison. WeVideo is a video creation and editing product, and Annoto is not. If your teams need timeline editing, stock media and production workflows, that is a separate requirement and worth pricing separately. Annoto starts once the video exists.
Two routes. An LMS admin registers it as an LTI 1.1 or 1.3 tool in Canvas, Moodle, Blackboard or Brightspace, and sign-on, rosters and grades run through the standard. On a portal, catalogue or homegrown platform, one script tag and a client ID attach the layer through the JavaScript SDK, with a REST API and webhooks behind it.
If the requirement is producing video and quizzing it, a creation product with a question layer fits. If the requirement is running video-heavy courses where students discuss, submit, review and are measured, compare on discussion, peer assessment and analytics, because those are where the two diverge.
A question layer produces one kind of record: whether a learner answered correctly at the point you interrupted them. A cohort working inside Annoto produces several at once. Threads accumulate under the moments that actually cause trouble, so a term of confusion becomes legible as a map of the video rather than a list of wrong answers. Notes and AI recaps sit alongside those threads as each learner's own revision trail. Peer review makes students the readers of one another's work, which is where reasoning gets exposed. And the reporting runs per learner and per second, showing who stalled, who rewatched and who never reached the final ten minutes, so a course team can intervene mid-term instead of diagnosing after the exam. The full engagement layer is the unit, not the quiz.
Institutions rarely migrate the video itself, because with Annoto the video does not move. What needs planning is the interactive layer built on top of it. Bulbs and their embedded questions are proprietary and do not import, so questions are re-authored, though Lumo AI drafts a graded set from the video's own transcript across Bloom's taxonomy, which turns re-authoring from typing into editing. Treat the LMS side deliberately: new LTI placements and fresh gradebook columns for the courses you move, plus a decision on whether historic scores stay in the old tool or are exported before it is retired. Most teams move at a term boundary, run both layers on separate sections for one term, and keep the accessibility and privacy review on the same cycle they already use for LTI tools.
A question layer is genuinely sufficient in several cases, and pretending otherwise wastes budget. Compliance modules, onboarding, procedural refreshers, anything where the requirement is that a named person watched and answered correctly: a bulb does that cleanly. The calculation changes when the learning is argumentative or performed. Seminars, clinical reasoning, language production, design critique and case-method teaching all depend on what students say to each other and what they produce, not on a score at an interruption. Scale changes it too, because at three hundred students an instructor needs to know which minute lost the room, and item statistics cannot say. And programme-level questions, such as whether a cohort improves across a sequence of courses, need a record that spans videos rather than one lesson at a time.
Both put questions on a timeline. Only one is built around the cohort.
PlayPosit keeps its checkmarks on questions. The difference shows up around them.
Compared against each vendor's published documentation, August 2026. Both products ship often, so confirm the current detail with each vendor before you decide.
The fairest test is one video, one cohort, two tools, one term.
An LMS admin registers Annoto over LTI 1.1 or 1.3. On a portal or custom site, one script tag and a client ID.
Annoto attaches to the existing player, so there is no rebuild and no second copy of the video to maintain.
Question scores, yes, but also how much students said to each other and which minutes they rewatched.
Side-by-sides with the platforms and tools institutions ask about most.
Twenty minutes on your content, in your LMS. Bring a video students already find hard.
Book A Demo