Build the App,
Not the Adapter
Why AI should create purpose-built tools
instead of learning to drive PowerPoint
2026 · A presentation that practices what it preaches
The Current Approach
How we teach AI to make presentations today:
- 🔧 Learn PowerPoint's COM API and OOXML format
- 🔧 Learn Google Slides' REST API and OAuth flow
- 🔧 Learn Keynote's AppleScript interface
- 🔧 Then Canva, Prezi, Figma, Pitch…
Each framework is a new language to master.
Each update is a new way to break.
The Abstraction Tax
Every framework demands AI learn:
- 📦 A proprietary file format (OOXML, Protobuf, JSON blobs…)
- 🔌 A unique API surface — hundreds of endpoints
- 🧩 A plugin and extension ecosystem
- 🔄 Version-specific quirks and breaking changes
- 📚 Thousands of pages of documentation — per tool
More effort adapting to the tool than creating value.
What Do We Actually Need?
Strip it down to first principles. A presentation needs to:
- ✓ Display content on a screen
- ✓ Navigate between pages
- ✓ Support speaker notes
- ✓ Export to PDF
- ✓ Work offline
That's it. That's the whole requirements list.
What if AI just…
built the app?
HTML → content & structure
CSS → styling & animation
JavaScript → interaction & logic
Browser → the universal runtime
One file. Zero dependencies. Infinite flexibility.
Zero Dependencies
- 🚫 No install, no license, no subscription
- 💻 Works on every OS — if it has a browser, it works
- ✈️ Works offline — it's just a file on your disk
- 🏛️ Will still work in 20 years — HTML is eternal
- 📦 This entire presentation: < 30 KB
Compare: PowerPoint requires a 4 GB install and $160/year.
Total Control
❌ Framework-driven
- "Sorry, the template doesn't support that layout"
- "Animations are limited to these 12 presets"
- "Custom fonts require a plugin"
- "You can't nest that object there"
✓ Purpose-built
- Every pixel is intentional
- Every animation is custom
- Every interaction is designed for this specific need
- The only limit is the web platform
The Web Platform IS the Framework
Need something? Just add it.
- 📊 Need a chart? →
<canvas> or <svg>
- ❓ Need a quiz? → 20 lines of JavaScript
- 🎮 Need 3D? → WebGL, right in the browser
- 📡 Need live data? →
fetch() API
- ⏱️ Need a timer? →
setInterval()
- 🎵 Need audio? →
<audio> element
Try embedding a live API call in a PowerPoint slide.
But What About…?
- "Collaboration?" → Git + any text editor. Better version control than Google Slides.
- "Non-technical users?" → AI generates the file for them. That's the whole point.
- "Brand templates?" → CSS custom properties. Swap one variable block.
- "Editing in place?" → That's just another app to build.
- "Existing content?" → AI can convert formats too.
None of these are blockers. They're all solvable — and most are already easier than the PowerPoint equivalents.
Stop adapting AI to tools.
Adapt tools to the task.
This presentation is the proof.
Single HTML file. Built by AI. Every feature purpose-built.
Press Ctrl+P to export this to PDF right now.
The future isn't better PowerPoint plugins — it's no PowerPoint at all.