Evaluate material’s SelectableText (and Flutter’s EditableText) with regards to moving Material and Cupertino out of the Flutter framework. The default for selecting static text in the framework for a long time has been SelectableText which lives in the material library and is built on top of the framework’s EditableText. SelectableText itself is not a “material” concept and fits more in a core widget offering rather than a design library.

• Consider the other selectable text offering provided by the framework in Text + SelectableRegion.
  SelectableText is mainly a platform adaptive wrapper around EditableText, that provides platform adaptive text selection context menus, spell check menus, magnifiers, and selection handles. When looking through Material and Apple's design specifications there are no specifications with regards to system controls on the platform, signaling that system controls like the ones discussed should not live in design libraries.

SelectableText provides some core platform functionality to EditableText like text selection gestures, we should investigate the value in moving this functionality to EditableText and what that means for its out of the box experience.

Evaluate the out of the box experience for Flutter’s text widgets, for example currently WidgetsApp provides a default “error” text style that is meant to signal to the user that they should define their own. We should determine if Flutter should provide reasonable defaults in the case of WidgetsApp.