Datasets:
Ekhlass
/
flutter_docs

Dataset card Data Studio Files
xet
Community
1
text
stringlengths
1
372
flutter apps or any other dart project.
but if hello happens to be a plugin package
whose platform-specific code needs access
to the platform-specific APIs exposed by url_launcher,
you also need to add suitable dependency declarations
to your platform-specific build files, as shown below.
<topic_end>
<topic_start>
android
the following example sets a dependency for
url_launcher in hello/android/build.gradle:
you can now import io.flutter.plugins.urllauncher.UrlLauncherPlugin
and access the UrlLauncherPlugin
class in the source code at hello/android/src.
for more information on build.gradle files, see the
gradle documentation on build scripts.
<topic_end>
<topic_start>
iOS
the following example sets a dependency for
url_launcher in hello/ios/hello.podspec:
you can now #import "urllauncherplugin.h" and
access the UrlLauncherPlugin class in the source code
at hello/ios/Classes.
for additional details on .podspec files, see the
CocoaPods documentation on them.
<topic_end>
<topic_start>
web
all web dependencies are handled by the pubspec.yaml
file like any other dart package.
<topic_end>
<topic_start>
flutter favorite program
the aim of the flutter favorite program is to identify
packages and plugins that you should first consider when
building your app.
this is not a guarantee of quality or suitability to your
particular situation—you should always perform your
own evaluation of packages and plugins for your project.
you can see the complete list of
flutter favorite packages on pub.dev.
info note
if you came here looking for the happy paths recommendations,
we have discontinued that project in favor of flutter favorites.
<topic_end>
<topic_start>
metrics
flutter favorite packages have passed high quality standards
using the following metrics:
<topic_end>
<topic_start>
flutter ecosystem committee
the flutter ecosystem committee is comprised of flutter
team members and flutter community members spread
across its ecosystem.
one of their jobs is to decide when a package
has met the quality bar to become a flutter favorite.
the current committee members
(ordered alphabetically by last name)
are as follows:
if you’d like to nominate a package or plugin as a
potential future flutter favorite, or would like
to bring any other issues to the attention of the committee,
send the committee an email.
<topic_end>
<topic_start>
flutter favorite usage guidelines
flutter favorite packages are labeled as such on pub.dev
by the flutter team.
if you own a package that has been designated as a flutter favorite,
you must adhere to the following guidelines:
<topic_end>
<topic_start>
what’s next
you should expect the list of flutter favorite packages
to grow and change as the ecosystem continues to thrive.
the committee will continue working with package authors
to increase quality, as well as consider other areas of the
ecosystem that could benefit from the flutter favorite program,
such as tools, consulting firms, and prolific flutter contributors.
as the flutter ecosystem grows,
we’ll be looking at expanding the set of metrics,
which might include the following:
<topic_end>
<topic_start>
flutter favorites
you can see the complete list of
flutter favorite packages on pub.dev.
<topic_end>
<topic_start>
testing flutter apps
the more features your app has, the harder it is to test manually.
automated tests help ensure that your app performs correctly before
you publish it, while retaining your feature and bug fix velocity.
info note
for hands-on practice of testing flutter apps, see the
how to test a flutter app codelab.
automated testing falls into a few categories:
generally speaking, a well-tested app has many unit and widget tests,