Every native UI toolkit before Flutter made the same bet: hand drawing over to the operating system. Android apps compose `View` objects that Android's own renderer draws; iOS apps compose `UIView` objects that UIKit draws. That bet has a cost nobody notices until they try to ship one UI on both platforms and watch a button render with subtly different padding, a different tap-highlight animation, and a scrollbar that behaves differently under a fast fling — three small inconsistencies that compound into an app that never quite feels like it was built by one team.
Flutter refuses that bet. A Flutter app does not ask Android or iOS to draw a single button, list, or transition. It asks the operating system for one thing only — a blank canvas, a rectangle of pixels it is allowed to own — and then draws every widget itself, pixel by pixel, using its own graphics engine. The practical result is that a Flutter button looks and animates identically on a five-year-old Android phone and a brand-new iPhone, because the same code drew both of them. The cost is that Flutter has to reinvent everything the platform used to hand you for free: text shaping, accessibility semantics, even the blinking text cursor.
Analogy🏏Cricket
🏏 Think of it like cricket: When India tour Australia, England and South Africa in the same season, a batter like Virat Kohli does not relearn his technique for each ground's footage or lighting rig. He brings one technique — his own grip, his own trigger movement, his own judgment of length — and applies it identically whether he is walking out at the WACA or Eden Gardens. He does not borrow the host ground's idea of a "correct" cover drive. Just as Kohli carries his own technique onto every pitch rather than adapting to each ground's local coaching style, Flutter carries its own rendering engine onto every device rather than adapting to each platform's native widget style. Just as the tradeoff for Kohli is that he must train that technique himself rather than relying on a local academy to hand it to him, the tradeoff for Flutter is that it must draw every pixel itself rather than relying on the platform to hand it a native button. This reveals why Flutter draws its own pixels: consistency across wildly different grounds is only possible when you stop depending on each ground's own equipment and bring your own.
🏏 Showing the Cricket analogy — a Cricket version isn’t available for this concept yet.