Introducing Flutter

[MUSIC PLAYING] SPEAKER: Mobile users expect their apps to have beautiful designs, smooth animations, and great performance. To deliver on this, developers need to create new features faster than ever without compromising on quality or performance. That's why we built Flutter. Flutter is Google's mobile UI framework that provides a fast and expressive way for developers to build native apps on both iOS and Android. This is because apps and interfaces made with Flutter are built from a single codebase, compiled directly to native arm code, use the GPU, and can access platform APIs and services. Here are three ways that Flutter will help you on day one. Flutter is engineered for high developer velocity. Stateful hot reload allows you to change your code and see it come to life in less than a second, without losing the state of the app. Flutter also ships with a rich set of customizable widgets, all built from our modern reactive framework. Plus, Flutter integrates with popular development tools, which means you can get started quickly with the editor or IDE you already know and love. Flutter moves the widgets, rendering, animation, and gestures into the framework, to give you complete control over every pixel on the screen. This means you have flexibility to build custom designs. Flutter apps follow platform conventions and interface details, such as scrolling, navigation, icons, fonts, and more. This is why apps built with Flutter are featured on both the App Store and Google Play Store. Flutter is great for developers, both new and experienced in mobile. If you're new to mobile, Flutter gives you a fast, fun, and modern way to deliver native apps. If you're an experienced mobile developer, you can add Flutter to your existing workflows and tools to build new expressive UIs. Flutter is free and open source, and used by developers and organizations around the world, including enterprise, agencies, and startups. Visit flutter.io to get started today. We can't wait to see what you build.

Channel: Google Developers

Views: 2,190,081

Keywords: GDS: Yes, Flutter, Introducing Flutter, Flutter IO, Flutterio, UI Framework, mobile app SDK, app, interface, developers, Google, native, development, iOS, Android, UI, framework, Google mobile UI, build native apps, native apps IOS, native apps Android, widgets, flutter widgets, mobile developer, mobile app developer, app developer, native app developer, expressive UI, open source, google, google developers, Firebase, Firebase and Flutter, Material Design, android, ios

Id: fq4N0hgOWzU

Length: 1min 53sec (113 seconds)

Published: Fri Feb 23 2018

Reddit Comments

[u/joey_sandwich277]

Flutter has been available in alpha for a while, why the"introduction?"

[u/drabred]

I might get downvoted hard but as long as it is Alpha and has a little tracktion at all I'm not going to bother. Flutter might be as well dead in a year or so.

However, It does not mean that It can't go the complete opposite way. I'll be happily surprised then.

[u/Nexxado]

I encountered Flutter about a week ago, the concept looks really promising in my opinion.

For those who wants to understand what's exactly new about Flutter and what's the difference between Flutter and frameworks like React-Native, I recommend reading this article

Though note that Flutter is still in Alpha and some features don't work yet, such as inline maps & Instance state not being saved when app is killed by OS.

[u/VasiliyZukanov]

RANT WARNING!

Sorry Google, but could you please make up your mind?

DataBinding, Kotlin, Arch Components, numerous Android arch blueprints, Flutter... It would be great for both beginners and experienced devs if there would be just one single way to develop Android application recommended by Google.

And no, I'm not buying BS about "we just provide options; it's never bad to have options".

If the framework is good, then having multiple options is always bad. It is only when the framework sucks and developers need to wrestle with it that multiple options become useful. I might like to kick framework's ass with Arch Components (not really); that pretty girl would use Flutter; and this guy over there uses Jiu Jitsu style grabs with RxKotlinMVPVMFlutterBinding.

And here are the news: developing workarounds is community's responsibility. Your responsibility is to make the core platform better. It took you 9 YEARS to allow us to specify custom text font in XML, but, meanwhile, you developed Fragments, Loaders, DataBinding and a bunch of other controversial stuff.

Honestly, it was much better back in the days when, per Dianne Hackborn's statement, this was the official policy: "we often don't have a strong opinion or really an opinion at all". Less than two years later you managed to completely confuse EVERYBODY in the community about development practices, design and architecture.

Being new to Android development today is analysis paralysis hell - there are just too many options to choose from, each of which is not exactly simple by itself.

To me, a person familiar with "internal enterprise politics games" in general, it looks like there is just a competition going on between multiple teams at Google, each of which wants to promote its product, regardless of consumers' interests.

So, thanks for Flutter - yet another project that consumes community's resources and attention, without a clear roadmap and commitment, and without any reasonable justifications for its existence.

Maybe it should be added to this post that "praises" many Android features.

[u/mentaleur]

This sounds too good to be true but I'm definetly intersted, I started with android studio but my humble 4 gb ram can't keep up, never saw a heavier software

[u/shadowdude777]

I think you're looking for /r/mAndroidDev :)

[u/Keremeki13]

I might consider it if they support kotlin maybe.

[u/BOBIDDY]

How is Flutter different from something like Xamarin.Forms?

[u/paramsen]

Why are people downvoting this? I for one welcome projects like this. Makes it easier to develop agency fire-and-forget projects and PoCs.

I wonder how it compares to ReactNative in terms of performance, and I also wonder how the road map looks. Also; Why would I choose Flutter over ReactNative?