When evaluating new technologies, I find details of what something can’t do even more useful than what it can, even if such lists can seem horribly negative.
Welcome to doom and gloom.
I’ve tried to avoid matters of opinion and things people don’t like (such as a lack of a markup language), just hard facts about what Flutter can’t currently do, and when it will hopefully be able to.
Note: article fully updated as of August 2020 for Flutter 1.20.
Directly Calling Native APIs from Dart
Flutter can interact with native platform APIs, but not directly. This differs from Xamarin and NativeScript where you can use…
There’s been plenty of comparing Flutter with other cross-platform mobile frameworks. But the key difference is often overlooked or downplayed.
Flutter owns every pixel on the screen.
Cross-platform frameworks such as React Native and Xamarin.Forms which use native Android and iOS interface elements sound like a great idea, on paper:
“ Write once and run anywhere! Fully native interfaces! Apps feel like they fit right in! Screens magically adapt to platform paradigms!”
But these frameworks aren’t totally in control, they’re having to rely on the OS to draw the interface. …
Tom Gilder
Slightly obsessed with Flutter. I make the best apps around with lovely people at Codemate in Helsinki — codemate.com
