Episode Details
Back to Episodes
Power Apps Generative Pages vs Canvas Apps: when to stop pixel‑building and let AI design your app
Season 1
Published 5 months, 3 weeks ago
Description
Canvas Apps vs. Generative Pages Power Apps: in this episode of M365.fm, Mirko Peters explains why clinging to classic Canvas Apps has become self‑inflicted pain—and how Generative Pages with the new App Agent fundamentally change how you should design Power Apps. He starts with the “Canvas lie”: the promise of pixel‑perfect freedom that turned into pixel purgatory, where every layout tweak, theme change, or new filter means spelunking through nested containers, brittle Power FX formulas, and UI dependencies that collapse like Jenga pieces.
Mirko recounts how enterprises quietly normalized this suffering. Teams celebrated beautifully aligned screens while sprint boards filled with chores like “fix header layout,” “refactor gallery filter,” and “make it responsive,” pushing real work—data modeling, security, performance, governance—into the background. Canvas Apps became hobby farms for perfectionists: handcrafted, visually impressive, and terrifying to modify once they hit production. Most organizations never noticed the bleed because it was disguised as craftsmanship rather than technical debt.
He then introduces Generative Pages as the grown‑up alternative: Dataverse‑aware, schema‑driven, and powered by AI that understands structure instead of just drawing rectangles. Instead of dragging controls, you describe intent: “Create an ideas tracker with categories, status, and charts,” attach a sample or sketch, and the system generates a fully functional, responsive page atop React components wired directly to Dataverse. Sorting, filtering, forms, and security come from your data model, not from hand‑written formulas; accessibility and theming are built in rather than bolted on.
The episode dives into the new architecture behind Generative Pages. Mirko explains how React‑based rendering brings real web‑app behavior, how CRUD operations and lookups are pre‑wired from your Dataverse schema, and how responsive layouts, dark mode, and accessibility are handled by design tokens instead of fragile width expressions. He also highlights the App Agent: a conversational copilot inside Power Apps that lets you say “replace search with dropdown filters,” “add a date range,” or “insert a chart of ideas by category” and see the app refactored automatically—with undo and history so experimentation is finally safe.
Throughout the episode, you get concrete comparisons: how long a typical Canvas page with multiple galleries, filters, and themes takes to build versus a Generative Page; what happens when requirements change mid‑project; and how Dataverse‑first design shifts your focus from pixel pushing to schema, relationships, and governance. Mirko argues that the real upgrade is not prettier UI but a different mental model: you stop being a layout technician and become an architect who describes outcomes while AI and the platform handle the assembly.
WHAT YOU WILL LEARN
Mirko recounts how enterprises quietly normalized this suffering. Teams celebrated beautifully aligned screens while sprint boards filled with chores like “fix header layout,” “refactor gallery filter,” and “make it responsive,” pushing real work—data modeling, security, performance, governance—into the background. Canvas Apps became hobby farms for perfectionists: handcrafted, visually impressive, and terrifying to modify once they hit production. Most organizations never noticed the bleed because it was disguised as craftsmanship rather than technical debt.
He then introduces Generative Pages as the grown‑up alternative: Dataverse‑aware, schema‑driven, and powered by AI that understands structure instead of just drawing rectangles. Instead of dragging controls, you describe intent: “Create an ideas tracker with categories, status, and charts,” attach a sample or sketch, and the system generates a fully functional, responsive page atop React components wired directly to Dataverse. Sorting, filtering, forms, and security come from your data model, not from hand‑written formulas; accessibility and theming are built in rather than bolted on.
The episode dives into the new architecture behind Generative Pages. Mirko explains how React‑based rendering brings real web‑app behavior, how CRUD operations and lookups are pre‑wired from your Dataverse schema, and how responsive layouts, dark mode, and accessibility are handled by design tokens instead of fragile width expressions. He also highlights the App Agent: a conversational copilot inside Power Apps that lets you say “replace search with dropdown filters,” “add a date range,” or “insert a chart of ideas by category” and see the app refactored automatically—with undo and history so experimentation is finally safe.
Throughout the episode, you get concrete comparisons: how long a typical Canvas page with multiple galleries, filters, and themes takes to build versus a Generative Page; what happens when requirements change mid‑project; and how Dataverse‑first design shifts your focus from pixel pushing to schema, relationships, and governance. Mirko argues that the real upgrade is not prettier UI but a different mental model: you stop being a layout technician and become an architect who describes outcomes while AI and the platform handle the assembly.
WHAT YOU WILL LEARN
- Why classic Canvas Apps create fragile, unscalable UI debt in enterprise projects.
- How Generative Pages use Dataverse, React, and AI to generate responsive, schema‑aware Power Apps from intent.
- How the App Agent refactors apps via natural language—adding filters, charts, and layout changes safely.
- How shifting from manual layout to model‑driven, AI‑assisted design changes your sprint and governance practices.
Listen Now
Love PodBriefly?
If you like Podbriefly.com, please consider donating to support the ongoing development.
Support Us