Ekhlass/flutter_docs · Datasets at Hugging Face

text stringlengths 1 372
<topic_start>
what devices and OS versions does flutter run on?
we support and test running flutter on a variety
of low-end to high-end platforms. for a detailed list
of the platforms on which we test, see
the list of supported platforms.
flutter supports building ahead-of-time (aot) compiled libraries
for x86_64, armeabi-v7a, and arm64-v8a.
apps built for ARMv7 or ARM64 run fine (using ARM emulation)
on many x86 android devices.
we support developing flutter apps on a range of platforms.
see the system requirements listed under each
development operating system.
<topic_end>
<topic_start>
does flutter run on the web?
yes, web support is available in the stable channel.
for more details, check out the web instructions.
<topic_end>
<topic_start>
can i use flutter to build desktop apps?
yes, desktop support is in stable for windows,
macOS, and linux.
<topic_end>
<topic_start>
can i use flutter inside of my existing native app?
yes, learn more in the add-to-app section of our website.
<topic_end>
<topic_start>
can i access platform services and APIs like sensors and local storage?
yes. flutter gives developers out-of-the-box access to some
platform-specific services and APIs from the operating system.
however, we want to avoid the “lowest common denominator” problem
with most cross-platform APIs, so we don’t intend to build
cross-platform APIs for all native services and APIs.
a number of platform services and APIs have
ready-made packages available on pub.dev.
using an existing package is easy.
finally, we encourage developers to use flutter’s
asynchronous message passing system to create your
own integrations with platform and third-party APIs.
developers can expose as much or as little of the
platform APIs as they need, and build layers of
abstractions that are a best fit for their project.
<topic_end>
<topic_start>
can i extend and customize the bundled widgets?
absolutely. flutter’s widget system was designed
to be easily customizable.
rather than having each widget provide a large number of parameters,
flutter embraces composition. widgets are built out of smaller
widgets that you can reuse and combine in novel ways to make
custom widgets. for example, rather than subclassing a generic
button widget, ElevatedButton combines a material widget with a
GestureDetector widget. the material widget provides the visual
design and the GestureDetector widget provides the
interaction design.
to create a button with a custom visual design, you can combine
widgets that implement your visual design with a GestureDetector,
which provides the interaction design. for example,
CupertinoButton follows this approach and combines a
GestureDetector with several other widgets that implement its
visual design.
composition gives you maximum control over the visual and
interaction design of your widgets while also allowing a
large amount of code reuse. in the framework, we’ve decomposed
complex widgets to pieces that separately implement
the visual, interaction, and motion design. you can remix
these widgets however you like to make your own custom
widgets that have full range of expression.
<topic_end>
<topic_start>
why would i want to share layout code across iOS and android?
you can choose to implement different app layouts for
iOS and android. developers are free to check the mobile OS
at runtime and render different layouts,
though we find this practice to be rare.
more and more, we see mobile app layouts and designs evolving
to be more brand-driven and unified across platforms.
this implies a strong motivation to share layout and UI
code across iOS and android.
the brand identity and customization of the app’s
aesthetic design is now becoming more important than
strictly adhering to traditional platform aesthetics.
for example, app designs often require custom fonts, colors,
shapes, motion, and more in order to clearly convey their
brand identity.
we also see common layout patterns deployed across
iOS and android. for example, the “bottom nav bar”
pattern can now be naturally found across iOS and android.
there seems to be a convergence of design ideas
across mobile platforms.
<topic_end>
<topic_start>
can i interop with my mobile platform’s default programming language?
yes, flutter supports calling into the platform,
including integrating with java or kotlin code on android,
and ObjectiveC or swift code on iOS.
this is enabled by a flexible message passing style
where a flutter app might send and receive messages

<topic_start>

what devices and OS versions does flutter run on?

we support and test running flutter on a variety

of low-end to high-end platforms. for a detailed list

of the platforms on which we test, see

the list of supported platforms.

flutter supports building ahead-of-time (aot) compiled libraries

for x86_64, armeabi-v7a, and arm64-v8a.

apps built for ARMv7 or ARM64 run fine (using ARM emulation)

on many x86 android devices.

we support developing flutter apps on a range of platforms.

see the system requirements listed under each

development operating system.

<topic_end>

<topic_start>

does flutter run on the web?

yes, web support is available in the stable channel.

for more details, check out the web instructions.

<topic_end>

<topic_start>

can i use flutter to build desktop apps?

yes, desktop support is in stable for windows,

macOS, and linux.

<topic_end>

<topic_start>

can i use flutter inside of my existing native app?

yes, learn more in the add-to-app section of our website.

<topic_end>

<topic_start>

can i access platform services and APIs like sensors and local storage?

yes. flutter gives developers out-of-the-box access to some

platform-specific services and APIs from the operating system.

however, we want to avoid the “lowest common denominator” problem

with most cross-platform APIs, so we don’t intend to build

cross-platform APIs for all native services and APIs.

a number of platform services and APIs have

ready-made packages available on pub.dev.

using an existing package is easy.

finally, we encourage developers to use flutter’s

asynchronous message passing system to create your

own integrations with platform and third-party APIs.

developers can expose as much or as little of the

platform APIs as they need, and build layers of

abstractions that are a best fit for their project.

<topic_end>

<topic_start>

can i extend and customize the bundled widgets?

absolutely. flutter’s widget system was designed

to be easily customizable.

rather than having each widget provide a large number of parameters,

flutter embraces composition. widgets are built out of smaller

widgets that you can reuse and combine in novel ways to make

custom widgets. for example, rather than subclassing a generic

button widget, ElevatedButton combines a material widget with a

GestureDetector widget. the material widget provides the visual

design and the GestureDetector widget provides the

interaction design.

to create a button with a custom visual design, you can combine

widgets that implement your visual design with a GestureDetector,

which provides the interaction design. for example,

CupertinoButton follows this approach and combines a

GestureDetector with several other widgets that implement its

visual design.

composition gives you maximum control over the visual and

interaction design of your widgets while also allowing a

large amount of code reuse. in the framework, we’ve decomposed

complex widgets to pieces that separately implement

the visual, interaction, and motion design. you can remix

these widgets however you like to make your own custom

widgets that have full range of expression.

<topic_end>

<topic_start>

why would i want to share layout code across iOS and android?

you can choose to implement different app layouts for

iOS and android. developers are free to check the mobile OS

at runtime and render different layouts,

though we find this practice to be rare.

more and more, we see mobile app layouts and designs evolving

to be more brand-driven and unified across platforms.

this implies a strong motivation to share layout and UI

code across iOS and android.

the brand identity and customization of the app’s

aesthetic design is now becoming more important than

strictly adhering to traditional platform aesthetics.

for example, app designs often require custom fonts, colors,

shapes, motion, and more in order to clearly convey their

brand identity.

we also see common layout patterns deployed across

iOS and android. for example, the “bottom nav bar”

pattern can now be naturally found across iOS and android.

there seems to be a convergence of design ideas

across mobile platforms.

<topic_end>

<topic_start>

can i interop with my mobile platform’s default programming language?

yes, flutter supports calling into the platform,

including integrating with java or kotlin code on android,

and ObjectiveC or swift code on iOS.

this is enabled by a flexible message passing style

where a flutter app might send and receive messages