Skip to main content

Flutter plugin v21 now available -- Introducing the NEW Flutter Inspector

Flutter Inspector



We’re very excited to be able to announce the first version of the Flutter Inspector for IntelliJ and Android Studio! It will be featured in a talk at DartConf in LA (Wednesday, Jan. 24, 10am Pacific time) and will be live streamed on the DartConf website and on the Google Developers channel on Youtube. Be sure to watch it.



The inspector makes it much easier to understand why your application is rendering the way it does. It allows you to: 
  • View the UI structure of your app as a tree of widgets. 
  • Select a point on your device or simulator and find the corresponding Widget that rendered those pixels. 
  • View properties for individual widgets. 
  • Generally, better understand layout issues. 
The inspector view can be opened via View > Tool Windows > Flutter Inspector (it shows content only when an app is running). To inspect a specific widget, select the ‘Toggle inspect mode’ action in the toolbar, then click on the desired widget on the phone or simulator. The widget will be highlighted in your app’s UI, you’ll see the widget in the widget hierarchy in IntelliJ, and will be able to view the individual properties for that widget.



We’re actively working in this space, including working on ways to filter the number of widgets shown in the tree view; look for more news in the coming months. Don’t hesitate to provide feedback to us on the inspector!

Additional inspector features and changes in the M21 release:
  • renamed the ‘Flutter’ view to ‘Flutter Inspector’ 
  • normalized the Flutter Inspector toolbar icons 
  • in the property view, show color properties with a color swatch 
  • in the property view, show icon properties using their associated Material icons 
  • fix to enable the Flutter Inspector view to display for Bazel projects 

App launch and running improvements

We now display a notification when programs elements were successfully reloaded but not run when the view was reassembled; this is an indication that you may need to restart to see your UI changes:



Additional launch and run changes:
  • add a hyperlink for the “restart” message in the debugging console output 
  • improved console hyperlinking for local files 
  • ensure that an existing config is selected at startup, and fix run config autoselection for plugin projects 
  • for non-Bazel projects, don't show the Flutter Bazel launch type 

Testing support improvements

  • fix test discovery for plugin example tests, and fix discovery of tests in example sub-directories 
  • improve the pub root detection for flutter tests

Popular posts from this blog

AngularDart 4

AngularDart v4 is now available. We've been busy since the release angular2 v3.1.0 in May. Not only did we "drop the 2", but we also improved the compiler and tightened up the framework to give you smaller code, we updated the package structure to improve usability, and we added several new features. Check out the updated documentation to get started.
Just angular Upgrading to v4 will require more than updating your version constraint. The package has changed names (back) to angular – dropping the 2. You'll need to update your pubspec.yaml and the corresponding imports in your code. In most instances, find-and-replace should do the trick. Going forward, the package will be called package:angular. We'll just update the version number.
Smaller code The updated compiler in 4.0 allows type-based optimizations that not only improve runtime performance but generate better code because we are able to strongly type templates. A big result of the update is that many ap…

The new AdWords UI uses Dart — we asked why

Google just announced a re-designed AdWords experience. In case you’re not familiar with AdWords: businesses use it to advertise on google.com and partner websites. Advertising makes up majority of Google’s revenue, so when Google decides to completely redo the customer-facing front end to it, it’s a big deal. The Dart team is proud to say that this new front end is built with Dart and Angular 2. Whenever you asked us whether Google is ‘even using Dart for anything,’ this is what we had in mind but couldn’t say aloud. Until now. We asked Joshy Joseph, the primary technical lead on the project, some questions. Joshy is focusing on things like infrastructure, application latency and development velocity, so he’s the right person to ask about Dart.Q: What exactly did we launch on Monday?It’s a complete redesign of the AdWords customer experience that is rolling out slowly as a test to a small initial set of advertisers. The most noticeable thing is probably the Material Design look and f…

A stronger Dart for everyone

We are constantly asking ourselves:
How do we make developers even more productive when writing Dart apps? We believe that a critical part of the answer to this question is to make strongmode – a sound static type system for Dart – the standard for all Dart developers.

Teams that use Dart to build apps like Soundtrap, AdWords, AdSense, and Greentea say they really enjoy using strong mode features, such as early error detection. In fact, teams that have switched completely to strong mode cite not only early error detection but also better code readability and maintainability as major benefits. We hear this both from small teams and – even more so – from large teams with hundreds of developers writing and maintaining millions of lines of Dart code. As Björn Sperber from Soundtrap says,
Strong mode and the smooth integration with IntelliJ is a joy to use and a huge improvement. If you’ve tried out Flutter, you’ve already used strong mode checks from the Dart analyzer.

Given the benefits …