Your 25 MB Power Apps Screen Contains 430 Lines of Real Work
What actually takes up space inside a canvas app, measured byte by byte.
> ls ./series/canvas-app-internals
Eight posts mined from the control source files that ship inside every .msapp. Every figure measured, not estimated; every claim reproducible from a Methodology footer.
What ships inside the .msapp archive, measured from real exports — three apps, three years apart. The series walks from bytes-on-disk through migration changelogs, control generation history, sizing limits, and the SARIF report you already have but never opened.
Every claim in every post traces to a command in its Methodology section. Start with Post 1 if you want the headline numbers; jump to Post 5 or Post 6 if you have a broken layout to debug.
What actually takes up space inside a canvas app, measured byte by byte.
There is a machine-readable record of every property Microsoft added, removed, and renamed on the modern controls. It is sitting in your `.msapp` right now.
Two apps, three years apart, same control templates. Here is the diff.
What a Power Apps control actually is, read straight from its source.
And one of them explains why your container stops growing at a very specific number.
Every canvas control carries a tablet default, a phone default, and a web default. They disagree with each other by up to 3.7×.
Seven code comments in the control templates, and what each one tells you about the platform's actual roadmap.
Plus the 83 preview feature flags your app is carrying, and what they reveal about what is coming.