Subject(opens in a new tab) was built with intention from the very beginning. The team set out to create a rich learning experience for students that felt engaging, seamless, and fully in-platform. Assignments had to happen inside the product, not through downloads or external tools. As the platform grew, Subject looked for a document layer that felt native and could scale with its vision. That’s when the company turned to Nutrient.

The challenge: A new approach to online learning

Subject was founded during the pandemic to rethink what digital education could look like for middle and high school students. “We were very intentional about building a rich experience for students,” said the former chief product officer at Subject.

Rather than replicating traditional textbooks online, the team focused on cinematic, video-led courses designed to keep students engaged.

Delivering that experience introduced immediate challenges. Many digital learning models forced students to download documents or switch tools to complete assignments, in turn breaking continuity and adding friction. For Subject, that clashed with its instructional design philosophy and added unnecessary cognitive load on students.

Early attempts to use open source PDF rendering tools and basic PDF annotation libraries solved viewing needs, but not the dynamic drawing needed for scaffolded assignments. Building those capabilities internally would have drained engineering effort and added long-term maintenance debt — an unsustainable tradeoff as the curriculum expanded.

As Subject grew, the challenge became clearer: It needed a solution that could deliver rich, in-app document interaction across thousands of lessons without becoming another system its lean team had to constantly manage.

The solution: Dynamic assignments and no detours

Subject integrated Nutrient’s document SDKs to power interactive PDF experiences directly within its web application. Students can annotate documents, draw diagrams, highlight text, and complete assignments without ever leaving the platform.

Implementation was “super straightforward,” and Subject’s engineering team embedded Nutrient’s PDF annotation tools with minimal setup. Beyond SDK updates, the document layer required little ongoing attention.

Nutrient’s layered PDF data also enabled integration with Subject’s AI-powered grading tools, supporting automated and assisted assessments while preserving the richness of student work.

Across product, engineering, and instructional design teams, Nutrient quietly handled document complexity so Subject could stay focused on the students and improve the core learning experience.

The impact: Scaling up without slowing down

Before Nutrient, Subject faced uncertainty around how to deliver interactive assignments at scale without investing heavily in custom document infrastructure. After integration, document workflows became a stable foundation rather than a recurring concern.

Students now complete assignments entirely within the platform, reducing friction and keeping focus. Engineers concentrate on core platform innovation instead of debugging document logic.

As the platform scaled rapidly, including 5× student growth in consecutive spring semesters, the document layer continued to perform consistently. Even during high-stress moments, such as onboarding 50,000 students in a single day, document performance remained reliable.

After years of continuous use, Nutrient has remained consistent, invisible, and foundational to the experience.

Results by the numbers

A better class of online learning

With Nutrient, Subject scaled from early-stage startup to national growth without ever rebuilding its document foundation. The infrastructure stayed invisible. The experience stayed rich. And the team continues building one of today’s leading online learning platforms with the very same intentionality and clarity of purpose it started with.