Uploaded August 2026 | Updated September 2026, 2 weeks ago
This video breaks down the native-first hybrid architecture of yoAnime Studio and shows how we decouple animation logic from PowerPoint's legacy timing and host constraints to create a host-independent, mathematically deterministic 2D motion runtime.
Instead of treating PowerPoint as the authority for animation behavior, yoAnime moves semantic and mathematical authority into its native runtime. PowerPoint becomes the document/COM host and rendering target, while the runtime controls animation evaluation, interpolation, trajectories, identity, and playback state.
⏱️ Timestamps & Key Chapters
0:00 — Runtime Authority: Why PowerPoint Is Not the Animation Authority
Why yoAnime separates animation semantics from PowerPoint's native timing model and treats PowerPoint primarily as a COM host and rendering substrate.
1:45 — The 4-Layer Hybrid Architecture
How four isolated layers work together without collapsing responsibilities:
VSTO / COM Layer (C#)
PowerPoint event subscriptions, document integration, serialization, and final COM shape mutations.
Shared.Core (C#)
A pure, portable C# computation layer with no UI or COM dependencies, responsible for motion mathematics, curve evaluation, and trajectory calculations.
WPF Layer (Companion App)
The spatial authority for desktop interaction, transparent overlays, coordinate management, and slide-to-screen projection.
WebView2 Layer (HTML5 / JavaScript)
The interaction and authoring surface for cinematic timelines and editing tools, sending intent into the runtime rather than owning canonical geometry.
4:15 — The Deterministic Frame Evaluation Pipeline
A walkthrough of the runtime evaluation stages designed for deterministic playback, repeatable seeking, and stable frame calculation without state-dependent drift.
6:30 — Coordinate Spaces & the Projection Law
How yoAnime maintains spatial consistency through a strict one-way projection pipeline from absolute Slide Space to screen DIPs and local SVG coordinates.
7:15 — Stable Runtime Identity: runtimeNodeId
How persistent runtime identity avoids relying on unstable PowerPoint shape IDs, allowing authored timelines to survive operations such as duplication, slide edits, and copy/paste scenarios.
🧩 Build on the yoAnime Platform
The public yoAnime SDK lets developers create JavaScript/HTML extensions for PowerPoint motion, timelines, physics, procedural animation, interactive tools, and live web experiences.
Extensions communicate through the SDK rather than receiving raw PowerPoint COM objects or Office internals. The native yoAnime runtime validates and coordinates those requests before applying changes to PowerPoint.
Explore the open-source TypeScript SDK, API specifications, developer documentation, sample extensions, and starter templates:
👉 GitHub Repository: github.com/theteacherpoint1977/yoanime-sdk
👍 Like • 💬 Comment • 🔗 Share • 🔔 Subscribe
#PowerPoint #Animation #CSharp #WPF #WebView2 #VSTO #COM #TypeScript #JavaScript #SoftwareArchitecture
This video breaks down the native-first hybrid architecture of yoAnime Studio and shows how we decouple animation logic from PowerPoint's legacy timing and host constraints to create a host-independent, mathematically deterministic 2D motion runtime.
Instead of treating PowerPoint as the authority for animation behavior, yoAnime moves semantic and mathematical authority into its native runtime. PowerPoint becomes the document/COM host and rendering target, while the runtime controls animation evaluation, interpolation, trajectories, identity, and playback state.
⏱️ Timestamps & Key Chapters
0:00 — Runtime Authority: Why PowerPoint Is Not the Animation Authority
Why yoAnime separates animation semantics from PowerPoint's native timing model and treats PowerPoint primarily as a COM host and rendering substrate.
1:45 — The 4-Layer Hybrid Architecture
How four isolated layers work together without collapsing responsibilities:
VSTO / COM Layer (C#)
PowerPoint event subscriptions, document integration, serialization, and final COM shape mutations.
Shared.Core (C#)
A pure, portable C# computation layer with no UI or COM dependencies, responsible for motion mathematics, curve evaluation, and trajectory calculations.
WPF Layer (Companion App)
The spatial authority for desktop interaction, transparent overlays, coordinate management, and slide-to-screen projection.
WebView2 Layer (HTML5 / JavaScript)
The interaction and authoring surface for cinematic timelines and editing tools, sending intent into the runtime rather than owning canonical geometry.
4:15 — The Deterministic Frame Evaluation Pipeline
A walkthrough of the runtime evaluation stages designed for deterministic playback, repeatable seeking, and stable frame calculation without state-dependent drift.
6:30 — Coordinate Spaces & the Projection Law
How yoAnime maintains spatial consistency through a strict one-way projection pipeline from absolute Slide Space to screen DIPs and local SVG coordinates.
7:15 — Stable Runtime Identity: runtimeNodeId
How persistent runtime identity avoids relying on unstable PowerPoint shape IDs, allowing authored timelines to survive operations such as duplication, slide edits, and copy/paste scenarios.
🧩 Build on the yoAnime Platform
The public yoAnime SDK lets developers create JavaScript/HTML extensions for PowerPoint motion, timelines, physics, procedural animation, interactive tools, and live web experiences.
Extensions communicate through the SDK rather than receiving raw PowerPoint COM objects or Office internals. The native yoAnime runtime validates and coordinates those requests before applying changes to PowerPoint.
Explore the open-source TypeScript SDK, API specifications, developer documentation, sample extensions, and starter templates:
👉 GitHub Repository: github.com/theteacherpoint1977/yoanime-sdk
👍 Like • 💬 Comment • 🔗 Share • 🔔 Subscribe
#PowerPoint #Animation #CSharp #WPF #WebView2 #VSTO #COM #TypeScript #JavaScript #SoftwareArchitecture
