diff --git a/blog/2015/11/23/making-react-native-apps-accessible.html b/blog/2015/11/23/making-react-native-apps-accessible.html index 259cf4ddb75..d843f17c85b 100644 --- a/blog/2015/11/23/making-react-native-apps-accessible.html +++ b/blog/2015/11/23/making-react-native-apps-accessible.html @@ -69,7 +69,7 @@ } });

Making React Native apps accessible

November 23, 2015

Georgiy KassabliSoftware Engineer at Facebook

Georgiy Kassabli

With the recent launch of React on web and React Native on mobile, we've provided a new front-end framework for developers to build products. One key aspect of building a robust product is ensuring that anyone can use it, including people who have vision loss or other disabilities. The Accessibility API for React and React Native enables you to make any React-powered experience usable by someone who may use assistive technology, like a screen reader for the blind and visually impaired.

-

For this post, we're going to focus on React Native apps. We've designed the React Accessibility API to look and feel similar to the iOS and Android APIs. If you've developed accessible applications for the web, iOS, or Android before, you should feel comfortable with the framework and nomenclature of the React AX API. For instance, you can make a UI element accessible (therefore exposed to assistive technology) and use accessibilityLabel to provide a string description for the element:

+

For this post, we're going to focus on React Native apps. We've designed the React Accessibility API to look and feel similar to the Android and iOS APIs. If you've developed accessible applications for Android, iOS, or the web before, you should feel comfortable with the framework and nomenclature of the React AX API. For instance, you can make a UI element accessible (therefore exposed to assistive technology) and use accessibilityLabel to provide a string description for the element:

<View accessible={true} accessibilityLabel=”This is simple view”>

Let's walk through a slightly more involved application of the React AX API by looking at one of Facebook's own React-powered products: the Ads Manager app.

diff --git a/blog/2015/11/23/making-react-native-apps-accessible/index.html b/blog/2015/11/23/making-react-native-apps-accessible/index.html index 259cf4ddb75..d843f17c85b 100644 --- a/blog/2015/11/23/making-react-native-apps-accessible/index.html +++ b/blog/2015/11/23/making-react-native-apps-accessible/index.html @@ -69,7 +69,7 @@ } });

Making React Native apps accessible

November 23, 2015

Georgiy KassabliSoftware Engineer at Facebook

Georgiy Kassabli

With the recent launch of React on web and React Native on mobile, we've provided a new front-end framework for developers to build products. One key aspect of building a robust product is ensuring that anyone can use it, including people who have vision loss or other disabilities. The Accessibility API for React and React Native enables you to make any React-powered experience usable by someone who may use assistive technology, like a screen reader for the blind and visually impaired.

-

For this post, we're going to focus on React Native apps. We've designed the React Accessibility API to look and feel similar to the iOS and Android APIs. If you've developed accessible applications for the web, iOS, or Android before, you should feel comfortable with the framework and nomenclature of the React AX API. For instance, you can make a UI element accessible (therefore exposed to assistive technology) and use accessibilityLabel to provide a string description for the element:

+

For this post, we're going to focus on React Native apps. We've designed the React Accessibility API to look and feel similar to the Android and iOS APIs. If you've developed accessible applications for Android, iOS, or the web before, you should feel comfortable with the framework and nomenclature of the React AX API. For instance, you can make a UI element accessible (therefore exposed to assistive technology) and use accessibilityLabel to provide a string description for the element:

<View accessible={true} accessibilityLabel=”This is simple view”>

Let's walk through a slightly more involved application of the React AX API by looking at one of Facebook's own React-powered products: the Ads Manager app.

diff --git a/blog/2016/03/28/dive-into-react-native-performance.html b/blog/2016/03/28/dive-into-react-native-performance.html index 88527da05fb..298d5ec6b85 100644 --- a/blog/2016/03/28/dive-into-react-native-performance.html +++ b/blog/2016/03/28/dive-into-react-native-performance.html @@ -1,4 +1,4 @@ -Dive into React Native Performance · React Native

Dive into React Native Performance

March 28, 2016

Pieter De BaetsSoftware Engineer at Facebook

Pieter De Baets

React Native allows you to build iOS and Android apps in JavaScript using React and Relay's declarative programming model. This leads to more concise, easier-to-understand code; fast iteration without a compile cycle; and easy sharing of code across multiple platforms. You can ship faster and focus on details that really matter, making your app look and feel fantastic. Optimizing performance is a big part of this. Here is the story of how we made React Native app startup twice as fast.

+

Dive into React Native Performance

March 28, 2016

Pieter De BaetsSoftware Engineer at Facebook

Pieter De Baets

React Native allows you to build Android and iOS apps in JavaScript using React and Relay's declarative programming model. This leads to more concise, easier-to-understand code; fast iteration without a compile cycle; and easy sharing of code across multiple platforms. You can ship faster and focus on details that really matter, making your app look and feel fantastic. Optimizing performance is a big part of this. Here is the story of how we made React Native app startup twice as fast.

Why the hurry?

With an app that runs faster, content loads quickly, which means people get more time to interact with it, and smooth animations make the app enjoyable to use. In emerging markets, where 2011 class phones on 2G networks are the majority, a focus on performance can make the difference between an app that is usable and one that isn't.

Since releasing React Native on iOS and on Android, we have been improving list view scrolling performance, memory efficiency, UI responsiveness, and app startup time. Startup sets the first impression of an app and stresses all parts of the framework, so it is the most rewarding and challenging problem to tackle.

diff --git a/blog/2016/03/28/dive-into-react-native-performance/index.html b/blog/2016/03/28/dive-into-react-native-performance/index.html index 88527da05fb..298d5ec6b85 100644 --- a/blog/2016/03/28/dive-into-react-native-performance/index.html +++ b/blog/2016/03/28/dive-into-react-native-performance/index.html @@ -1,4 +1,4 @@ -Dive into React Native Performance · React Native

Dive into React Native Performance

March 28, 2016

Pieter De BaetsSoftware Engineer at Facebook

Pieter De Baets

React Native allows you to build iOS and Android apps in JavaScript using React and Relay's declarative programming model. This leads to more concise, easier-to-understand code; fast iteration without a compile cycle; and easy sharing of code across multiple platforms. You can ship faster and focus on details that really matter, making your app look and feel fantastic. Optimizing performance is a big part of this. Here is the story of how we made React Native app startup twice as fast.

+

Dive into React Native Performance

March 28, 2016

Pieter De BaetsSoftware Engineer at Facebook

Pieter De Baets

React Native allows you to build Android and iOS apps in JavaScript using React and Relay's declarative programming model. This leads to more concise, easier-to-understand code; fast iteration without a compile cycle; and easy sharing of code across multiple platforms. You can ship faster and focus on details that really matter, making your app look and feel fantastic. Optimizing performance is a big part of this. Here is the story of how we made React Native app startup twice as fast.

Why the hurry?

With an app that runs faster, content loads quickly, which means people get more time to interact with it, and smooth animations make the app enjoyable to use. In emerging markets, where 2011 class phones on 2G networks are the majority, a focus on performance can make the difference between an app that is usable and one that isn't.

Since releasing React Native on iOS and on Android, we have been improving list view scrolling performance, memory efficiency, UI responsiveness, and app startup time. Startup sets the first impression of an app and stresses all parts of the framework, so it is the most rewarding and challenging problem to tackle.

diff --git a/blog/2016/08/12/react-native-meetup-san-francisco.html b/blog/2016/08/12/react-native-meetup-san-francisco.html index ea5f5778b42..08c6fcf6998 100644 --- a/blog/2016/08/12/react-native-meetup-san-francisco.html +++ b/blog/2016/08/12/react-native-meetup-san-francisco.html @@ -89,23 +89,23 @@

Up next, the first featured talk of the evening. Clarence Leung, Senior Software Engineer at Netflix, presented his talk on Designing APIs for React Native. First he noted the two main types of libraries one may work on: components such as tab bars and date pickers, and libraries that provide access to native services such as the camera roll or in-app payments. There are two ways one may approach when building a library for use in React Native:

  • Provide platform-specific components
    • -
  • A cross-platform library with a similar API for both iOS and Android
    • +
  • A cross-platform library with a similar API for both Android and iOS

Each approach has its own considerations, and it’s up to you to determine what works best for your needs.

Approach #1

As an example of platform-specific components, Clarence talked about the DatePickerIOS and DatePickerAndroid from core React Native. On iOS, date pickers are rendered as part of the UI and can be easily embedded in an existing view, while date pickers on Android are presented modally. It makes sense to provide separate components in this case.

Approach #2

-

Photo pickers, on the other hand, are treated similarly on iOS and Android. There are some slight differences — Android does not group photos into folders like iOS does with Selfies, for example — but those are easily handled using if statements and the Platform component.

+

Photo pickers, on the other hand, are treated similarly on Android and iOS. There are some slight differences — Android does not group photos into folders like iOS does with Selfies, for example — but those are easily handled using if statements and the Platform component.

Regardless of which approach you settle on, it’s a good idea to minimize the API surface and build app-specific libraries. For example, iOS’s In-App Purchase framework supports one-time, consumable purchases, as well as renewable subscriptions. If your app will only need to support consumable purchases, you may get away with dropping support for subscriptions in your cross-platform library.

-

There was a brief Q&A session at the end of Clarence’s talk. One of the interesting tid bits that came out of it was that around 80% of the React Native code written for these libraries at Netflix is shared across both iOS and Android.

+

There was a brief Q&A session at the end of Clarence’s talk. One of the interesting tid bits that came out of it was that around 80% of the React Native code written for these libraries at Netflix is shared across both Android and iOS.

Bridging the Gap, Using React Native in Existing Codebases

The final talk of the night was by Leland Richardson from Airbnb. The talk was focused on the use of React Native in existing codebases. I already know how easy it is to write a new app from scratch using React Native, so I was very interested to hear about Airbnb’s experience adopting React Native in their existing native apps.

Leland started off by talking about greenfield apps versus brownfield apps. Greenfield means to start a project without the need to consider any prior work. This is in contrast to brownfield projects where you need to take into account the existing project’s requirements, development processes, and all of the teams various needs.

-

When you’re working on a greenfield app, the React Native CLI sets up a single repository for both iOS and Android and everything just works. The first challenge against using React Native at Airbnb was the fact that the iOS and Android app each had their own repository. Multi-repo companies have some hurdles to get past before they can adopt React Native.

-

To get around this, Airbnb first set up a new repo for the React Native codebase. They used their continuous integration servers to mirror the iOS and Android repos into this new repo. After tests are run and the bundle is built, the build artifacts are synced back to the iOS and Android repos. This allows the mobile engineers to work on native code without altering their development enviroment. Mobile engineers don't need to install npm, run the packager, or remember to build the JavaScript bundle. The engineers writing actual React Native code do not have to worry about syncing their code across iOS and Android, as they work on the React Native repository directly.

-

This does come with some drawbacks, mainly they could not ship atomic updates. Changes that require a combination of native and JavaScript code would require three separate pull requests, all of which had to be carefully landed. In order to avoid conflicts, CI will fail to land changes back to the iOS and Android repos if master has changed since the build started. This would cause long delays during high commit frequency days (such as when new releases are cut).

-

Airbnb has since moved to a mono repo approach. Fortunately this was already under consideration, and once the iOS and Android teams became comfortable with using React Native they were happy to accelerate the move towards the mono repo.

+

When you’re working on a greenfield app, the React Native CLI sets up a single repository for both Android and iOS and everything just works. The first challenge against using React Native at Airbnb was the fact that the Android and iOS app each had their own repository. Multi-repo companies have some hurdles to get past before they can adopt React Native.

+

To get around this, Airbnb first set up a new repo for the React Native codebase. They used their continuous integration servers to mirror the Android and iOS repos into this new repo. After tests are run and the bundle is built, the build artifacts are synced back to the Android and iOS repos. This allows the mobile engineers to work on native code without altering their development enviroment. Mobile engineers don't need to install npm, run the packager, or remember to build the JavaScript bundle. The engineers writing actual React Native code do not have to worry about syncing their code across Android and iOS, as they work on the React Native repository directly.

+

This does come with some drawbacks, mainly they could not ship atomic updates. Changes that require a combination of native and JavaScript code would require three separate pull requests, all of which had to be carefully landed. In order to avoid conflicts, CI will fail to land changes back to the Android and iOS repos if master has changed since the build started. This would cause long delays during high commit frequency days (such as when new releases are cut).

+

Airbnb has since moved to a mono repo approach. Fortunately this was already under consideration, and once the Android and iOS teams became comfortable with using React Native they were happy to accelerate the move towards the mono repo.

This has solved most of the issues they had with the split repo approach. Leland did note that this does cause a higher strain on the version control servers, which may be an issue for smaller companies.

The Navigation Problem

diff --git a/blog/2016/08/12/react-native-meetup-san-francisco/index.html b/blog/2016/08/12/react-native-meetup-san-francisco/index.html index ea5f5778b42..08c6fcf6998 100644 --- a/blog/2016/08/12/react-native-meetup-san-francisco/index.html +++ b/blog/2016/08/12/react-native-meetup-san-francisco/index.html @@ -89,23 +89,23 @@

Up next, the first featured talk of the evening. Clarence Leung, Senior Software Engineer at Netflix, presented his talk on Designing APIs for React Native. First he noted the two main types of libraries one may work on: components such as tab bars and date pickers, and libraries that provide access to native services such as the camera roll or in-app payments. There are two ways one may approach when building a library for use in React Native:

  • Provide platform-specific components
    • -
  • A cross-platform library with a similar API for both iOS and Android
    • +
  • A cross-platform library with a similar API for both Android and iOS

Each approach has its own considerations, and it’s up to you to determine what works best for your needs.

Approach #1

As an example of platform-specific components, Clarence talked about the DatePickerIOS and DatePickerAndroid from core React Native. On iOS, date pickers are rendered as part of the UI and can be easily embedded in an existing view, while date pickers on Android are presented modally. It makes sense to provide separate components in this case.

Approach #2

-

Photo pickers, on the other hand, are treated similarly on iOS and Android. There are some slight differences — Android does not group photos into folders like iOS does with Selfies, for example — but those are easily handled using if statements and the Platform component.

+

Photo pickers, on the other hand, are treated similarly on Android and iOS. There are some slight differences — Android does not group photos into folders like iOS does with Selfies, for example — but those are easily handled using if statements and the Platform component.

Regardless of which approach you settle on, it’s a good idea to minimize the API surface and build app-specific libraries. For example, iOS’s In-App Purchase framework supports one-time, consumable purchases, as well as renewable subscriptions. If your app will only need to support consumable purchases, you may get away with dropping support for subscriptions in your cross-platform library.

-

There was a brief Q&A session at the end of Clarence’s talk. One of the interesting tid bits that came out of it was that around 80% of the React Native code written for these libraries at Netflix is shared across both iOS and Android.

+

There was a brief Q&A session at the end of Clarence’s talk. One of the interesting tid bits that came out of it was that around 80% of the React Native code written for these libraries at Netflix is shared across both Android and iOS.

Bridging the Gap, Using React Native in Existing Codebases

The final talk of the night was by Leland Richardson from Airbnb. The talk was focused on the use of React Native in existing codebases. I already know how easy it is to write a new app from scratch using React Native, so I was very interested to hear about Airbnb’s experience adopting React Native in their existing native apps.

Leland started off by talking about greenfield apps versus brownfield apps. Greenfield means to start a project without the need to consider any prior work. This is in contrast to brownfield projects where you need to take into account the existing project’s requirements, development processes, and all of the teams various needs.

-

When you’re working on a greenfield app, the React Native CLI sets up a single repository for both iOS and Android and everything just works. The first challenge against using React Native at Airbnb was the fact that the iOS and Android app each had their own repository. Multi-repo companies have some hurdles to get past before they can adopt React Native.

-

To get around this, Airbnb first set up a new repo for the React Native codebase. They used their continuous integration servers to mirror the iOS and Android repos into this new repo. After tests are run and the bundle is built, the build artifacts are synced back to the iOS and Android repos. This allows the mobile engineers to work on native code without altering their development enviroment. Mobile engineers don't need to install npm, run the packager, or remember to build the JavaScript bundle. The engineers writing actual React Native code do not have to worry about syncing their code across iOS and Android, as they work on the React Native repository directly.

-

This does come with some drawbacks, mainly they could not ship atomic updates. Changes that require a combination of native and JavaScript code would require three separate pull requests, all of which had to be carefully landed. In order to avoid conflicts, CI will fail to land changes back to the iOS and Android repos if master has changed since the build started. This would cause long delays during high commit frequency days (such as when new releases are cut).

-

Airbnb has since moved to a mono repo approach. Fortunately this was already under consideration, and once the iOS and Android teams became comfortable with using React Native they were happy to accelerate the move towards the mono repo.

+

When you’re working on a greenfield app, the React Native CLI sets up a single repository for both Android and iOS and everything just works. The first challenge against using React Native at Airbnb was the fact that the Android and iOS app each had their own repository. Multi-repo companies have some hurdles to get past before they can adopt React Native.

+

To get around this, Airbnb first set up a new repo for the React Native codebase. They used their continuous integration servers to mirror the Android and iOS repos into this new repo. After tests are run and the bundle is built, the build artifacts are synced back to the Android and iOS repos. This allows the mobile engineers to work on native code without altering their development enviroment. Mobile engineers don't need to install npm, run the packager, or remember to build the JavaScript bundle. The engineers writing actual React Native code do not have to worry about syncing their code across Android and iOS, as they work on the React Native repository directly.

+

This does come with some drawbacks, mainly they could not ship atomic updates. Changes that require a combination of native and JavaScript code would require three separate pull requests, all of which had to be carefully landed. In order to avoid conflicts, CI will fail to land changes back to the Android and iOS repos if master has changed since the build started. This would cause long delays during high commit frequency days (such as when new releases are cut).

+

Airbnb has since moved to a mono repo approach. Fortunately this was already under consideration, and once the Android and iOS teams became comfortable with using React Native they were happy to accelerate the move towards the mono repo.

This has solved most of the issues they had with the split repo approach. Leland did note that this does cause a higher strain on the version control servers, which may be an issue for smaller companies.

The Navigation Problem

diff --git a/blog/2016/08/19/right-to-left-support-for-react-native-apps.html b/blog/2016/08/19/right-to-left-support-for-react-native-apps.html index 8995ccd8e11..a3a5daca1c6 100644 --- a/blog/2016/08/19/right-to-left-support-for-react-native-apps.html +++ b/blog/2016/08/19/right-to-left-support-for-react-native-apps.html @@ -148,7 +148,7 @@

Gestures and Animations

-

In iOS and Android development, when you change to RTL layout, the gestures and animations are the opposite of LTR layout. Currently, in RN, gestures and animations are not supported on RN core code level, but on components level. The good news is, some of these components already support RTL today, such as SwipeableRow and NavigationExperimental. However, other components with gestures will need to support RTL manually.

+

In Android and iOS development, when you change to RTL layout, the gestures and animations are the opposite of LTR layout. Currently, in RN, gestures and animations are not supported on RN core code level, but on components level. The good news is, some of these components already support RTL today, such as SwipeableRow and NavigationExperimental. However, other components with gestures will need to support RTL manually.

A good example to illustrate gesture RTL support is SwipeableRow.

@@ -212,7 +212,7 @@

Limitations and Future Plan

The RTL support should cover most of the UX in your app; however, there are some limitations for now:

    -
  • Text alignment behaviors differ in iOS and Android +
  • Text alignment behaviors differ in Android and iOS
    • In iOS, the default text alignment depends on the active language bundle, they are consistently on one side. In Android, the default text alignment depends on the language of the text content, i.e. English will be left-aligned and Arabic will be right-aligned.
    • In theory, this should be made consistent across platform, but some people may prefer one behavior to another when using an app. More user experience research may be needed to find out the best practice for text alignment.
      • diff --git a/blog/2016/08/19/right-to-left-support-for-react-native-apps/index.html b/blog/2016/08/19/right-to-left-support-for-react-native-apps/index.html index 8995ccd8e11..a3a5daca1c6 100644 --- a/blog/2016/08/19/right-to-left-support-for-react-native-apps/index.html +++ b/blog/2016/08/19/right-to-left-support-for-react-native-apps/index.html @@ -148,7 +148,7 @@

    Gestures and Animations

    -

    In iOS and Android development, when you change to RTL layout, the gestures and animations are the opposite of LTR layout. Currently, in RN, gestures and animations are not supported on RN core code level, but on components level. The good news is, some of these components already support RTL today, such as SwipeableRow and NavigationExperimental. However, other components with gestures will need to support RTL manually.

    +

    In Android and iOS development, when you change to RTL layout, the gestures and animations are the opposite of LTR layout. Currently, in RN, gestures and animations are not supported on RN core code level, but on components level. The good news is, some of these components already support RTL today, such as SwipeableRow and NavigationExperimental. However, other components with gestures will need to support RTL manually.

    A good example to illustrate gesture RTL support is SwipeableRow.

    @@ -212,7 +212,7 @@

    Limitations and Future Plan

    The RTL support should cover most of the UX in your app; however, there are some limitations for now:

      -
    • Text alignment behaviors differ in iOS and Android +
    • Text alignment behaviors differ in Android and iOS
      • In iOS, the default text alignment depends on the active language bundle, they are consistently on one side. In Android, the default text alignment depends on the language of the text content, i.e. English will be left-aligned and Arabic will be right-aligned.
      • In theory, this should be made consistent across platform, but some people may prefer one behavior to another when using an app. More user experience research may be needed to find out the best practice for text alignment.
        • diff --git a/blog/2016/10/25/0.36-headless-js-the-keyboard-api-and-more.html b/blog/2016/10/25/0.36-headless-js-the-keyboard-api-and-more.html index e33aec8b272..372be614bed 100644 --- a/blog/2016/10/25/0.36-headless-js-the-keyboard-api-and-more.html +++ b/blog/2016/10/25/0.36-headless-js-the-keyboard-api-and-more.html @@ -104,7 +104,7 @@ Animated.spring(a, {

        In this example, the inner image won't get stretched at all because the parent's scaling gets cancelled out. If you'd like to learn more, check out the Animations guide.

        Dark Status Bars

        -

        A new barStyle value has been added to StatusBar: dark-content. With this addition, you can now use barStyle on both iOS and Android. The behavior will now be the following:

        +

        A new barStyle value has been added to StatusBar: dark-content. With this addition, you can now use barStyle on both Android and iOS. The behavior will now be the following:

        • default: Use the platform default (light on iOS, dark on Android).
        • light-content: Use a light status bar with black text and icons.
          • diff --git a/blog/2016/10/25/0.36-headless-js-the-keyboard-api-and-more/index.html b/blog/2016/10/25/0.36-headless-js-the-keyboard-api-and-more/index.html index e33aec8b272..372be614bed 100644 --- a/blog/2016/10/25/0.36-headless-js-the-keyboard-api-and-more/index.html +++ b/blog/2016/10/25/0.36-headless-js-the-keyboard-api-and-more/index.html @@ -104,7 +104,7 @@ Animated.spring(a, {

          In this example, the inner image won't get stretched at all because the parent's scaling gets cancelled out. If you'd like to learn more, check out the Animations guide.

          Dark Status Bars

          -

          A new barStyle value has been added to StatusBar: dark-content. With this addition, you can now use barStyle on both iOS and Android. The behavior will now be the following:

          +

          A new barStyle value has been added to StatusBar: dark-content. With this addition, you can now use barStyle on both Android and iOS. The behavior will now be the following:

          • default: Use the platform default (light on iOS, dark on Android).
          • light-content: Use a light status bar with black text and icons.
            • diff --git a/blog/2016/12/05/easier-upgrades.html b/blog/2016/12/05/easier-upgrades.html index ab7ca3152e5..913c2de6d59 100644 --- a/blog/2016/12/05/easier-upgrades.html +++ b/blog/2016/12/05/easier-upgrades.html @@ -92,7 +92,7 @@

            Example output:

            You can also run react-native-git-upgrade with no arguments to upgrade to the latest version of React Native.

            -

            We try to preserve your changes in iOS and Android build files, so you don't need to run react-native link after an upgrade.

            +

            We try to preserve your changes in Android and iOS build files, so you don't need to run react-native link after an upgrade.

            We have designed the implementation to be as little intrusive as possible. It is entirely based on a local Git repository created on-the-fly in a temporary directory. It won't interfere with your project repository (no matter what VCS you use: Git, SVN, Mercurial, ... or none). Your sources are restored in case of unexpected errors.

            How does it work?

            The key step is generating a Git patch. The patch contains all the changes made in the React Native templates between the version your app is using and the new version.

            diff --git a/blog/2016/12/05/easier-upgrades/index.html b/blog/2016/12/05/easier-upgrades/index.html index ab7ca3152e5..913c2de6d59 100644 --- a/blog/2016/12/05/easier-upgrades/index.html +++ b/blog/2016/12/05/easier-upgrades/index.html @@ -92,7 +92,7 @@

            Example output:

            You can also run react-native-git-upgrade with no arguments to upgrade to the latest version of React Native.

            -

            We try to preserve your changes in iOS and Android build files, so you don't need to run react-native link after an upgrade.

            +

            We try to preserve your changes in Android and iOS build files, so you don't need to run react-native link after an upgrade.

            We have designed the implementation to be as little intrusive as possible. It is entirely based on a local Git repository created on-the-fly in a temporary directory. It won't interfere with your project repository (no matter what VCS you use: Git, SVN, Mercurial, ... or none). Your sources are restored in case of unexpected errors.

            How does it work?

            The key step is generating a Git patch. The patch contains all the changes made in the React Native templates between the version your app is using and the new version.

            diff --git a/blog/2017/08/30/react-native-monthly-3.html b/blog/2017/08/30/react-native-monthly-3.html index 9c8bd412d43..543ee4fd797 100644 --- a/blog/2017/08/30/react-native-monthly-3.html +++ b/blog/2017/08/30/react-native-monthly-3.html @@ -101,9 +101,9 @@

          Microsoft

            -
          • The new Skype app is built on top of React Native in order to facilitate sharing as much code between platforms as possible. The React Native-based Skype app is currently available in the iOS and Android app stores.
            • +
          • The new Skype app is built on top of React Native in order to facilitate sharing as much code between platforms as possible. The React Native-based Skype app is currently available in the Android and iOS app stores.
          • While building the Skype app on React Native, we send pull requests to React Native in order to address bugs and missing features that we come across. So far, we've gotten about 70 pull requests merged.
            • -
          • React Native enabled us to power both the iOS and Android Skype apps from the same codebase. We also want to use that codebase to power the Skype web app. To help us achieve that goal, we built and open sourced a thin layer on top of React/React Native called ReactXP. ReactXP provides a set of cross platform components that get mapped to React Native when targeting iOS/Android and to react-dom when targeting the web. ReactXP's goals are similar to another open source library called React Native for Web. There's a brief description of how the approaches of these libraries differ in the ReactXP FAQ.
            • +
          • React Native enabled us to power both the Android and iOS Skype apps from the same codebase. We also want to use that codebase to power the Skype web app. To help us achieve that goal, we built and open sourced a thin layer on top of React/React Native called ReactXP. ReactXP provides a set of cross platform components that get mapped to React Native when targeting iOS/Android and to react-dom when targeting the web. ReactXP's goals are similar to another open source library called React Native for Web. There's a brief description of how the approaches of these libraries differ in the ReactXP FAQ.

          Shoutem

            diff --git a/blog/2017/08/30/react-native-monthly-3/index.html b/blog/2017/08/30/react-native-monthly-3/index.html index 9c8bd412d43..543ee4fd797 100644 --- a/blog/2017/08/30/react-native-monthly-3/index.html +++ b/blog/2017/08/30/react-native-monthly-3/index.html @@ -101,9 +101,9 @@

          Microsoft

            -
          • The new Skype app is built on top of React Native in order to facilitate sharing as much code between platforms as possible. The React Native-based Skype app is currently available in the iOS and Android app stores.
            • +
          • The new Skype app is built on top of React Native in order to facilitate sharing as much code between platforms as possible. The React Native-based Skype app is currently available in the Android and iOS app stores.
          • While building the Skype app on React Native, we send pull requests to React Native in order to address bugs and missing features that we come across. So far, we've gotten about 70 pull requests merged.
            • -
          • React Native enabled us to power both the iOS and Android Skype apps from the same codebase. We also want to use that codebase to power the Skype web app. To help us achieve that goal, we built and open sourced a thin layer on top of React/React Native called ReactXP. ReactXP provides a set of cross platform components that get mapped to React Native when targeting iOS/Android and to react-dom when targeting the web. ReactXP's goals are similar to another open source library called React Native for Web. There's a brief description of how the approaches of these libraries differ in the ReactXP FAQ.
            • +
          • React Native enabled us to power both the Android and iOS Skype apps from the same codebase. We also want to use that codebase to power the Skype web app. To help us achieve that goal, we built and open sourced a thin layer on top of React/React Native called ReactXP. ReactXP provides a set of cross platform components that get mapped to React Native when targeting iOS/Android and to react-dom when targeting the web. ReactXP's goals are similar to another open source library called React Native for Web. There's a brief description of how the approaches of these libraries differ in the ReactXP FAQ.

          Shoutem

            diff --git a/blog/2018/03/05/AWS-app-sync.html b/blog/2018/03/05/AWS-app-sync.html index fd05eb1d999..0c010118e83 100644 --- a/blog/2018/03/05/AWS-app-sync.html +++ b/blog/2018/03/05/AWS-app-sync.html @@ -131,7 +131,7 @@ export default withAuthenticator(aws-exports file. However, developers can also use the library independently with existing resources.

            For a deep dive into the philosophy and to see a full demo, check out the video from AWS re:Invent.

            AWS AppSync

            -

            Shortly after the launch of AWS Amplify, we also released AWS AppSync. This is a fully managed GraphQL service that has both offline and real-time capabilities. Although you can use GraphQL in different client programming languages (including native iOS and Android), it's quite popular among React Native developers. This is because the data model fits nicely into a unidirectional data flow and component hierarchy.

            +

            Shortly after the launch of AWS Amplify, we also released AWS AppSync. This is a fully managed GraphQL service that has both offline and real-time capabilities. Although you can use GraphQL in different client programming languages (including native Android and iOS), it's quite popular among React Native developers. This is because the data model fits nicely into a unidirectional data flow and component hierarchy.

            AWS AppSync enables you to connect to resources in your own AWS account, meaning you own and control your data. This is done by using data sources, and the service supports Amazon DynamoDB, Amazon Elasticsearch, and AWS Lambda. This enables you to combine functionality (such as NoSQL and full-text search) in a single GraphQL API as a schema. This enables you to mix and match data sources. The AppSync service can also provision from a schema, so if you aren't familair with AWS services, you can write GraphQL SDL, click a button, and you're automatically up and running.

            The real-time functionality in AWS AppSync is controlled via GraphQL subscriptions with a well-known, event-based pattern. Because subscriptions in AWS AppSync are controlled on the schema with a GraphQL directive, and a schema can use any data source, this means you can trigger notifications from database operations with Amazon DynamoDB and Amazon Elasticsearch Service, or from other parts of your infrastructure with AWS Lambda.

            In a way similar to AWS Amplify, you can use enterprise security features on your GraphQL API with AWS AppSync. The service lets you get started quickly with API keys. However, as you roll to production it can transition to using AWS Identity and Access Management (IAM) or OIDC tokens from Amazon Cognito user pools. You can control access at the resolver level with policies on types. You can even use logical checks for fine-grained access control checks at run time, such as detecting if a user is the owner of a specific database resource. There are also capabilities around checking group membership for executing resolvers or individual database record access.

            diff --git a/blog/2018/03/05/AWS-app-sync/index.html b/blog/2018/03/05/AWS-app-sync/index.html index fd05eb1d999..0c010118e83 100644 --- a/blog/2018/03/05/AWS-app-sync/index.html +++ b/blog/2018/03/05/AWS-app-sync/index.html @@ -131,7 +131,7 @@ export default withAuthenticator(aws-exports file. However, developers can also use the library independently with existing resources.

            For a deep dive into the philosophy and to see a full demo, check out the video from AWS re:Invent.

            AWS AppSync

            -

            Shortly after the launch of AWS Amplify, we also released AWS AppSync. This is a fully managed GraphQL service that has both offline and real-time capabilities. Although you can use GraphQL in different client programming languages (including native iOS and Android), it's quite popular among React Native developers. This is because the data model fits nicely into a unidirectional data flow and component hierarchy.

            +

            Shortly after the launch of AWS Amplify, we also released AWS AppSync. This is a fully managed GraphQL service that has both offline and real-time capabilities. Although you can use GraphQL in different client programming languages (including native Android and iOS), it's quite popular among React Native developers. This is because the data model fits nicely into a unidirectional data flow and component hierarchy.

            AWS AppSync enables you to connect to resources in your own AWS account, meaning you own and control your data. This is done by using data sources, and the service supports Amazon DynamoDB, Amazon Elasticsearch, and AWS Lambda. This enables you to combine functionality (such as NoSQL and full-text search) in a single GraphQL API as a schema. This enables you to mix and match data sources. The AppSync service can also provision from a schema, so if you aren't familair with AWS services, you can write GraphQL SDL, click a button, and you're automatically up and running.

            The real-time functionality in AWS AppSync is controlled via GraphQL subscriptions with a well-known, event-based pattern. Because subscriptions in AWS AppSync are controlled on the schema with a GraphQL directive, and a schema can use any data source, this means you can trigger notifications from database operations with Amazon DynamoDB and Amazon Elasticsearch Service, or from other parts of your infrastructure with AWS Lambda.

            In a way similar to AWS Amplify, you can use enterprise security features on your GraphQL API with AWS AppSync. The service lets you get started quickly with API keys. However, as you roll to production it can transition to using AWS Identity and Access Management (IAM) or OIDC tokens from Amazon Cognito user pools. You can control access at the resolver level with policies on types. You can even use logical checks for fine-grained access control checks at run time, such as detecting if a user is the owner of a specific database resource. There are also capabilities around checking group membership for executing resolvers or individual database record access.

            diff --git a/blog/2018/04/09/build-com-app.html b/blog/2018/04/09/build-com-app.html index c8a0bbfb2d4..4dbe340d6f1 100644 --- a/blog/2018/04/09/build-com-app.html +++ b/blog/2018/04/09/build-com-app.html @@ -1,4 +1,4 @@ -Built with React Native - The Build.com app · React Native

Built with React Native - The Build.com app

April 9, 2018

Garrett McCulloughSenior Mobile Engineer

Garrett McCullough

Build.com, headquartered in Chico, California, is one of the largest online retailers for home improvement items. The team has had a strong web-centric business for 18 years and began thinking about a mobile App in 2015. Building unique iOS and Android apps wasn’t practical due to our small team and limited native experience. Instead, we decided to take a risk on the very new React Native framework. Our initial commit was on August 12, 2015 using React Native v0.8.0! We were live in both App Stores on October 15, 2016. Over the last two years, we’ve continued to upgrade and expand the app. We are currently on React Native version 0.53.0.

+

Built with React Native - The Build.com app

April 9, 2018

Garrett McCulloughSenior Mobile Engineer

Garrett McCullough

Build.com, headquartered in Chico, California, is one of the largest online retailers for home improvement items. The team has had a strong web-centric business for 18 years and began thinking about a mobile App in 2015. Building unique Android and iOS apps wasn’t practical due to our small team and limited native experience. Instead, we decided to take a risk on the very new React Native framework. Our initial commit was on August 12, 2015 using React Native v0.8.0! We were live in both App Stores on October 15, 2016. Over the last two years, we’ve continued to upgrade and expand the app. We are currently on React Native version 0.53.0.

You can check out the app at https://www.build.com/app.

@@ -78,7 +78,7 @@

A few standout features you might not expect include:

  1. 3D models available for around 40 products with 90 finishes
    2. -
  2. Augmented Reality (AR) to allow the user to see how lights and faucets will look in their home at 98% size accuracy. The Build.com React Native App is featured in the Apple App store for AR Shopping! AR is now available for iOS and Android!
    3. +
  3. Augmented Reality (AR) to allow the user to see how lights and faucets will look in their home at 98% size accuracy. The Build.com React Native App is featured in the Apple App store for AR Shopping! AR is now available for Android and iOS!
  4. Collaborative project management features that allow people to put together shopping lists for the different phases of their project and collaborate around selection

We’re working on many new and exciting features that will continue to improve our app experience including the next phase of Immersive Shopping with AR.

diff --git a/blog/2018/04/09/build-com-app/index.html b/blog/2018/04/09/build-com-app/index.html index c8a0bbfb2d4..4dbe340d6f1 100644 --- a/blog/2018/04/09/build-com-app/index.html +++ b/blog/2018/04/09/build-com-app/index.html @@ -1,4 +1,4 @@ -Built with React Native - The Build.com app · React Native

Built with React Native - The Build.com app

April 9, 2018

Garrett McCulloughSenior Mobile Engineer

Garrett McCullough

Build.com, headquartered in Chico, California, is one of the largest online retailers for home improvement items. The team has had a strong web-centric business for 18 years and began thinking about a mobile App in 2015. Building unique iOS and Android apps wasn’t practical due to our small team and limited native experience. Instead, we decided to take a risk on the very new React Native framework. Our initial commit was on August 12, 2015 using React Native v0.8.0! We were live in both App Stores on October 15, 2016. Over the last two years, we’ve continued to upgrade and expand the app. We are currently on React Native version 0.53.0.

+

Built with React Native - The Build.com app

April 9, 2018

Garrett McCulloughSenior Mobile Engineer

Garrett McCullough

Build.com, headquartered in Chico, California, is one of the largest online retailers for home improvement items. The team has had a strong web-centric business for 18 years and began thinking about a mobile App in 2015. Building unique Android and iOS apps wasn’t practical due to our small team and limited native experience. Instead, we decided to take a risk on the very new React Native framework. Our initial commit was on August 12, 2015 using React Native v0.8.0! We were live in both App Stores on October 15, 2016. Over the last two years, we’ve continued to upgrade and expand the app. We are currently on React Native version 0.53.0.

You can check out the app at https://www.build.com/app.

@@ -78,7 +78,7 @@

A few standout features you might not expect include:

  1. 3D models available for around 40 products with 90 finishes
    2. -
  2. Augmented Reality (AR) to allow the user to see how lights and faucets will look in their home at 98% size accuracy. The Build.com React Native App is featured in the Apple App store for AR Shopping! AR is now available for iOS and Android!
    3. +
  3. Augmented Reality (AR) to allow the user to see how lights and faucets will look in their home at 98% size accuracy. The Build.com React Native App is featured in the Apple App store for AR Shopping! AR is now available for Android and iOS!
  4. Collaborative project management features that allow people to put together shopping lists for the different phases of their project and collaborate around selection

We’re working on many new and exciting features that will continue to improve our app experience including the next phase of Immersive Shopping with AR.

diff --git a/blog/atom.xml b/blog/atom.xml index f4e7d17d60b..40ef6a85827 100644 --- a/blog/atom.xml +++ b/blog/atom.xml @@ -193,7 +193,7 @@ 2018-04-09T06:00:00Z - Build.com, headquartered in Chico, California, is one of the largest online retailers for home improvement items. The team has had a strong web-centric business for 18 years and began thinking about a mobile App in 2015. Building unique iOS and Andro...

]]> + Build.com, headquartered in Chico, California, is one of the largest online retailers for home improvement items. The team has had a strong web-centric business for 18 years and began thinking about a mobile App in 2015. Building unique Android and i...

]]> Garrett McCullough https://twitter.com/gwmccull @@ -481,7 +481,7 @@ 2016-03-28T06:00:00Z - React Native allows you to build iOS and Android apps in JavaScript using React and Relay's declarative programming model. This leads to more concise, easier-to-understand code; fast iteration without a compile cycle; and easy sharing of code across ...

]]> + React Native allows you to build Android and iOS apps in JavaScript using React and Relay's declarative programming model. This leads to more concise, easier-to-understand code; fast iteration without a compile cycle; and easy sharing of code across ...

]]> Pieter De Baets https://github.com/javache diff --git a/blog/feed.xml b/blog/feed.xml index 3696e9accee..34221e6b477 100644 --- a/blog/feed.xml +++ b/blog/feed.xml @@ -122,7 +122,7 @@ https://facebook.github.io/react-native/blog/2018/04/09/build-com-app.html https://facebook.github.io/react-native/blog/2018/04/09/build-com-app.html Mon, 09 Apr 2018 06:00:00 GMT - Build.com, headquartered in Chico, California, is one of the largest online retailers for home improvement items. The team has had a strong web-centric business for 18 years and began thinking about a mobile App in 2015. Building unique iOS and Andro...

]]> + Build.com, headquartered in Chico, California, is one of the largest online retailers for home improvement items. The team has had a strong web-centric business for 18 years and began thinking about a mobile App in 2015. Building unique Android and i...

]]> <![CDATA[Building <InputAccessoryView> For React Native]]> @@ -290,7 +290,7 @@ https://facebook.github.io/react-native/blog/2016/03/28/dive-into-react-native-performance.html https://facebook.github.io/react-native/blog/2016/03/28/dive-into-react-native-performance.html Mon, 28 Mar 2016 06:00:00 GMT - React Native allows you to build iOS and Android apps in JavaScript using React and Relay's declarative programming model. This leads to more concise, easier-to-understand code; fast iteration without a compile cycle; and easy sharing of code across ...

]]> + React Native allows you to build Android and iOS apps in JavaScript using React and Relay's declarative programming model. This leads to more concise, easier-to-understand code; fast iteration without a compile cycle; and easy sharing of code across ...

]]> <![CDATA[Introducing Hot Reloading]]> diff --git a/blog/page2/index.html b/blog/page2/index.html index 1cd61a5bf1c..58b657b9631 100644 --- a/blog/page2/index.html +++ b/blog/page2/index.html @@ -433,7 +433,7 @@ it('renders correctly with defaults', Next Steps

Check out the official React tutorial and state-management library Redux. These resources can be helpful when writing React Native apps. Additionally, you may want to look at ReactXP, a component library written entirely in TypeScript that supports both React on the web as well as React Native.

Have fun in a more type-safe React Native development environment!

-

Built with React Native - The Build.com app

April 9, 2018

Garrett McCulloughSenior Mobile Engineer

Garrett McCullough

Build.com, headquartered in Chico, California, is one of the largest online retailers for home improvement items. The team has had a strong web-centric business for 18 years and began thinking about a mobile App in 2015. Building unique iOS and Android apps wasn’t practical due to our small team and limited native experience. Instead, we decided to take a risk on the very new React Native framework. Our initial commit was on August 12, 2015 using React Native v0.8.0! We were live in both App Stores on October 15, 2016. Over the last two years, we’ve continued to upgrade and expand the app. We are currently on React Native version 0.53.0.

+

Built with React Native - The Build.com app

April 9, 2018

Garrett McCulloughSenior Mobile Engineer

Garrett McCullough

Build.com, headquartered in Chico, California, is one of the largest online retailers for home improvement items. The team has had a strong web-centric business for 18 years and began thinking about a mobile App in 2015. Building unique Android and iOS apps wasn’t practical due to our small team and limited native experience. Instead, we decided to take a risk on the very new React Native framework. Our initial commit was on August 12, 2015 using React Native v0.8.0! We were live in both App Stores on October 15, 2016. Over the last two years, we’ve continued to upgrade and expand the app. We are currently on React Native version 0.53.0.

You can check out the app at https://www.build.com/app.

@@ -443,7 +443,7 @@ it('renders correctly with defaults', A few standout features you might not expect include:

  1. 3D models available for around 40 products with 90 finishes
    2. -
  2. Augmented Reality (AR) to allow the user to see how lights and faucets will look in their home at 98% size accuracy. The Build.com React Native App is featured in the Apple App store for AR Shopping! AR is now available for iOS and Android!
    3. +
  3. Augmented Reality (AR) to allow the user to see how lights and faucets will look in their home at 98% size accuracy. The Build.com React Native App is featured in the Apple App store for AR Shopping! AR is now available for Android and iOS!
  4. Collaborative project management features that allow people to put together shopping lists for the different phases of their project and collaborate around selection

We’re working on many new and exciting features that will continue to improve our app experience including the next phase of Immersive Shopping with AR.

@@ -623,7 +623,7 @@ export default withAuthenticator(aws-exports file. However, developers can also use the library independently with existing resources.

For a deep dive into the philosophy and to see a full demo, check out the video from AWS re:Invent.

AWS AppSync

-

Shortly after the launch of AWS Amplify, we also released AWS AppSync. This is a fully managed GraphQL service that has both offline and real-time capabilities. Although you can use GraphQL in different client programming languages (including native iOS and Android), it's quite popular among React Native developers. This is because the data model fits nicely into a unidirectional data flow and component hierarchy.

+

Shortly after the launch of AWS Amplify, we also released AWS AppSync. This is a fully managed GraphQL service that has both offline and real-time capabilities. Although you can use GraphQL in different client programming languages (including native Android and iOS), it's quite popular among React Native developers. This is because the data model fits nicely into a unidirectional data flow and component hierarchy.

AWS AppSync enables you to connect to resources in your own AWS account, meaning you own and control your data. This is done by using data sources, and the service supports Amazon DynamoDB, Amazon Elasticsearch, and AWS Lambda. This enables you to combine functionality (such as NoSQL and full-text search) in a single GraphQL API as a schema. This enables you to mix and match data sources. The AppSync service can also provision from a schema, so if you aren't familair with AWS services, you can write GraphQL SDL, click a button, and you're automatically up and running.

The real-time functionality in AWS AppSync is controlled via GraphQL subscriptions with a well-known, event-based pattern. Because subscriptions in AWS AppSync are controlled on the schema with a GraphQL directive, and a schema can use any data source, this means you can trigger notifications from database operations with Amazon DynamoDB and Amazon Elasticsearch Service, or from other parts of your infrastructure with AWS Lambda.

In a way similar to AWS Amplify, you can use enterprise security features on your GraphQL API with AWS AppSync. The service lets you get started quickly with API keys. However, as you roll to production it can transition to using AWS Identity and Access Management (IAM) or OIDC tokens from Amazon Cognito user pools. You can control access at the resolver level with policies on types. You can even use logical checks for fine-grained access control checks at run time, such as detecting if a user is the owner of a specific database resource. There are also capabilities around checking group membership for executing resolvers or individual database record access.

diff --git a/blog/page3/index.html b/blog/page3/index.html index af02efd836e..7e7842f60b2 100644 --- a/blog/page3/index.html +++ b/blog/page3/index.html @@ -197,9 +197,9 @@

Microsoft

    -
  • The new Skype app is built on top of React Native in order to facilitate sharing as much code between platforms as possible. The React Native-based Skype app is currently available in the iOS and Android app stores.
    • +
  • The new Skype app is built on top of React Native in order to facilitate sharing as much code between platforms as possible. The React Native-based Skype app is currently available in the Android and iOS app stores.
  • While building the Skype app on React Native, we send pull requests to React Native in order to address bugs and missing features that we come across. So far, we've gotten about 70 pull requests merged.
    • -
  • React Native enabled us to power both the iOS and Android Skype apps from the same codebase. We also want to use that codebase to power the Skype web app. To help us achieve that goal, we built and open sourced a thin layer on top of React/React Native called ReactXP. ReactXP provides a set of cross platform components that get mapped to React Native when targeting iOS/Android and to react-dom when targeting the web. ReactXP's goals are similar to another open source library called React Native for Web. There's a brief description of how the approaches of these libraries differ in the ReactXP FAQ.
    • +
  • React Native enabled us to power both the Android and iOS Skype apps from the same codebase. We also want to use that codebase to power the Skype web app. To help us achieve that goal, we built and open sourced a thin layer on top of React/React Native called ReactXP. ReactXP provides a set of cross platform components that get mapped to React Native when targeting iOS/Android and to react-dom when targeting the web. ReactXP's goals are similar to another open source library called React Native for Web. There's a brief description of how the approaches of these libraries differ in the ReactXP FAQ.

Shoutem

    diff --git a/blog/page4/index.html b/blog/page4/index.html index e620ccf5d6d..281b483f756 100644 --- a/blog/page4/index.html +++ b/blog/page4/index.html @@ -106,7 +106,7 @@ react-native-git-up

    Example output:

    You can also run react-native-git-upgrade with no arguments to upgrade to the latest version of React Native.

    -

    We try to preserve your changes in iOS and Android build files, so you don't need to run react-native link after an upgrade.

    +

    We try to preserve your changes in Android and iOS build files, so you don't need to run react-native link after an upgrade.

    We have designed the implementation to be as little intrusive as possible. It is entirely based on a local Git repository created on-the-fly in a temporary directory. It won't interfere with your project repository (no matter what VCS you use: Git, SVN, Mercurial, ... or none). Your sources are restored in case of unexpected errors.

    How does it work?

    The key step is generating a Git patch. The patch contains all the changes made in the React Native templates between the version your app is using and the new version.

    @@ -225,7 +225,7 @@ Animated.spring(a, {

    In this example, the inner image won't get stretched at all because the parent's scaling gets cancelled out. If you'd like to learn more, check out the Animations guide.

    Dark Status Bars

    -

    A new barStyle value has been added to StatusBar: dark-content. With this addition, you can now use barStyle on both iOS and Android. The behavior will now be the following:

    +

    A new barStyle value has been added to StatusBar: dark-content. With this addition, you can now use barStyle on both Android and iOS. The behavior will now be the following:

    • default: Use the platform default (light on iOS, dark on Android).
    • light-content: Use a light status bar with black text and icons.
      • @@ -318,7 +318,7 @@ $ react-native upgrade

    Gestures and Animations

    -

    In iOS and Android development, when you change to RTL layout, the gestures and animations are the opposite of LTR layout. Currently, in RN, gestures and animations are not supported on RN core code level, but on components level. The good news is, some of these components already support RTL today, such as SwipeableRow and NavigationExperimental. However, other components with gestures will need to support RTL manually.

    +

    In Android and iOS development, when you change to RTL layout, the gestures and animations are the opposite of LTR layout. Currently, in RN, gestures and animations are not supported on RN core code level, but on components level. The good news is, some of these components already support RTL today, such as SwipeableRow and NavigationExperimental. However, other components with gestures will need to support RTL manually.

    A good example to illustrate gesture RTL support is SwipeableRow.

    @@ -382,7 +382,7 @@ $ react-native upgrade

    Limitations and Future Plan

    The RTL support should cover most of the UX in your app; however, there are some limitations for now:

      -
    • Text alignment behaviors differ in iOS and Android +
    • Text alignment behaviors differ in Android and iOS
      • In iOS, the default text alignment depends on the active language bundle, they are consistently on one side. In Android, the default text alignment depends on the language of the text content, i.e. English will be left-aligned and Arabic will be right-aligned.
      • In theory, this should be made consistent across platform, but some people may prefer one behavior to another when using an app. More user experience research may be needed to find out the best practice for text alignment.
        • @@ -418,23 +418,23 @@ $ react-native upgrade

        Up next, the first featured talk of the evening. Clarence Leung, Senior Software Engineer at Netflix, presented his talk on Designing APIs for React Native. First he noted the two main types of libraries one may work on: components such as tab bars and date pickers, and libraries that provide access to native services such as the camera roll or in-app payments. There are two ways one may approach when building a library for use in React Native:

        • Provide platform-specific components
          • -
        • A cross-platform library with a similar API for both iOS and Android
          • +
        • A cross-platform library with a similar API for both Android and iOS

        Each approach has its own considerations, and it’s up to you to determine what works best for your needs.

        Approach #1

        As an example of platform-specific components, Clarence talked about the DatePickerIOS and DatePickerAndroid from core React Native. On iOS, date pickers are rendered as part of the UI and can be easily embedded in an existing view, while date pickers on Android are presented modally. It makes sense to provide separate components in this case.

        Approach #2

        -

        Photo pickers, on the other hand, are treated similarly on iOS and Android. There are some slight differences — Android does not group photos into folders like iOS does with Selfies, for example — but those are easily handled using if statements and the Platform component.

        +

        Photo pickers, on the other hand, are treated similarly on Android and iOS. There are some slight differences — Android does not group photos into folders like iOS does with Selfies, for example — but those are easily handled using if statements and the Platform component.

        Regardless of which approach you settle on, it’s a good idea to minimize the API surface and build app-specific libraries. For example, iOS’s In-App Purchase framework supports one-time, consumable purchases, as well as renewable subscriptions. If your app will only need to support consumable purchases, you may get away with dropping support for subscriptions in your cross-platform library.

        -

        There was a brief Q&A session at the end of Clarence’s talk. One of the interesting tid bits that came out of it was that around 80% of the React Native code written for these libraries at Netflix is shared across both iOS and Android.

        +

        There was a brief Q&A session at the end of Clarence’s talk. One of the interesting tid bits that came out of it was that around 80% of the React Native code written for these libraries at Netflix is shared across both Android and iOS.

        Bridging the Gap, Using React Native in Existing Codebases

        The final talk of the night was by Leland Richardson from Airbnb. The talk was focused on the use of React Native in existing codebases. I already know how easy it is to write a new app from scratch using React Native, so I was very interested to hear about Airbnb’s experience adopting React Native in their existing native apps.

        Leland started off by talking about greenfield apps versus brownfield apps. Greenfield means to start a project without the need to consider any prior work. This is in contrast to brownfield projects where you need to take into account the existing project’s requirements, development processes, and all of the teams various needs.

        -

        When you’re working on a greenfield app, the React Native CLI sets up a single repository for both iOS and Android and everything just works. The first challenge against using React Native at Airbnb was the fact that the iOS and Android app each had their own repository. Multi-repo companies have some hurdles to get past before they can adopt React Native.

        -

        To get around this, Airbnb first set up a new repo for the React Native codebase. They used their continuous integration servers to mirror the iOS and Android repos into this new repo. After tests are run and the bundle is built, the build artifacts are synced back to the iOS and Android repos. This allows the mobile engineers to work on native code without altering their development enviroment. Mobile engineers don't need to install npm, run the packager, or remember to build the JavaScript bundle. The engineers writing actual React Native code do not have to worry about syncing their code across iOS and Android, as they work on the React Native repository directly.

        -

        This does come with some drawbacks, mainly they could not ship atomic updates. Changes that require a combination of native and JavaScript code would require three separate pull requests, all of which had to be carefully landed. In order to avoid conflicts, CI will fail to land changes back to the iOS and Android repos if master has changed since the build started. This would cause long delays during high commit frequency days (such as when new releases are cut).

        -

        Airbnb has since moved to a mono repo approach. Fortunately this was already under consideration, and once the iOS and Android teams became comfortable with using React Native they were happy to accelerate the move towards the mono repo.

        +

        When you’re working on a greenfield app, the React Native CLI sets up a single repository for both Android and iOS and everything just works. The first challenge against using React Native at Airbnb was the fact that the Android and iOS app each had their own repository. Multi-repo companies have some hurdles to get past before they can adopt React Native.

        +

        To get around this, Airbnb first set up a new repo for the React Native codebase. They used their continuous integration servers to mirror the Android and iOS repos into this new repo. After tests are run and the bundle is built, the build artifacts are synced back to the Android and iOS repos. This allows the mobile engineers to work on native code without altering their development enviroment. Mobile engineers don't need to install npm, run the packager, or remember to build the JavaScript bundle. The engineers writing actual React Native code do not have to worry about syncing their code across Android and iOS, as they work on the React Native repository directly.

        +

        This does come with some drawbacks, mainly they could not ship atomic updates. Changes that require a combination of native and JavaScript code would require three separate pull requests, all of which had to be carefully landed. In order to avoid conflicts, CI will fail to land changes back to the Android and iOS repos if master has changed since the build started. This would cause long delays during high commit frequency days (such as when new releases are cut).

        +

        Airbnb has since moved to a mono repo approach. Fortunately this was already under consideration, and once the Android and iOS teams became comfortable with using React Native they were happy to accelerate the move towards the mono repo.

        This has solved most of the issues they had with the split repo approach. Leland did note that this does cause a higher strain on the version control servers, which may be an issue for smaller companies.

        The Navigation Problem

        @@ -515,7 +515,7 @@ AppRegistry.registerComponent('ScratchPad', ()

        This is an excerpt. Read the rest of the post on Facebook Code.

        -

Dive into React Native Performance

March 28, 2016

Pieter De BaetsSoftware Engineer at Facebook

Pieter De Baets

React Native allows you to build iOS and Android apps in JavaScript using React and Relay's declarative programming model. This leads to more concise, easier-to-understand code; fast iteration without a compile cycle; and easy sharing of code across multiple platforms. You can ship faster and focus on details that really matter, making your app look and feel fantastic. Optimizing performance is a big part of this. Here is the story of how we made React Native app startup twice as fast.

+

Dive into React Native Performance

March 28, 2016

Pieter De BaetsSoftware Engineer at Facebook

Pieter De Baets

React Native allows you to build Android and iOS apps in JavaScript using React and Relay's declarative programming model. This leads to more concise, easier-to-understand code; fast iteration without a compile cycle; and easy sharing of code across multiple platforms. You can ship faster and focus on details that really matter, making your app look and feel fantastic. Optimizing performance is a big part of this. Here is the story of how we made React Native app startup twice as fast.

Why the hurry?

With an app that runs faster, content loads quickly, which means people get more time to interact with it, and smooth animations make the app enjoyable to use. In emerging markets, where 2011 class phones on 2G networks are the majority, a focus on performance can make the difference between an app that is usable and one that isn't.

Since releasing React Native on iOS and on Android, we have been improving list view scrolling performance, memory efficiency, UI responsiveness, and app startup time. Startup sets the first impression of an app and stresses all parts of the framework, so it is the most rewarding and challenging problem to tackle.

diff --git a/blog/page5/index.html b/blog/page5/index.html index b246a71cea2..5307d11dfc5 100644 --- a/blog/page5/index.html +++ b/blog/page5/index.html @@ -208,7 +208,7 @@

If you are interested in helping making hot reloading better, I encourage you to read Dan Abramov's post around the future of hot reloading and to contribute. For example, Johny Days is going to make it work with multiple connected clients. We're relying on you all to maintain and improve this feature.

With React Native, we have the opportunity to rethink the way we build apps in order to make it a great developer experience. Hot reloading is only one piece of the puzzle, what other crazy hacks can we do to make it better?

Making React Native apps accessible

November 23, 2015

Georgiy KassabliSoftware Engineer at Facebook

Georgiy Kassabli

With the recent launch of React on web and React Native on mobile, we've provided a new front-end framework for developers to build products. One key aspect of building a robust product is ensuring that anyone can use it, including people who have vision loss or other disabilities. The Accessibility API for React and React Native enables you to make any React-powered experience usable by someone who may use assistive technology, like a screen reader for the blind and visually impaired.

-

For this post, we're going to focus on React Native apps. We've designed the React Accessibility API to look and feel similar to the iOS and Android APIs. If you've developed accessible applications for the web, iOS, or Android before, you should feel comfortable with the framework and nomenclature of the React AX API. For instance, you can make a UI element accessible (therefore exposed to assistive technology) and use accessibilityLabel to provide a string description for the element:

+

For this post, we're going to focus on React Native apps. We've designed the React Accessibility API to look and feel similar to the Android and iOS APIs. If you've developed accessible applications for Android, iOS, or the web before, you should feel comfortable with the framework and nomenclature of the React AX API. For instance, you can make a UI element accessible (therefore exposed to assistive technology) and use accessibilityLabel to provide a string description for the element:

<View accessible={true} accessibilityLabel=”This is simple view”>

Let's walk through a slightly more involved application of the React AX API by looking at one of Facebook's own React-powered products: the Ads Manager app.

diff --git a/docs/0.10/accessibility.html b/docs/0.10/accessibility.html index 186e69e089c..0a0abd85b45 100644 --- a/docs/0.10/accessibility.html +++ b/docs/0.10/accessibility.html @@ -1,4 +1,4 @@ -Accessibility · React Native
Edit

Accessibility

Native App Accessibility (iOS and Android)

-

Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

+
Edit

Accessibility

Native App Accessibility (Android and iOS)

+

Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

Making Apps Accessible

Accessibility properties

@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService -
← AnimationsImproving User Experience →
Edit

Accessibility

Native App Accessibility (iOS and Android)

-

Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

+
Edit

Accessibility

Native App Accessibility (Android and iOS)

+

Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

Making Apps Accessible

Accessibility properties

@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService -
← AnimationsImproving User Experience →

0.10

Edit

Alert

Use Alert to display an alert dialog.

-

This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+

This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

On iOS, you can specify any number of buttons.

On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@

Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.10/alert/index.html b/docs/0.10/alert/index.html
index a8df889a272..18fbe9b4d7b 100644
--- a/docs/0.10/alert/index.html
+++ b/docs/0.10/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
0.10
Edit
Alert
Use Alert to display an alert dialog.

-
This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+
This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

 
Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

 
On iOS, you can specify any number of buttons.

 
On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@
 
Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

 
Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

 
Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.10/clipboard.html b/docs/0.10/clipboard.html
index 3eb8b6ba1e7..1cc32f56f74 100644
--- a/docs/0.10/clipboard.html
+++ b/docs/0.10/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
0.10
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
0.10
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.10/clipboard/index.html b/docs/0.10/clipboard/index.html
index 3eb8b6ba1e7..1cc32f56f74 100644
--- a/docs/0.10/clipboard/index.html
+++ b/docs/0.10/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
    0.10
    Edit
    Clipboard
    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
    
+        
    0.10
    Edit
    Clipboard
    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
    
 
    Methods
    
 
      
 
    • getString
      • 
diff --git a/docs/0.10/components-and-apis.html b/docs/0.10/components-and-apis.html
index d12d251e114..cacd5878997 100644
--- a/docs/0.10/components-and-apis.html
+++ b/docs/0.10/components-and-apis.html
@@ -130,7 +130,7 @@
   
      
     
       
      Picker
      
-      
      Renders the native picker component on iOS and Android.
      
+      
      Renders the native picker component on Android and iOS.
      
           
   
      
   
      
@@ -290,7 +290,7 @@
   
      
     
       
      Clipboard
      
-      
      Provides an interface for setting and getting content from the clipboard on both iOS and Android.
      
+      
      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
      
           
   
      
   
      
diff --git a/docs/0.10/components-and-apis/index.html b/docs/0.10/components-and-apis/index.html
index d12d251e114..cacd5878997 100644
--- a/docs/0.10/components-and-apis/index.html
+++ b/docs/0.10/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
      
     
       
      Picker
      
-      
      Renders the native picker component on iOS and Android.
      
+      
      Renders the native picker component on Android and iOS.
      
           
   
      
   
      
@@ -290,7 +290,7 @@
   
      
     
       
      Clipboard
      
-      
      Provides an interface for setting and getting content from the clipboard on both iOS and Android.
      
+      
      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
      
           
   
      
   
      
diff --git a/docs/0.10/getting-started.html b/docs/0.10/getting-started.html
index c0b8b179542..af1771587ab 100644
--- a/docs/0.10/getting-started.html
+++ b/docs/0.10/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
      
 
      
 
      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
      
-
      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
      
+
      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
      
 
      
   Development OS:
   
diff --git a/docs/0.10/getting-started/index.html b/docs/0.10/getting-started/index.html
index c0b8b179542..af1771587ab 100644
--- a/docs/0.10/getting-started/index.html
+++ b/docs/0.10/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
      
 
      
 
      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
      
-
      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
      
+
      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
      
 
      
   Development OS:
   
diff --git a/docs/0.10/images.html b/docs/0.10/images.html
index 9a3d486bcaf..a143bc8e84a 100644
--- a/docs/0.10/images.html
+++ b/docs/0.10/images.html
@@ -69,7 +69,7 @@
               }
             });
         
      Edit
      Images
      Static Image Resources
      
-
      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
      
+
      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
      
 
      <Image source={require('./my-icon.png')} />
 
      
 
      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
      
@@ -88,7 +88,7 @@
 
      On Windows, you might need to restart the packager if you add new images to your project.
      
 
      Here are some benefits that you get:
      
 
        
-
      1. Same system on iOS and Android.
        2. 
+
      2. Same system on Android and iOS.
        3. 
 
      3. Images live in the same folder as your JavaScript code. Components are self-contained.
        4. 
 
      4. No global namespace, i.e. you don't have to worry about name collisions.
        5. 
 
      5. Only the images that are actually used will be packaged into your app.
        6. 
diff --git a/docs/0.10/images/index.html b/docs/0.10/images/index.html
index 9a3d486bcaf..a143bc8e84a 100644
--- a/docs/0.10/images/index.html
+++ b/docs/0.10/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
      Edit
      Images
      Static Image Resources
      
-
      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
      
+
      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
      
 
      <Image source={require('./my-icon.png')} />
 
      
 
      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
      
@@ -88,7 +88,7 @@
 
      On Windows, you might need to restart the packager if you add new images to your project.
      
 
      Here are some benefits that you get:
      
 
        
-
      1. Same system on iOS and Android.
        2. 
+
      2. Same system on Android and iOS.
        3. 
 
      3. Images live in the same folder as your JavaScript code. Components are self-contained.
        4. 
 
      4. No global namespace, i.e. you don't have to worry about name collisions.
        5. 
 
      5. Only the images that are actually used will be packaged into your app.
        6. 
diff --git a/docs/0.10/navigation.html b/docs/0.10/navigation.html
index 0bf57ed865e..a0721c10d8e 100644
--- a/docs/0.10/navigation.html
+++ b/docs/0.10/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
      Edit
      Navigating Between Screens
      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
      
-
      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
      
-
      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
      
+
      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
      
+
      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
      
 
      React Navigation
      
 
      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
      
 
      The first step is to install in your project:
      
diff --git a/docs/0.10/navigation/index.html b/docs/0.10/navigation/index.html
index 0bf57ed865e..a0721c10d8e 100644
--- a/docs/0.10/navigation/index.html
+++ b/docs/0.10/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
      Edit
      Navigating Between Screens
      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
      
-
      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
      
-
      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
      
+
      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
      
+
      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
      
 
      React Navigation
      
 
      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
      
 
      The first step is to install in your project:
      
diff --git a/docs/0.10/navigator.html b/docs/0.10/navigator.html
index f47f36a9d17..79e4627271b 100644
--- a/docs/0.10/navigator.html
+++ b/docs/0.10/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
      Edit
      Navigator
      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
      
+        
      Edit
      Navigator
      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
      
 
      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
      
 
      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.10/navigator/index.html b/docs/0.10/navigator/index.html
index f47f36a9d17..79e4627271b 100644
--- a/docs/0.10/navigator/index.html
+++ b/docs/0.10/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
      Edit
      Navigator
      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
      
+        
      Edit
      Navigator
      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
      
 
      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
      
 
      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.10/picker.html b/docs/0.10/picker.html
index 326331d488f..a85047b9fc6 100644
--- a/docs/0.10/picker.html
+++ b/docs/0.10/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
      0.10
      Edit
      Picker
      Renders the native picker component on iOS and Android. Example:
      
+        
      0.10
      Edit
      Picker
      Renders the native picker component on Android and iOS. Example:
      
 
      <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.10/picker/index.html b/docs/0.10/picker/index.html
index 326331d488f..a85047b9fc6 100644
--- a/docs/0.10/picker/index.html
+++ b/docs/0.10/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
      0.10
      Edit
      Picker
      Renders the native picker component on iOS and Android. Example:
      
+        
      0.10
      Edit
      Picker
      Renders the native picker component on Android and iOS. Example:
      
 
      <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.10/platform-specific-code.html b/docs/0.10/platform-specific-code.html
index 6f768e62802..00cfaba5cf0 100644
--- a/docs/0.10/platform-specific-code.html
+++ b/docs/0.10/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
      Edit
      Platform Specific Code
      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
      
+        
      Edit
      Platform Specific Code
      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
      
 
      React Native provides two ways to organize your code and separate it by platform:
      
 
        
 
      • Using the Platform module.
        • 
diff --git a/docs/0.10/platform-specific-code/index.html b/docs/0.10/platform-specific-code/index.html
index 6f768e62802..00cfaba5cf0 100644
--- a/docs/0.10/platform-specific-code/index.html
+++ b/docs/0.10/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
      Edit
      Platform Specific Code
      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
      
+        
      Edit
      Platform Specific Code
      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
      
 
      React Native provides two ways to organize your code and separate it by platform:
      
 
        
 
      • Using the Platform module.
        • 
diff --git a/docs/0.11/accessibility.html b/docs/0.11/accessibility.html
index be66bc450cb..c319e9bcc7f 100644
--- a/docs/0.11/accessibility.html
+++ b/docs/0.11/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
      Edit
      Accessibility
      Native App Accessibility (iOS and Android)
      
-
      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
      
+        
      Edit
      Accessibility
      Native App Accessibility (Android and iOS)
      
+
      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
      
 
      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
      
 
      Making Apps Accessible
      
 
      Accessibility properties
      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
      
-
      ← AnimationsImproving User Experience →
      Edit
      Accessibility
      Native App Accessibility (iOS and Android)
      
-
      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
      
+        
      Edit
      Accessibility
      Native App Accessibility (Android and iOS)
      
+
      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
      
 
      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
      
 
      Making Apps Accessible
      
 
      Accessibility properties
      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
      
-
      ← AnimationsImproving User Experience →
      0.11
      Edit
      Alert
      Use Alert to display an alert dialog.
      
-
      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
      
+
      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
      
 
      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
      
 
      On iOS, you can specify any number of buttons.
      
 
      On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
      
@@ -25,7 +25,7 @@
 
      Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
      
 
      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
      
 
      Example usage:
      
-
      // Works on both iOS and Android
+
      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.11/alert/index.html b/docs/0.11/alert/index.html
index 0f74277a2d2..45358f2633f 100644
--- a/docs/0.11/alert/index.html
+++ b/docs/0.11/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
      0.11
      Edit
      Alert
      Use Alert to display an alert dialog.
      
-
      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
      
+
      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
      
 
      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
      
 
      On iOS, you can specify any number of buttons.
      
 
      On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
      
@@ -25,7 +25,7 @@
 
      Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
      
 
      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
      
 
      Example usage:
      
-
      // Works on both iOS and Android
+
      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.11/clipboard.html b/docs/0.11/clipboard.html
index cabbb6394e4..273060409be 100644
--- a/docs/0.11/clipboard.html
+++ b/docs/0.11/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
      0.11
      Edit
      Clipboard
      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
      
+        
      0.11
      Edit
      Clipboard
      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
      
 
      Methods
      
 
        
 
      • getString
        • 
diff --git a/docs/0.11/clipboard/index.html b/docs/0.11/clipboard/index.html
index cabbb6394e4..273060409be 100644
--- a/docs/0.11/clipboard/index.html
+++ b/docs/0.11/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
        0.11
        Edit
        Clipboard
        Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
        
+        
        0.11
        Edit
        Clipboard
        Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
        
 
        Methods
        
 
          
 
        • getString
          • 
diff --git a/docs/0.11/components-and-apis.html b/docs/0.11/components-and-apis.html
index d1344ebb00c..be5703d40de 100644
--- a/docs/0.11/components-and-apis.html
+++ b/docs/0.11/components-and-apis.html
@@ -130,7 +130,7 @@
   
          
     
       
          Picker
          
-      
          Renders the native picker component on iOS and Android.
          
+      
          Renders the native picker component on Android and iOS.
          
               
   
          
   
          
@@ -290,7 +290,7 @@
   
          
     
       
          Clipboard
          
-      
          Provides an interface for setting and getting content from the clipboard on both iOS and Android.
          
+      
          Provides an interface for setting and getting content from the clipboard on both Android and iOS.
          
               
   
          
   
          
diff --git a/docs/0.11/components-and-apis/index.html b/docs/0.11/components-and-apis/index.html
index d1344ebb00c..be5703d40de 100644
--- a/docs/0.11/components-and-apis/index.html
+++ b/docs/0.11/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
          
     
       
          Picker
          
-      
          Renders the native picker component on iOS and Android.
          
+      
          Renders the native picker component on Android and iOS.
          
               
   
          
   
          
@@ -290,7 +290,7 @@
   
          
     
       
          Clipboard
          
-      
          Provides an interface for setting and getting content from the clipboard on both iOS and Android.
          
+      
          Provides an interface for setting and getting content from the clipboard on both Android and iOS.
          
               
   
          
   
          
diff --git a/docs/0.11/getting-started.html b/docs/0.11/getting-started.html
index 74812687187..ade34f9abbf 100644
--- a/docs/0.11/getting-started.html
+++ b/docs/0.11/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
          If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
          
 
          
 
          Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
          
-
          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
          
+
          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
          
 
          
   Development OS:
   
diff --git a/docs/0.11/getting-started/index.html b/docs/0.11/getting-started/index.html
index 74812687187..ade34f9abbf 100644
--- a/docs/0.11/getting-started/index.html
+++ b/docs/0.11/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
          If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
          
 
          
 
          Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
          
-
          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
          
+
          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
          
 
          
   Development OS:
   
diff --git a/docs/0.11/images.html b/docs/0.11/images.html
index 21f5802ec86..5fdb3d7f982 100644
--- a/docs/0.11/images.html
+++ b/docs/0.11/images.html
@@ -69,7 +69,7 @@
               }
             });
         
          Edit
          Images
          Static Image Resources
          
-
          React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
          
+
          React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
          
 
          <Image source={require('./my-icon.png')} />
 
          
 
          The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
          
@@ -88,7 +88,7 @@
 
          On Windows, you might need to restart the packager if you add new images to your project.
          
 
          Here are some benefits that you get:
          
 
            
-
          1. Same system on iOS and Android.
            2. 
+
          2. Same system on Android and iOS.
            3. 
 
          3. Images live in the same folder as your JavaScript code. Components are self-contained.
            4. 
 
          4. No global namespace, i.e. you don't have to worry about name collisions.
            5. 
 
          5. Only the images that are actually used will be packaged into your app.
            6. 
diff --git a/docs/0.11/images/index.html b/docs/0.11/images/index.html
index 21f5802ec86..5fdb3d7f982 100644
--- a/docs/0.11/images/index.html
+++ b/docs/0.11/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
          Edit
          Images
          Static Image Resources
          
-
          React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
          
+
          React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
          
 
          <Image source={require('./my-icon.png')} />
 
          
 
          The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
          
@@ -88,7 +88,7 @@
 
          On Windows, you might need to restart the packager if you add new images to your project.
          
 
          Here are some benefits that you get:
          
 
            
-
          1. Same system on iOS and Android.
            2. 
+
          2. Same system on Android and iOS.
            3. 
 
          3. Images live in the same folder as your JavaScript code. Components are self-contained.
            4. 
 
          4. No global namespace, i.e. you don't have to worry about name collisions.
            5. 
 
          5. Only the images that are actually used will be packaged into your app.
            6. 
diff --git a/docs/0.11/navigation.html b/docs/0.11/navigation.html
index 0eb32ba83e7..433c6a4a974 100644
--- a/docs/0.11/navigation.html
+++ b/docs/0.11/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
          Edit
          Navigating Between Screens
          Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
          
-
          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
          
-
          If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
          
+
          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
          
+
          If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
          
 
          React Navigation
          
 
          The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
          
 
          The first step is to install in your project:
          
diff --git a/docs/0.11/navigation/index.html b/docs/0.11/navigation/index.html
index 0eb32ba83e7..433c6a4a974 100644
--- a/docs/0.11/navigation/index.html
+++ b/docs/0.11/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
          Edit
          Navigating Between Screens
          Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
          
-
          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
          
-
          If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
          
+
          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
          
+
          If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
          
 
          React Navigation
          
 
          The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
          
 
          The first step is to install in your project:
          
diff --git a/docs/0.11/navigator.html b/docs/0.11/navigator.html
index e89763ea660..8f8411cb4e5 100644
--- a/docs/0.11/navigator.html
+++ b/docs/0.11/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
          Edit
          Navigator
          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
          
+        
          Edit
          Navigator
          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
          
 
          To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
          
 
          import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.11/navigator/index.html b/docs/0.11/navigator/index.html
index e89763ea660..8f8411cb4e5 100644
--- a/docs/0.11/navigator/index.html
+++ b/docs/0.11/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
          Edit
          Navigator
          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
          
+        
          Edit
          Navigator
          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
          
 
          To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
          
 
          import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.11/picker.html b/docs/0.11/picker.html
index 975cdb46a89..4a60c82eb48 100644
--- a/docs/0.11/picker.html
+++ b/docs/0.11/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
          0.11
          Edit
          Picker
          Renders the native picker component on iOS and Android. Example:
          
+        
          0.11
          Edit
          Picker
          Renders the native picker component on Android and iOS. Example:
          
 
          <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.11/picker/index.html b/docs/0.11/picker/index.html
index 975cdb46a89..4a60c82eb48 100644
--- a/docs/0.11/picker/index.html
+++ b/docs/0.11/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
          0.11
          Edit
          Picker
          Renders the native picker component on iOS and Android. Example:
          
+        
          0.11
          Edit
          Picker
          Renders the native picker component on Android and iOS. Example:
          
 
          <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.11/platform-specific-code.html b/docs/0.11/platform-specific-code.html
index ea033d2ec9c..ac4c543fb06 100644
--- a/docs/0.11/platform-specific-code.html
+++ b/docs/0.11/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
          Edit
          Platform Specific Code
          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
          
+        
          Edit
          Platform Specific Code
          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
          
 
          React Native provides two ways to organize your code and separate it by platform:
          
 
            
 
          • Using the Platform module.
            • 
diff --git a/docs/0.11/platform-specific-code/index.html b/docs/0.11/platform-specific-code/index.html
index ea033d2ec9c..ac4c543fb06 100644
--- a/docs/0.11/platform-specific-code/index.html
+++ b/docs/0.11/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
          Edit
          Platform Specific Code
          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
          
+        
          Edit
          Platform Specific Code
          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
          
 
          React Native provides two ways to organize your code and separate it by platform:
          
 
            
 
          • Using the Platform module.
            • 
diff --git a/docs/0.12/accessibility.html b/docs/0.12/accessibility.html
index 0d29559b739..137ad8c8870 100644
--- a/docs/0.12/accessibility.html
+++ b/docs/0.12/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
          Edit
          Accessibility
          Native App Accessibility (iOS and Android)
          
-
          Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
          
+        
          Edit
          Accessibility
          Native App Accessibility (Android and iOS)
          
+
          Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
          
 
          In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
          
 
          Making Apps Accessible
          
 
          Accessibility properties
          
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
          
-
          ← AnimationsImproving User Experience →
          Edit
          Accessibility
          Native App Accessibility (iOS and Android)
          
-
          Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
          
+        
          Edit
          Accessibility
          Native App Accessibility (Android and iOS)
          
+
          Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
          
 
          In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
          
 
          Making Apps Accessible
          
 
          Accessibility properties
          
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
          
-
          ← AnimationsImproving User Experience →
          0.12
          Edit
          Alert
          Use Alert to display an alert dialog.
          
-
          This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
          
+
          This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
          
 
          Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
          
 
          On iOS, you can specify any number of buttons.
          
 
          On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
          
@@ -25,7 +25,7 @@
 
          Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
          
 
          Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
          
 
          Example usage:
          
-
          // Works on both iOS and Android
+
          // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.12/alert/index.html b/docs/0.12/alert/index.html
index 479fae03e68..7448018ccf9 100644
--- a/docs/0.12/alert/index.html
+++ b/docs/0.12/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
          0.12
          Edit
          Alert
          Use Alert to display an alert dialog.
          
-
          This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
          
+
          This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
          
 
          Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
          
 
          On iOS, you can specify any number of buttons.
          
 
          On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
          
@@ -25,7 +25,7 @@
 
          Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
          
 
          Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
          
 
          Example usage:
          
-
          // Works on both iOS and Android
+
          // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.12/clipboard.html b/docs/0.12/clipboard.html
index 8985db3284b..7b6ca6157ba 100644
--- a/docs/0.12/clipboard.html
+++ b/docs/0.12/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
          0.12
          Edit
          Clipboard
          Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
          
+        
          0.12
          Edit
          Clipboard
          Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
          
 
          Methods
          
 
            
 
          • getString
            • 
diff --git a/docs/0.12/clipboard/index.html b/docs/0.12/clipboard/index.html
index 8985db3284b..7b6ca6157ba 100644
--- a/docs/0.12/clipboard/index.html
+++ b/docs/0.12/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
            0.12
            Edit
            Clipboard
            Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
            
+        
            0.12
            Edit
            Clipboard
            Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
            
 
            Methods
            
 
              
 
            • getString
              • 
diff --git a/docs/0.12/components-and-apis.html b/docs/0.12/components-and-apis.html
index e4a49e9cda9..f20102269bc 100644
--- a/docs/0.12/components-and-apis.html
+++ b/docs/0.12/components-and-apis.html
@@ -130,7 +130,7 @@
   
              
     
       
              Picker
              
-      
              Renders the native picker component on iOS and Android.
              
+      
              Renders the native picker component on Android and iOS.
              
                   
   
              
   
              
@@ -290,7 +290,7 @@
   
              
     
       
              Clipboard
              
-      
              Provides an interface for setting and getting content from the clipboard on both iOS and Android.
              
+      
              Provides an interface for setting and getting content from the clipboard on both Android and iOS.
              
                   
   
              
   
              
diff --git a/docs/0.12/components-and-apis/index.html b/docs/0.12/components-and-apis/index.html
index e4a49e9cda9..f20102269bc 100644
--- a/docs/0.12/components-and-apis/index.html
+++ b/docs/0.12/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
              
     
       
              Picker
              
-      
              Renders the native picker component on iOS and Android.
              
+      
              Renders the native picker component on Android and iOS.
              
                   
   
              
   
              
@@ -290,7 +290,7 @@
   
              
     
       
              Clipboard
              
-      
              Provides an interface for setting and getting content from the clipboard on both iOS and Android.
              
+      
              Provides an interface for setting and getting content from the clipboard on both Android and iOS.
              
                   
   
              
   
              
diff --git a/docs/0.12/getting-started.html b/docs/0.12/getting-started.html
index 9c80e444e89..b8c9e92d00e 100644
--- a/docs/0.12/getting-started.html
+++ b/docs/0.12/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
              If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
              
 
              
 
              Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
              
-
              The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
              
+
              The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
              
 
              
   Development OS:
   
diff --git a/docs/0.12/getting-started/index.html b/docs/0.12/getting-started/index.html
index 9c80e444e89..b8c9e92d00e 100644
--- a/docs/0.12/getting-started/index.html
+++ b/docs/0.12/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
              If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
              
 
              
 
              Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
              
-
              The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
              
+
              The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
              
 
              
   Development OS:
   
diff --git a/docs/0.12/images.html b/docs/0.12/images.html
index 73cc8f53d06..59243f50635 100644
--- a/docs/0.12/images.html
+++ b/docs/0.12/images.html
@@ -69,7 +69,7 @@
               }
             });
         
              Edit
              Images
              Static Image Resources
              
-
              React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
              
+
              React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
              
 
              <Image source={require('./my-icon.png')} />
 
              
 
              The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
              
@@ -88,7 +88,7 @@
 
              On Windows, you might need to restart the packager if you add new images to your project.
              
 
              Here are some benefits that you get:
              
 
                
-
              1. Same system on iOS and Android.
                2. 
+
              2. Same system on Android and iOS.
                3. 
 
              3. Images live in the same folder as your JavaScript code. Components are self-contained.
                4. 
 
              4. No global namespace, i.e. you don't have to worry about name collisions.
                5. 
 
              5. Only the images that are actually used will be packaged into your app.
                6. 
diff --git a/docs/0.12/images/index.html b/docs/0.12/images/index.html
index 73cc8f53d06..59243f50635 100644
--- a/docs/0.12/images/index.html
+++ b/docs/0.12/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
              Edit
              Images
              Static Image Resources
              
-
              React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
              
+
              React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
              
 
              <Image source={require('./my-icon.png')} />
 
              
 
              The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
              
@@ -88,7 +88,7 @@
 
              On Windows, you might need to restart the packager if you add new images to your project.
              
 
              Here are some benefits that you get:
              
 
                
-
              1. Same system on iOS and Android.
                2. 
+
              2. Same system on Android and iOS.
                3. 
 
              3. Images live in the same folder as your JavaScript code. Components are self-contained.
                4. 
 
              4. No global namespace, i.e. you don't have to worry about name collisions.
                5. 
 
              5. Only the images that are actually used will be packaged into your app.
                6. 
diff --git a/docs/0.12/navigation.html b/docs/0.12/navigation.html
index a8ed58c4fca..b09dedf4c0f 100644
--- a/docs/0.12/navigation.html
+++ b/docs/0.12/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
              Edit
              Navigating Between Screens
              Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
              
-
              This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
              
-
              If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
              
+
              This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
              
+
              If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
              
 
              React Navigation
              
 
              The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
              
 
              The first step is to install in your project:
              
diff --git a/docs/0.12/navigation/index.html b/docs/0.12/navigation/index.html
index a8ed58c4fca..b09dedf4c0f 100644
--- a/docs/0.12/navigation/index.html
+++ b/docs/0.12/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
              Edit
              Navigating Between Screens
              Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
              
-
              This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
              
-
              If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
              
+
              This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
              
+
              If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
              
 
              React Navigation
              
 
              The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
              
 
              The first step is to install in your project:
              
diff --git a/docs/0.12/navigator.html b/docs/0.12/navigator.html
index cec7ca78330..110a2ca0a0d 100644
--- a/docs/0.12/navigator.html
+++ b/docs/0.12/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
              Edit
              Navigator
              Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
              
+        
              Edit
              Navigator
              Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
              
 
              To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
              
 
              import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.12/navigator/index.html b/docs/0.12/navigator/index.html
index cec7ca78330..110a2ca0a0d 100644
--- a/docs/0.12/navigator/index.html
+++ b/docs/0.12/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
              Edit
              Navigator
              Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
              
+        
              Edit
              Navigator
              Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
              
 
              To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
              
 
              import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.12/picker.html b/docs/0.12/picker.html
index 50af68f99ae..735980d84d5 100644
--- a/docs/0.12/picker.html
+++ b/docs/0.12/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
              0.12
              Edit
              Picker
              Renders the native picker component on iOS and Android. Example:
              
+        
              0.12
              Edit
              Picker
              Renders the native picker component on Android and iOS. Example:
              
 
              <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.12/picker/index.html b/docs/0.12/picker/index.html
index 50af68f99ae..735980d84d5 100644
--- a/docs/0.12/picker/index.html
+++ b/docs/0.12/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
              0.12
              Edit
              Picker
              Renders the native picker component on iOS and Android. Example:
              
+        
              0.12
              Edit
              Picker
              Renders the native picker component on Android and iOS. Example:
              
 
              <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.12/platform-specific-code.html b/docs/0.12/platform-specific-code.html
index ad0e19c228e..6e5351d58ee 100644
--- a/docs/0.12/platform-specific-code.html
+++ b/docs/0.12/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
              Edit
              Platform Specific Code
              When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
              
+        
              Edit
              Platform Specific Code
              When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
              
 
              React Native provides two ways to organize your code and separate it by platform:
              
 
                
 
              • Using the Platform module.
                • 
diff --git a/docs/0.12/platform-specific-code/index.html b/docs/0.12/platform-specific-code/index.html
index ad0e19c228e..6e5351d58ee 100644
--- a/docs/0.12/platform-specific-code/index.html
+++ b/docs/0.12/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
              Edit
              Platform Specific Code
              When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
              
+        
              Edit
              Platform Specific Code
              When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
              
 
              React Native provides two ways to organize your code and separate it by platform:
              
 
                
 
              • Using the Platform module.
                • 
diff --git a/docs/0.13/accessibility.html b/docs/0.13/accessibility.html
index c0f61544f89..4d7de14d9d3 100644
--- a/docs/0.13/accessibility.html
+++ b/docs/0.13/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
              Edit
              Accessibility
              Native App Accessibility (iOS and Android)
              
-
              Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
              
+        
              Edit
              Accessibility
              Native App Accessibility (Android and iOS)
              
+
              Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
              
 
              In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
              
 
              Making Apps Accessible
              
 
              Accessibility properties
              
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
              
-
              ← AnimationsImproving User Experience →
              Edit
              Accessibility
              Native App Accessibility (iOS and Android)
              
-
              Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
              
+        
              Edit
              Accessibility
              Native App Accessibility (Android and iOS)
              
+
              Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
              
 
              In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
              
 
              Making Apps Accessible
              
 
              Accessibility properties
              
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
              
-
              ← AnimationsImproving User Experience →
              0.13
              Edit
              Alert
              Use Alert to display an alert dialog.
              
-
              This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
              
+
              This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
              
 
              Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
              
 
              On iOS, you can specify any number of buttons.
              
 
              On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
              
@@ -25,7 +25,7 @@
 
              Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
              
 
              Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
              
 
              Example usage:
              
-
              // Works on both iOS and Android
+
              // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.13/alert/index.html b/docs/0.13/alert/index.html
index 2637ce6c38b..e4648db22ba 100644
--- a/docs/0.13/alert/index.html
+++ b/docs/0.13/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
              0.13
              Edit
              Alert
              Use Alert to display an alert dialog.
              
-
              This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
              
+
              This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
              
 
              Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
              
 
              On iOS, you can specify any number of buttons.
              
 
              On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
              
@@ -25,7 +25,7 @@
 
              Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
              
 
              Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
              
 
              Example usage:
              
-
              // Works on both iOS and Android
+
              // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.13/clipboard.html b/docs/0.13/clipboard.html
index 3b65fc1edda..f397e8a9b72 100644
--- a/docs/0.13/clipboard.html
+++ b/docs/0.13/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
              0.13
              Edit
              Clipboard
              Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
              
+        
              0.13
              Edit
              Clipboard
              Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
              
 
              Methods
              
 
                
 
              • getString
                • 
diff --git a/docs/0.13/clipboard/index.html b/docs/0.13/clipboard/index.html
index 3b65fc1edda..f397e8a9b72 100644
--- a/docs/0.13/clipboard/index.html
+++ b/docs/0.13/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                0.13
                Edit
                Clipboard
                Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                
+        
                0.13
                Edit
                Clipboard
                Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                
 
                Methods
                
 
                  
 
                • getString
                  • 
diff --git a/docs/0.13/components-and-apis.html b/docs/0.13/components-and-apis.html
index 38a1e9a57e6..32f30788190 100644
--- a/docs/0.13/components-and-apis.html
+++ b/docs/0.13/components-and-apis.html
@@ -130,7 +130,7 @@
   
                  
     
       
                  Picker
                  
-      
                  Renders the native picker component on iOS and Android.
                  
+      
                  Renders the native picker component on Android and iOS.
                  
                       
   
                  
   
                  
@@ -290,7 +290,7 @@
   
                  
     
       
                  Clipboard
                  
-      
                  Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                  
+      
                  Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                  
                       
   
                  
   
                  
diff --git a/docs/0.13/components-and-apis/index.html b/docs/0.13/components-and-apis/index.html
index 38a1e9a57e6..32f30788190 100644
--- a/docs/0.13/components-and-apis/index.html
+++ b/docs/0.13/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                  
     
       
                  Picker
                  
-      
                  Renders the native picker component on iOS and Android.
                  
+      
                  Renders the native picker component on Android and iOS.
                  
                       
   
                  
   
                  
@@ -290,7 +290,7 @@
   
                  
     
       
                  Clipboard
                  
-      
                  Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                  
+      
                  Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                  
                       
   
                  
   
                  
diff --git a/docs/0.13/getting-started.html b/docs/0.13/getting-started.html
index 1c4d611cb4b..4370af65b4b 100644
--- a/docs/0.13/getting-started.html
+++ b/docs/0.13/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                  If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                  
 
                  
 
                  Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                  
-
                  The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                  
+
                  The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                  
 
                  
   Development OS:
   
diff --git a/docs/0.13/getting-started/index.html b/docs/0.13/getting-started/index.html
index 1c4d611cb4b..4370af65b4b 100644
--- a/docs/0.13/getting-started/index.html
+++ b/docs/0.13/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                  If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                  
 
                  
 
                  Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                  
-
                  The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                  
+
                  The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                  
 
                  
   Development OS:
   
diff --git a/docs/0.13/images.html b/docs/0.13/images.html
index a8a96e86e7a..6ada524a797 100644
--- a/docs/0.13/images.html
+++ b/docs/0.13/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                  Edit
                  Images
                  Static Image Resources
                  
-
                  React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                  
+
                  React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                  
 
                  <Image source={require('./my-icon.png')} />
 
                  
 
                  The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                  
@@ -88,7 +88,7 @@
 
                  On Windows, you might need to restart the packager if you add new images to your project.
                  
 
                  Here are some benefits that you get:
                  
 
                    
-
                  1. Same system on iOS and Android.
                    2. 
+
                  2. Same system on Android and iOS.
                    3. 
 
                  3. Images live in the same folder as your JavaScript code. Components are self-contained.
                    4. 
 
                  4. No global namespace, i.e. you don't have to worry about name collisions.
                    5. 
 
                  5. Only the images that are actually used will be packaged into your app.
                    6. 
diff --git a/docs/0.13/images/index.html b/docs/0.13/images/index.html
index a8a96e86e7a..6ada524a797 100644
--- a/docs/0.13/images/index.html
+++ b/docs/0.13/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                  Edit
                  Images
                  Static Image Resources
                  
-
                  React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                  
+
                  React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                  
 
                  <Image source={require('./my-icon.png')} />
 
                  
 
                  The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                  
@@ -88,7 +88,7 @@
 
                  On Windows, you might need to restart the packager if you add new images to your project.
                  
 
                  Here are some benefits that you get:
                  
 
                    
-
                  1. Same system on iOS and Android.
                    2. 
+
                  2. Same system on Android and iOS.
                    3. 
 
                  3. Images live in the same folder as your JavaScript code. Components are self-contained.
                    4. 
 
                  4. No global namespace, i.e. you don't have to worry about name collisions.
                    5. 
 
                  5. Only the images that are actually used will be packaged into your app.
                    6. 
diff --git a/docs/0.13/navigation.html b/docs/0.13/navigation.html
index 0d1f7422aeb..b9039d7b179 100644
--- a/docs/0.13/navigation.html
+++ b/docs/0.13/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                  Edit
                  Navigating Between Screens
                  Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                  
-
                  This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                  
-
                  If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                  
+
                  This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                  
+
                  If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                  
 
                  React Navigation
                  
 
                  The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                  
 
                  The first step is to install in your project:
                  
diff --git a/docs/0.13/navigation/index.html b/docs/0.13/navigation/index.html
index 0d1f7422aeb..b9039d7b179 100644
--- a/docs/0.13/navigation/index.html
+++ b/docs/0.13/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                  Edit
                  Navigating Between Screens
                  Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                  
-
                  This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                  
-
                  If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                  
+
                  This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                  
+
                  If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                  
 
                  React Navigation
                  
 
                  The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                  
 
                  The first step is to install in your project:
                  
diff --git a/docs/0.13/navigator.html b/docs/0.13/navigator.html
index 567fed18391..7a53b602abd 100644
--- a/docs/0.13/navigator.html
+++ b/docs/0.13/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                  Edit
                  Navigator
                  Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                  
+        
                  Edit
                  Navigator
                  Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                  
 
                  To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                  
 
                  import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.13/navigator/index.html b/docs/0.13/navigator/index.html
index 567fed18391..7a53b602abd 100644
--- a/docs/0.13/navigator/index.html
+++ b/docs/0.13/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                  Edit
                  Navigator
                  Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                  
+        
                  Edit
                  Navigator
                  Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                  
 
                  To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                  
 
                  import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.13/picker.html b/docs/0.13/picker.html
index 3670aacd3e5..507b9f2c332 100644
--- a/docs/0.13/picker.html
+++ b/docs/0.13/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                  0.13
                  Edit
                  Picker
                  Renders the native picker component on iOS and Android. Example:
                  
+        
                  0.13
                  Edit
                  Picker
                  Renders the native picker component on Android and iOS. Example:
                  
 
                  <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.13/picker/index.html b/docs/0.13/picker/index.html
index 3670aacd3e5..507b9f2c332 100644
--- a/docs/0.13/picker/index.html
+++ b/docs/0.13/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                  0.13
                  Edit
                  Picker
                  Renders the native picker component on iOS and Android. Example:
                  
+        
                  0.13
                  Edit
                  Picker
                  Renders the native picker component on Android and iOS. Example:
                  
 
                  <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.13/platform-specific-code.html b/docs/0.13/platform-specific-code.html
index f9fc266229b..99aa9798444 100644
--- a/docs/0.13/platform-specific-code.html
+++ b/docs/0.13/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                  Edit
                  Platform Specific Code
                  When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                  
+        
                  Edit
                  Platform Specific Code
                  When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                  
 
                  React Native provides two ways to organize your code and separate it by platform:
                  
 
                    
 
                  • Using the Platform module.
                    • 
diff --git a/docs/0.13/platform-specific-code/index.html b/docs/0.13/platform-specific-code/index.html
index f9fc266229b..99aa9798444 100644
--- a/docs/0.13/platform-specific-code/index.html
+++ b/docs/0.13/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                  Edit
                  Platform Specific Code
                  When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                  
+        
                  Edit
                  Platform Specific Code
                  When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                  
 
                  React Native provides two ways to organize your code and separate it by platform:
                  
 
                    
 
                  • Using the Platform module.
                    • 
diff --git a/docs/0.14/accessibility.html b/docs/0.14/accessibility.html
index a68708146cd..3d1ad99d5e1 100644
--- a/docs/0.14/accessibility.html
+++ b/docs/0.14/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                  Edit
                  Accessibility
                  Native App Accessibility (iOS and Android)
                  
-
                  Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                  
+        
                  Edit
                  Accessibility
                  Native App Accessibility (Android and iOS)
                  
+
                  Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                  
 
                  In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                  
 
                  Making Apps Accessible
                  
 
                  Accessibility properties
                  
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                  
-
                  ← AnimationsImproving User Experience →
                  Edit
                  Accessibility
                  Native App Accessibility (iOS and Android)
                  
-
                  Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                  
+        
                  Edit
                  Accessibility
                  Native App Accessibility (Android and iOS)
                  
+
                  Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                  
 
                  In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                  
 
                  Making Apps Accessible
                  
 
                  Accessibility properties
                  
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                  
-
                  ← AnimationsImproving User Experience →
                  0.14
                  Edit
                  Alert
                  Use Alert to display an alert dialog.
                  
-
                  This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                  
+
                  This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                  
 
                  Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                  
 
                  On iOS, you can specify any number of buttons.
                  
 
                  On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                  
@@ -25,7 +25,7 @@
 
                  Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                  
 
                  Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                  
 
                  Example usage:
                  
-
                  // Works on both iOS and Android
+
                  // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.14/alert/index.html b/docs/0.14/alert/index.html
index ffe001c71a2..0ecfd755f40 100644
--- a/docs/0.14/alert/index.html
+++ b/docs/0.14/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
                  0.14
                  Edit
                  Alert
                  Use Alert to display an alert dialog.
                  
-
                  This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                  
+
                  This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                  
 
                  Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                  
 
                  On iOS, you can specify any number of buttons.
                  
 
                  On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                  
@@ -25,7 +25,7 @@
 
                  Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                  
 
                  Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                  
 
                  Example usage:
                  
-
                  // Works on both iOS and Android
+
                  // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.14/clipboard.html b/docs/0.14/clipboard.html
index 57ef8e1ec4d..b1e266d6ed4 100644
--- a/docs/0.14/clipboard.html
+++ b/docs/0.14/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                  0.14
                  Edit
                  Clipboard
                  Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                  
+        
                  0.14
                  Edit
                  Clipboard
                  Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                  
 
                  Methods
                  
 
                    
 
                  • getString
                    • 
diff --git a/docs/0.14/clipboard/index.html b/docs/0.14/clipboard/index.html
index 57ef8e1ec4d..b1e266d6ed4 100644
--- a/docs/0.14/clipboard/index.html
+++ b/docs/0.14/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                    0.14
                    Edit
                    Clipboard
                    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                    
+        
                    0.14
                    Edit
                    Clipboard
                    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                    
 
                    Methods
                    
 
                      
 
                    • getString
                      • 
diff --git a/docs/0.14/components-and-apis.html b/docs/0.14/components-and-apis.html
index ab9d2401fcf..482240591c6 100644
--- a/docs/0.14/components-and-apis.html
+++ b/docs/0.14/components-and-apis.html
@@ -130,7 +130,7 @@
   
                      
     
       
                      Picker
                      
-      
                      Renders the native picker component on iOS and Android.
                      
+      
                      Renders the native picker component on Android and iOS.
                      
                           
   
                      
   
                      
@@ -290,7 +290,7 @@
   
                      
     
       
                      Clipboard
                      
-      
                      Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                      
+      
                      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                      
                           
   
                      
   
                      
diff --git a/docs/0.14/components-and-apis/index.html b/docs/0.14/components-and-apis/index.html
index ab9d2401fcf..482240591c6 100644
--- a/docs/0.14/components-and-apis/index.html
+++ b/docs/0.14/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                      
     
       
                      Picker
                      
-      
                      Renders the native picker component on iOS and Android.
                      
+      
                      Renders the native picker component on Android and iOS.
                      
                           
   
                      
   
                      
@@ -290,7 +290,7 @@
   
                      
     
       
                      Clipboard
                      
-      
                      Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                      
+      
                      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                      
                           
   
                      
   
                      
diff --git a/docs/0.14/getting-started.html b/docs/0.14/getting-started.html
index d2cebc9b48d..4a20760a6dd 100644
--- a/docs/0.14/getting-started.html
+++ b/docs/0.14/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                      
 
                      
 
                      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                      
-
                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                      
+
                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                      
 
                      
   Development OS:
   
diff --git a/docs/0.14/getting-started/index.html b/docs/0.14/getting-started/index.html
index d2cebc9b48d..4a20760a6dd 100644
--- a/docs/0.14/getting-started/index.html
+++ b/docs/0.14/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                      
 
                      
 
                      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                      
-
                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                      
+
                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                      
 
                      
   Development OS:
   
diff --git a/docs/0.14/images.html b/docs/0.14/images.html
index b5e87a82dc0..62b5e0f3be3 100644
--- a/docs/0.14/images.html
+++ b/docs/0.14/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                      Edit
                      Images
                      Static Image Resources
                      
-
                      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                      
+
                      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                      
 
                      <Image source={require('./my-icon.png')} />
 
                      
 
                      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                      
@@ -88,7 +88,7 @@
 
                      On Windows, you might need to restart the packager if you add new images to your project.
                      
 
                      Here are some benefits that you get:
                      
 
                        
-
                      1. Same system on iOS and Android.
                        2. 
+
                      2. Same system on Android and iOS.
                        3. 
 
                      3. Images live in the same folder as your JavaScript code. Components are self-contained.
                        4. 
 
                      4. No global namespace, i.e. you don't have to worry about name collisions.
                        5. 
 
                      5. Only the images that are actually used will be packaged into your app.
                        6. 
diff --git a/docs/0.14/images/index.html b/docs/0.14/images/index.html
index b5e87a82dc0..62b5e0f3be3 100644
--- a/docs/0.14/images/index.html
+++ b/docs/0.14/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                      Edit
                      Images
                      Static Image Resources
                      
-
                      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                      
+
                      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                      
 
                      <Image source={require('./my-icon.png')} />
 
                      
 
                      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                      
@@ -88,7 +88,7 @@
 
                      On Windows, you might need to restart the packager if you add new images to your project.
                      
 
                      Here are some benefits that you get:
                      
 
                        
-
                      1. Same system on iOS and Android.
                        2. 
+
                      2. Same system on Android and iOS.
                        3. 
 
                      3. Images live in the same folder as your JavaScript code. Components are self-contained.
                        4. 
 
                      4. No global namespace, i.e. you don't have to worry about name collisions.
                        5. 
 
                      5. Only the images that are actually used will be packaged into your app.
                        6. 
diff --git a/docs/0.14/navigation.html b/docs/0.14/navigation.html
index 23f79fc43a6..25e10594f42 100644
--- a/docs/0.14/navigation.html
+++ b/docs/0.14/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                      Edit
                      Navigating Between Screens
                      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                      
-
                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                      
-
                      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                      
+
                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                      
+
                      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                      
 
                      React Navigation
                      
 
                      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                      
 
                      The first step is to install in your project:
                      
diff --git a/docs/0.14/navigation/index.html b/docs/0.14/navigation/index.html
index 23f79fc43a6..25e10594f42 100644
--- a/docs/0.14/navigation/index.html
+++ b/docs/0.14/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                      Edit
                      Navigating Between Screens
                      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                      
-
                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                      
-
                      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                      
+
                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                      
+
                      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                      
 
                      React Navigation
                      
 
                      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                      
 
                      The first step is to install in your project:
                      
diff --git a/docs/0.14/navigator.html b/docs/0.14/navigator.html
index 9f445c85ad4..7c2bc2dc1ab 100644
--- a/docs/0.14/navigator.html
+++ b/docs/0.14/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                      Edit
                      Navigator
                      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                      
+        
                      Edit
                      Navigator
                      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                      
 
                      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                      
 
                      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.14/navigator/index.html b/docs/0.14/navigator/index.html
index 9f445c85ad4..7c2bc2dc1ab 100644
--- a/docs/0.14/navigator/index.html
+++ b/docs/0.14/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                      Edit
                      Navigator
                      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                      
+        
                      Edit
                      Navigator
                      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                      
 
                      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                      
 
                      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.14/picker.html b/docs/0.14/picker.html
index 7d2e88dc23e..4b7ad4adeff 100644
--- a/docs/0.14/picker.html
+++ b/docs/0.14/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                      0.14
                      Edit
                      Picker
                      Renders the native picker component on iOS and Android. Example:
                      
+        
                      0.14
                      Edit
                      Picker
                      Renders the native picker component on Android and iOS. Example:
                      
 
                      <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.14/picker/index.html b/docs/0.14/picker/index.html
index 7d2e88dc23e..4b7ad4adeff 100644
--- a/docs/0.14/picker/index.html
+++ b/docs/0.14/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                      0.14
                      Edit
                      Picker
                      Renders the native picker component on iOS and Android. Example:
                      
+        
                      0.14
                      Edit
                      Picker
                      Renders the native picker component on Android and iOS. Example:
                      
 
                      <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.14/platform-specific-code.html b/docs/0.14/platform-specific-code.html
index e48c1f8850a..275bd5a457f 100644
--- a/docs/0.14/platform-specific-code.html
+++ b/docs/0.14/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                      Edit
                      Platform Specific Code
                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                      
+        
                      Edit
                      Platform Specific Code
                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                      
 
                      React Native provides two ways to organize your code and separate it by platform:
                      
 
                        
 
                      • Using the Platform module.
                        • 
diff --git a/docs/0.14/platform-specific-code/index.html b/docs/0.14/platform-specific-code/index.html
index e48c1f8850a..275bd5a457f 100644
--- a/docs/0.14/platform-specific-code/index.html
+++ b/docs/0.14/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                      Edit
                      Platform Specific Code
                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                      
+        
                      Edit
                      Platform Specific Code
                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                      
 
                      React Native provides two ways to organize your code and separate it by platform:
                      
 
                        
 
                      • Using the Platform module.
                        • 
diff --git a/docs/0.15/accessibility.html b/docs/0.15/accessibility.html
index e4dc14764e4..3c3987caf7f 100644
--- a/docs/0.15/accessibility.html
+++ b/docs/0.15/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                      Edit
                      Accessibility
                      Native App Accessibility (iOS and Android)
                      
-
                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
+        
                      Edit
                      Accessibility
                      Native App Accessibility (Android and iOS)
                      
+
                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
 
                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                      
 
                      Making Apps Accessible
                      
 
                      Accessibility properties
                      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                      
-
                      ← AnimationsImproving User Experience →
                      Edit
                      Accessibility
                      Native App Accessibility (iOS and Android)
                      
-
                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
+        
                      Edit
                      Accessibility
                      Native App Accessibility (Android and iOS)
                      
+
                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
 
                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                      
 
                      Making Apps Accessible
                      
 
                      Accessibility properties
                      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                      
-
                      ← AnimationsImproving User Experience →
                      0.15
                      Edit
                      Alert
                      Use Alert to display an alert dialog.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                      
 
                      On iOS, you can specify any number of buttons.
                      
 
                      On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                      
@@ -25,7 +25,7 @@
 
                      Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                      
 
                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                      
 
                      Example usage:
                      
-
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.15/alert/index.html b/docs/0.15/alert/index.html
index 53559d5a4ad..c00079b053e 100644
--- a/docs/0.15/alert/index.html
+++ b/docs/0.15/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
                      0.15
                      Edit
                      Alert
                      Use Alert to display an alert dialog.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                      
 
                      On iOS, you can specify any number of buttons.
                      
 
                      On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                      
@@ -25,7 +25,7 @@
 
                      Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                      
 
                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                      
 
                      Example usage:
                      
-
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.15/clipboard.html b/docs/0.15/clipboard.html
index f5a08aaf581..4063479c2cb 100644
--- a/docs/0.15/clipboard.html
+++ b/docs/0.15/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      0.15
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      0.15
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.15/clipboard/index.html b/docs/0.15/clipboard/index.html
index f5a08aaf581..4063479c2cb 100644
--- a/docs/0.15/clipboard/index.html
+++ b/docs/0.15/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                        0.15
                        Edit
                        Clipboard
                        Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                        
+        
                        0.15
                        Edit
                        Clipboard
                        Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                        
 
                        Methods
                        
 
                          
 
                        • getString
                          • 
diff --git a/docs/0.15/components-and-apis.html b/docs/0.15/components-and-apis.html
index 4e07d1407d3..9add366c516 100644
--- a/docs/0.15/components-and-apis.html
+++ b/docs/0.15/components-and-apis.html
@@ -130,7 +130,7 @@
   
                          
     
       
                          Picker
                          
-      
                          Renders the native picker component on iOS and Android.
                          
+      
                          Renders the native picker component on Android and iOS.
                          
                               
   
                          
   
                          
@@ -290,7 +290,7 @@
   
                          
     
       
                          Clipboard
                          
-      
                          Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                          
+      
                          Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                          
                               
   
                          
   
                          
diff --git a/docs/0.15/components-and-apis/index.html b/docs/0.15/components-and-apis/index.html
index 4e07d1407d3..9add366c516 100644
--- a/docs/0.15/components-and-apis/index.html
+++ b/docs/0.15/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                          
     
       
                          Picker
                          
-      
                          Renders the native picker component on iOS and Android.
                          
+      
                          Renders the native picker component on Android and iOS.
                          
                               
   
                          
   
                          
@@ -290,7 +290,7 @@
   
                          
     
       
                          Clipboard
                          
-      
                          Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                          
+      
                          Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                          
                               
   
                          
   
                          
diff --git a/docs/0.15/getting-started.html b/docs/0.15/getting-started.html
index c2d3b3954a0..f9261f1aefd 100644
--- a/docs/0.15/getting-started.html
+++ b/docs/0.15/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                          If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                          
 
                          
 
                          Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                          
-
                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                          
+
                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                          
 
                          
   Development OS:
   
diff --git a/docs/0.15/getting-started/index.html b/docs/0.15/getting-started/index.html
index c2d3b3954a0..f9261f1aefd 100644
--- a/docs/0.15/getting-started/index.html
+++ b/docs/0.15/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                          If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                          
 
                          
 
                          Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                          
-
                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                          
+
                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                          
 
                          
   Development OS:
   
diff --git a/docs/0.15/images.html b/docs/0.15/images.html
index 4ca9d00acc3..f7a8765940a 100644
--- a/docs/0.15/images.html
+++ b/docs/0.15/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                          Edit
                          Images
                          Static Image Resources
                          
-
                          React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                          
+
                          React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                          
 
                          <Image source={require('./my-icon.png')} />
 
                          
 
                          The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                          
@@ -88,7 +88,7 @@
 
                          On Windows, you might need to restart the packager if you add new images to your project.
                          
 
                          Here are some benefits that you get:
                          
 
                            
-
                          1. Same system on iOS and Android.
                            2. 
+
                          2. Same system on Android and iOS.
                            3. 
 
                          3. Images live in the same folder as your JavaScript code. Components are self-contained.
                            4. 
 
                          4. No global namespace, i.e. you don't have to worry about name collisions.
                            5. 
 
                          5. Only the images that are actually used will be packaged into your app.
                            6. 
diff --git a/docs/0.15/images/index.html b/docs/0.15/images/index.html
index 4ca9d00acc3..f7a8765940a 100644
--- a/docs/0.15/images/index.html
+++ b/docs/0.15/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                          Edit
                          Images
                          Static Image Resources
                          
-
                          React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                          
+
                          React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                          
 
                          <Image source={require('./my-icon.png')} />
 
                          
 
                          The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                          
@@ -88,7 +88,7 @@
 
                          On Windows, you might need to restart the packager if you add new images to your project.
                          
 
                          Here are some benefits that you get:
                          
 
                            
-
                          1. Same system on iOS and Android.
                            2. 
+
                          2. Same system on Android and iOS.
                            3. 
 
                          3. Images live in the same folder as your JavaScript code. Components are self-contained.
                            4. 
 
                          4. No global namespace, i.e. you don't have to worry about name collisions.
                            5. 
 
                          5. Only the images that are actually used will be packaged into your app.
                            6. 
diff --git a/docs/0.15/navigation.html b/docs/0.15/navigation.html
index bb9e065e536..df8bf5c292b 100644
--- a/docs/0.15/navigation.html
+++ b/docs/0.15/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                          Edit
                          Navigating Between Screens
                          Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                          
-
                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                          
-
                          If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                          
+
                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                          
+
                          If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                          
 
                          React Navigation
                          
 
                          The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                          
 
                          The first step is to install in your project:
                          
diff --git a/docs/0.15/navigation/index.html b/docs/0.15/navigation/index.html
index bb9e065e536..df8bf5c292b 100644
--- a/docs/0.15/navigation/index.html
+++ b/docs/0.15/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                          Edit
                          Navigating Between Screens
                          Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                          
-
                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                          
-
                          If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                          
+
                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                          
+
                          If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                          
 
                          React Navigation
                          
 
                          The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                          
 
                          The first step is to install in your project:
                          
diff --git a/docs/0.15/navigator.html b/docs/0.15/navigator.html
index 8765651a81c..60f5ca5337c 100644
--- a/docs/0.15/navigator.html
+++ b/docs/0.15/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                          Edit
                          Navigator
                          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                          
+        
                          Edit
                          Navigator
                          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                          
 
                          To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                          
 
                          import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.15/navigator/index.html b/docs/0.15/navigator/index.html
index 8765651a81c..60f5ca5337c 100644
--- a/docs/0.15/navigator/index.html
+++ b/docs/0.15/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                          Edit
                          Navigator
                          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                          
+        
                          Edit
                          Navigator
                          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                          
 
                          To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                          
 
                          import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.15/picker.html b/docs/0.15/picker.html
index 07c69458004..91a54361449 100644
--- a/docs/0.15/picker.html
+++ b/docs/0.15/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                          0.15
                          Edit
                          Picker
                          Renders the native picker component on iOS and Android. Example:
                          
+        
                          0.15
                          Edit
                          Picker
                          Renders the native picker component on Android and iOS. Example:
                          
 
                          <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.15/picker/index.html b/docs/0.15/picker/index.html
index 07c69458004..91a54361449 100644
--- a/docs/0.15/picker/index.html
+++ b/docs/0.15/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                          0.15
                          Edit
                          Picker
                          Renders the native picker component on iOS and Android. Example:
                          
+        
                          0.15
                          Edit
                          Picker
                          Renders the native picker component on Android and iOS. Example:
                          
 
                          <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.15/platform-specific-code.html b/docs/0.15/platform-specific-code.html
index a37c75bf640..e487097bf9f 100644
--- a/docs/0.15/platform-specific-code.html
+++ b/docs/0.15/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                          Edit
                          Platform Specific Code
                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                          
+        
                          Edit
                          Platform Specific Code
                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                          
 
                          React Native provides two ways to organize your code and separate it by platform:
                          
 
                            
 
                          • Using the Platform module.
                            • 
diff --git a/docs/0.15/platform-specific-code/index.html b/docs/0.15/platform-specific-code/index.html
index a37c75bf640..e487097bf9f 100644
--- a/docs/0.15/platform-specific-code/index.html
+++ b/docs/0.15/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                          Edit
                          Platform Specific Code
                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                          
+        
                          Edit
                          Platform Specific Code
                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                          
 
                          React Native provides two ways to organize your code and separate it by platform:
                          
 
                            
 
                          • Using the Platform module.
                            • 
diff --git a/docs/0.16/accessibility.html b/docs/0.16/accessibility.html
index bc6ede9d7bf..447c38a8a06 100644
--- a/docs/0.16/accessibility.html
+++ b/docs/0.16/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                          Edit
                          Accessibility
                          Native App Accessibility (iOS and Android)
                          
-
                          Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                          
+        
                          Edit
                          Accessibility
                          Native App Accessibility (Android and iOS)
                          
+
                          Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                          
 
                          In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                          
 
                          Making Apps Accessible
                          
 
                          Accessibility properties
                          
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                          
-
                          ← AnimationsImproving User Experience →
                          Edit
                          Accessibility
                          Native App Accessibility (iOS and Android)
                          
-
                          Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                          
+        
                          Edit
                          Accessibility
                          Native App Accessibility (Android and iOS)
                          
+
                          Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                          
 
                          In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                          
 
                          Making Apps Accessible
                          
 
                          Accessibility properties
                          
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                          
-
                          ← AnimationsImproving User Experience →
                          0.16
                          Edit
                          Alert
                          Use Alert to display an alert dialog.
                          
-
                          This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                          
+
                          This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                          
 
                          Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                          
 
                          On iOS, you can specify any number of buttons.
                          
 
                          On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                          
@@ -25,7 +25,7 @@
 
                          Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                          
 
                          Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                          
 
                          Example usage:
                          
-
                          // Works on both iOS and Android
+
                          // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.16/alert/index.html b/docs/0.16/alert/index.html
index 086dba39fc4..7ebdb244865 100644
--- a/docs/0.16/alert/index.html
+++ b/docs/0.16/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
                          0.16
                          Edit
                          Alert
                          Use Alert to display an alert dialog.
                          
-
                          This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                          
+
                          This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                          
 
                          Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                          
 
                          On iOS, you can specify any number of buttons.
                          
 
                          On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                          
@@ -25,7 +25,7 @@
 
                          Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                          
 
                          Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                          
 
                          Example usage:
                          
-
                          // Works on both iOS and Android
+
                          // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.16/clipboard.html b/docs/0.16/clipboard.html
index f911e78d7df..64175ef22fe 100644
--- a/docs/0.16/clipboard.html
+++ b/docs/0.16/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                          0.16
                          Edit
                          Clipboard
                          Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                          
+        
                          0.16
                          Edit
                          Clipboard
                          Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                          
 
                          Methods
                          
 
                            
 
                          • getString
                            • 
diff --git a/docs/0.16/clipboard/index.html b/docs/0.16/clipboard/index.html
index f911e78d7df..64175ef22fe 100644
--- a/docs/0.16/clipboard/index.html
+++ b/docs/0.16/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                            0.16
                            Edit
                            Clipboard
                            Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                            
+        
                            0.16
                            Edit
                            Clipboard
                            Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                            
 
                            Methods
                            
 
                              
 
                            • getString
                              • 
diff --git a/docs/0.16/components-and-apis.html b/docs/0.16/components-and-apis.html
index dc5bebea5a2..b8b67e083f0 100644
--- a/docs/0.16/components-and-apis.html
+++ b/docs/0.16/components-and-apis.html
@@ -130,7 +130,7 @@
   
                              
     
       
                              Picker
                              
-      
                              Renders the native picker component on iOS and Android.
                              
+      
                              Renders the native picker component on Android and iOS.
                              
                                   
   
                              
   
                              
@@ -290,7 +290,7 @@
   
                              
     
       
                              Clipboard
                              
-      
                              Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                              
+      
                              Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                              
                                   
   
                              
   
                              
diff --git a/docs/0.16/components-and-apis/index.html b/docs/0.16/components-and-apis/index.html
index dc5bebea5a2..b8b67e083f0 100644
--- a/docs/0.16/components-and-apis/index.html
+++ b/docs/0.16/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                              
     
       
                              Picker
                              
-      
                              Renders the native picker component on iOS and Android.
                              
+      
                              Renders the native picker component on Android and iOS.
                              
                                   
   
                              
   
                              
@@ -290,7 +290,7 @@
   
                              
     
       
                              Clipboard
                              
-      
                              Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                              
+      
                              Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                              
                                   
   
                              
   
                              
diff --git a/docs/0.16/getting-started.html b/docs/0.16/getting-started.html
index 6905e80ba34..8bd4853ee20 100644
--- a/docs/0.16/getting-started.html
+++ b/docs/0.16/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                              If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                              
 
                              
 
                              Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                              
-
                              The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                              
+
                              The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                              
 
                              
   Development OS:
   
diff --git a/docs/0.16/getting-started/index.html b/docs/0.16/getting-started/index.html
index 6905e80ba34..8bd4853ee20 100644
--- a/docs/0.16/getting-started/index.html
+++ b/docs/0.16/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                              If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                              
 
                              
 
                              Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                              
-
                              The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                              
+
                              The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                              
 
                              
   Development OS:
   
diff --git a/docs/0.16/images.html b/docs/0.16/images.html
index c040784f755..dfd6fba8c12 100644
--- a/docs/0.16/images.html
+++ b/docs/0.16/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                              Edit
                              Images
                              Static Image Resources
                              
-
                              React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                              
+
                              React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                              
 
                              <Image source={require('./my-icon.png')} />
 
                              
 
                              The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                              
@@ -88,7 +88,7 @@
 
                              On Windows, you might need to restart the packager if you add new images to your project.
                              
 
                              Here are some benefits that you get:
                              
 
                                
-
                              1. Same system on iOS and Android.
                                2. 
+
                              2. Same system on Android and iOS.
                                3. 
 
                              3. Images live in the same folder as your JavaScript code. Components are self-contained.
                                4. 
 
                              4. No global namespace, i.e. you don't have to worry about name collisions.
                                5. 
 
                              5. Only the images that are actually used will be packaged into your app.
                                6. 
diff --git a/docs/0.16/images/index.html b/docs/0.16/images/index.html
index c040784f755..dfd6fba8c12 100644
--- a/docs/0.16/images/index.html
+++ b/docs/0.16/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                              Edit
                              Images
                              Static Image Resources
                              
-
                              React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                              
+
                              React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                              
 
                              <Image source={require('./my-icon.png')} />
 
                              
 
                              The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                              
@@ -88,7 +88,7 @@
 
                              On Windows, you might need to restart the packager if you add new images to your project.
                              
 
                              Here are some benefits that you get:
                              
 
                                
-
                              1. Same system on iOS and Android.
                                2. 
+
                              2. Same system on Android and iOS.
                                3. 
 
                              3. Images live in the same folder as your JavaScript code. Components are self-contained.
                                4. 
 
                              4. No global namespace, i.e. you don't have to worry about name collisions.
                                5. 
 
                              5. Only the images that are actually used will be packaged into your app.
                                6. 
diff --git a/docs/0.16/navigation.html b/docs/0.16/navigation.html
index 79ee912a234..bef227c7c4d 100644
--- a/docs/0.16/navigation.html
+++ b/docs/0.16/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                              Edit
                              Navigating Between Screens
                              Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                              
-
                              This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                              
-
                              If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                              
+
                              This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                              
+
                              If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                              
 
                              React Navigation
                              
 
                              The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                              
 
                              The first step is to install in your project:
                              
diff --git a/docs/0.16/navigation/index.html b/docs/0.16/navigation/index.html
index 79ee912a234..bef227c7c4d 100644
--- a/docs/0.16/navigation/index.html
+++ b/docs/0.16/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                              Edit
                              Navigating Between Screens
                              Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                              
-
                              This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                              
-
                              If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                              
+
                              This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                              
+
                              If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                              
 
                              React Navigation
                              
 
                              The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                              
 
                              The first step is to install in your project:
                              
diff --git a/docs/0.16/navigator.html b/docs/0.16/navigator.html
index 8e25ee86d8b..ae972dccce7 100644
--- a/docs/0.16/navigator.html
+++ b/docs/0.16/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                              Edit
                              Navigator
                              Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                              
+        
                              Edit
                              Navigator
                              Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                              
 
                              To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                              
 
                              import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.16/navigator/index.html b/docs/0.16/navigator/index.html
index 8e25ee86d8b..ae972dccce7 100644
--- a/docs/0.16/navigator/index.html
+++ b/docs/0.16/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                              Edit
                              Navigator
                              Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                              
+        
                              Edit
                              Navigator
                              Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                              
 
                              To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                              
 
                              import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.16/picker.html b/docs/0.16/picker.html
index 7e1511a68c5..a74345be917 100644
--- a/docs/0.16/picker.html
+++ b/docs/0.16/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                              0.16
                              Edit
                              Picker
                              Renders the native picker component on iOS and Android. Example:
                              
+        
                              0.16
                              Edit
                              Picker
                              Renders the native picker component on Android and iOS. Example:
                              
 
                              <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.16/picker/index.html b/docs/0.16/picker/index.html
index 7e1511a68c5..a74345be917 100644
--- a/docs/0.16/picker/index.html
+++ b/docs/0.16/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                              0.16
                              Edit
                              Picker
                              Renders the native picker component on iOS and Android. Example:
                              
+        
                              0.16
                              Edit
                              Picker
                              Renders the native picker component on Android and iOS. Example:
                              
 
                              <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.16/platform-specific-code.html b/docs/0.16/platform-specific-code.html
index 781b90d0698..746e372eee3 100644
--- a/docs/0.16/platform-specific-code.html
+++ b/docs/0.16/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                              Edit
                              Platform Specific Code
                              When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                              
+        
                              Edit
                              Platform Specific Code
                              When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                              
 
                              React Native provides two ways to organize your code and separate it by platform:
                              
 
                                
 
                              • Using the Platform module.
                                • 
diff --git a/docs/0.16/platform-specific-code/index.html b/docs/0.16/platform-specific-code/index.html
index 781b90d0698..746e372eee3 100644
--- a/docs/0.16/platform-specific-code/index.html
+++ b/docs/0.16/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                              Edit
                              Platform Specific Code
                              When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                              
+        
                              Edit
                              Platform Specific Code
                              When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                              
 
                              React Native provides two ways to organize your code and separate it by platform:
                              
 
                                
 
                              • Using the Platform module.
                                • 
diff --git a/docs/0.17/accessibility.html b/docs/0.17/accessibility.html
index 4b184f76fe3..43e443c8f73 100644
--- a/docs/0.17/accessibility.html
+++ b/docs/0.17/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                              Edit
                              Accessibility
                              Native App Accessibility (iOS and Android)
                              
-
                              Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                              
+        
                              Edit
                              Accessibility
                              Native App Accessibility (Android and iOS)
                              
+
                              Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                              
 
                              In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                              
 
                              Making Apps Accessible
                              
 
                              Accessibility properties
                              
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                              
-
                              ← AnimationsImproving User Experience →
                              Edit
                              Accessibility
                              Native App Accessibility (iOS and Android)
                              
-
                              Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                              
+        
                              Edit
                              Accessibility
                              Native App Accessibility (Android and iOS)
                              
+
                              Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                              
 
                              In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                              
 
                              Making Apps Accessible
                              
 
                              Accessibility properties
                              
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                              
-
                              ← AnimationsImproving User Experience →
                              0.17
                              Edit
                              Alert
                              Use Alert to display an alert dialog.
                              
-
                              This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                              
+
                              This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                              
 
                              Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                              
 
                              On iOS, you can specify any number of buttons.
                              
 
                              On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                              
@@ -25,7 +25,7 @@
 
                              Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                              
 
                              Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                              
 
                              Example usage:
                              
-
                              // Works on both iOS and Android
+
                              // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.17/alert/index.html b/docs/0.17/alert/index.html
index f0192170b25..2c66b99d9e6 100644
--- a/docs/0.17/alert/index.html
+++ b/docs/0.17/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
                              0.17
                              Edit
                              Alert
                              Use Alert to display an alert dialog.
                              
-
                              This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                              
+
                              This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                              
 
                              Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                              
 
                              On iOS, you can specify any number of buttons.
                              
 
                              On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                              
@@ -25,7 +25,7 @@
 
                              Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                              
 
                              Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                              
 
                              Example usage:
                              
-
                              // Works on both iOS and Android
+
                              // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.17/clipboard.html b/docs/0.17/clipboard.html
index 25a3b0b47ac..2b3d7d51319 100644
--- a/docs/0.17/clipboard.html
+++ b/docs/0.17/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                              0.17
                              Edit
                              Clipboard
                              Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                              
+        
                              0.17
                              Edit
                              Clipboard
                              Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                              
 
                              Methods
                              
 
                                
 
                              • getString
                                • 
diff --git a/docs/0.17/clipboard/index.html b/docs/0.17/clipboard/index.html
index 25a3b0b47ac..2b3d7d51319 100644
--- a/docs/0.17/clipboard/index.html
+++ b/docs/0.17/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                                0.17
                                Edit
                                Clipboard
                                Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                                
+        
                                0.17
                                Edit
                                Clipboard
                                Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                                
 
                                Methods
                                
 
                                  
 
                                • getString
                                  • 
diff --git a/docs/0.17/components-and-apis.html b/docs/0.17/components-and-apis.html
index bbb681f615b..034a38d401c 100644
--- a/docs/0.17/components-and-apis.html
+++ b/docs/0.17/components-and-apis.html
@@ -130,7 +130,7 @@
   
                                  
     
       
                                  Picker
                                  
-      
                                  Renders the native picker component on iOS and Android.
                                  
+      
                                  Renders the native picker component on Android and iOS.
                                  
                                       
   
                                  
   
                                  
@@ -290,7 +290,7 @@
   
                                  
     
       
                                  Clipboard
                                  
-      
                                  Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                                  
+      
                                  Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                                  
                                       
   
                                  
   
                                  
diff --git a/docs/0.17/components-and-apis/index.html b/docs/0.17/components-and-apis/index.html
index bbb681f615b..034a38d401c 100644
--- a/docs/0.17/components-and-apis/index.html
+++ b/docs/0.17/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                                  
     
       
                                  Picker
                                  
-      
                                  Renders the native picker component on iOS and Android.
                                  
+      
                                  Renders the native picker component on Android and iOS.
                                  
                                       
   
                                  
   
                                  
@@ -290,7 +290,7 @@
   
                                  
     
       
                                  Clipboard
                                  
-      
                                  Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                                  
+      
                                  Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                                  
                                       
   
                                  
   
                                  
diff --git a/docs/0.17/getting-started.html b/docs/0.17/getting-started.html
index 4d9429c69d6..b1f464a1dc2 100644
--- a/docs/0.17/getting-started.html
+++ b/docs/0.17/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                                  If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                                  
 
                                  
 
                                  Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                                  
-
                                  The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                                  
+
                                  The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                                  
 
                                  
   Development OS:
   
diff --git a/docs/0.17/getting-started/index.html b/docs/0.17/getting-started/index.html
index 4d9429c69d6..b1f464a1dc2 100644
--- a/docs/0.17/getting-started/index.html
+++ b/docs/0.17/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                                  If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                                  
 
                                  
 
                                  Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                                  
-
                                  The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                                  
+
                                  The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                                  
 
                                  
   Development OS:
   
diff --git a/docs/0.17/images.html b/docs/0.17/images.html
index 554e27a6716..438c064260c 100644
--- a/docs/0.17/images.html
+++ b/docs/0.17/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                                  Edit
                                  Images
                                  Static Image Resources
                                  
-
                                  React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                  
+
                                  React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                  
 
                                  <Image source={require('./my-icon.png')} />
 
                                  
 
                                  The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                                  
@@ -88,7 +88,7 @@
 
                                  On Windows, you might need to restart the packager if you add new images to your project.
                                  
 
                                  Here are some benefits that you get:
                                  
 
                                    
-
                                  1. Same system on iOS and Android.
                                    2. 
+
                                  2. Same system on Android and iOS.
                                    3. 
 
                                  3. Images live in the same folder as your JavaScript code. Components are self-contained.
                                    4. 
 
                                  4. No global namespace, i.e. you don't have to worry about name collisions.
                                    5. 
 
                                  5. Only the images that are actually used will be packaged into your app.
                                    6. 
diff --git a/docs/0.17/images/index.html b/docs/0.17/images/index.html
index 554e27a6716..438c064260c 100644
--- a/docs/0.17/images/index.html
+++ b/docs/0.17/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                                  Edit
                                  Images
                                  Static Image Resources
                                  
-
                                  React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                  
+
                                  React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                  
 
                                  <Image source={require('./my-icon.png')} />
 
                                  
 
                                  The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                                  
@@ -88,7 +88,7 @@
 
                                  On Windows, you might need to restart the packager if you add new images to your project.
                                  
 
                                  Here are some benefits that you get:
                                  
 
                                    
-
                                  1. Same system on iOS and Android.
                                    2. 
+
                                  2. Same system on Android and iOS.
                                    3. 
 
                                  3. Images live in the same folder as your JavaScript code. Components are self-contained.
                                    4. 
 
                                  4. No global namespace, i.e. you don't have to worry about name collisions.
                                    5. 
 
                                  5. Only the images that are actually used will be packaged into your app.
                                    6. 
diff --git a/docs/0.17/navigation.html b/docs/0.17/navigation.html
index 36da3612e72..5f390b2e274 100644
--- a/docs/0.17/navigation.html
+++ b/docs/0.17/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                                  Edit
                                  Navigating Between Screens
                                  Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                                  
-
                                  This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                                  
-
                                  If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                  
+
                                  This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                                  
+
                                  If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                  
 
                                  React Navigation
                                  
 
                                  The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                                  
 
                                  The first step is to install in your project:
                                  
diff --git a/docs/0.17/navigation/index.html b/docs/0.17/navigation/index.html
index 36da3612e72..5f390b2e274 100644
--- a/docs/0.17/navigation/index.html
+++ b/docs/0.17/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                                  Edit
                                  Navigating Between Screens
                                  Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                                  
-
                                  This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                                  
-
                                  If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                  
+
                                  This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                                  
+
                                  If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                  
 
                                  React Navigation
                                  
 
                                  The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                                  
 
                                  The first step is to install in your project:
                                  
diff --git a/docs/0.17/navigator.html b/docs/0.17/navigator.html
index e10fd981a0f..f921e75abe4 100644
--- a/docs/0.17/navigator.html
+++ b/docs/0.17/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                                  Edit
                                  Navigator
                                  Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                  
+        
                                  Edit
                                  Navigator
                                  Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                  
 
                                  To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                                  
 
                                  import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.17/navigator/index.html b/docs/0.17/navigator/index.html
index e10fd981a0f..f921e75abe4 100644
--- a/docs/0.17/navigator/index.html
+++ b/docs/0.17/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                                  Edit
                                  Navigator
                                  Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                  
+        
                                  Edit
                                  Navigator
                                  Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                  
 
                                  To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                                  
 
                                  import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.17/picker.html b/docs/0.17/picker.html
index e1dc4d39d8b..dfef3280aaf 100644
--- a/docs/0.17/picker.html
+++ b/docs/0.17/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                                  0.17
                                  Edit
                                  Picker
                                  Renders the native picker component on iOS and Android. Example:
                                  
+        
                                  0.17
                                  Edit
                                  Picker
                                  Renders the native picker component on Android and iOS. Example:
                                  
 
                                  <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.17/picker/index.html b/docs/0.17/picker/index.html
index e1dc4d39d8b..dfef3280aaf 100644
--- a/docs/0.17/picker/index.html
+++ b/docs/0.17/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                                  0.17
                                  Edit
                                  Picker
                                  Renders the native picker component on iOS and Android. Example:
                                  
+        
                                  0.17
                                  Edit
                                  Picker
                                  Renders the native picker component on Android and iOS. Example:
                                  
 
                                  <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.17/platform-specific-code.html b/docs/0.17/platform-specific-code.html
index 596fc2d1704..e70cfafc144 100644
--- a/docs/0.17/platform-specific-code.html
+++ b/docs/0.17/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                                  Edit
                                  Platform Specific Code
                                  When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                                  
+        
                                  Edit
                                  Platform Specific Code
                                  When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                                  
 
                                  React Native provides two ways to organize your code and separate it by platform:
                                  
 
                                    
 
                                  • Using the Platform module.
                                    • 
diff --git a/docs/0.17/platform-specific-code/index.html b/docs/0.17/platform-specific-code/index.html
index 596fc2d1704..e70cfafc144 100644
--- a/docs/0.17/platform-specific-code/index.html
+++ b/docs/0.17/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                                  Edit
                                  Platform Specific Code
                                  When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                                  
+        
                                  Edit
                                  Platform Specific Code
                                  When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                                  
 
                                  React Native provides two ways to organize your code and separate it by platform:
                                  
 
                                    
 
                                  • Using the Platform module.
                                    • 
diff --git a/docs/0.18/accessibility.html b/docs/0.18/accessibility.html
index d9ce502a809..ad82143ac18 100644
--- a/docs/0.18/accessibility.html
+++ b/docs/0.18/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                                  Edit
                                  Accessibility
                                  Native App Accessibility (iOS and Android)
                                  
-
                                  Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                  
+        
                                  Edit
                                  Accessibility
                                  Native App Accessibility (Android and iOS)
                                  
+
                                  Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                  
 
                                  In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                                  
 
                                  Making Apps Accessible
                                  
 
                                  Accessibility properties
                                  
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                                  
-
                                  ← AnimationsImproving User Experience →
                                  Edit
                                  Accessibility
                                  Native App Accessibility (iOS and Android)
                                  
-
                                  Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                  
+        
                                  Edit
                                  Accessibility
                                  Native App Accessibility (Android and iOS)
                                  
+
                                  Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                  
 
                                  In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                                  
 
                                  Making Apps Accessible
                                  
 
                                  Accessibility properties
                                  
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                                  
-
                                  ← AnimationsImproving User Experience →
                                  0.18
                                  Edit
                                  Alert
                                  Use Alert to display an alert dialog.
                                  
-
                                  This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                                  
+
                                  This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                                  
 
                                  Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                                  
 
                                  On iOS, you can specify any number of buttons.
                                  
 
                                  On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                                  
@@ -25,7 +25,7 @@
 
                                  Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                                  
 
                                  Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                                  
 
                                  Example usage:
                                  
-
                                  // Works on both iOS and Android
+
                                  // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.18/alert/index.html b/docs/0.18/alert/index.html
index ca50752bfdd..978f0f66ce1 100644
--- a/docs/0.18/alert/index.html
+++ b/docs/0.18/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
                                  0.18
                                  Edit
                                  Alert
                                  Use Alert to display an alert dialog.
                                  
-
                                  This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                                  
+
                                  This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                                  
 
                                  Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                                  
 
                                  On iOS, you can specify any number of buttons.
                                  
 
                                  On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                                  
@@ -25,7 +25,7 @@
 
                                  Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                                  
 
                                  Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                                  
 
                                  Example usage:
                                  
-
                                  // Works on both iOS and Android
+
                                  // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.18/clipboard.html b/docs/0.18/clipboard.html
index 7f84ceba871..bd2d9bdf529 100644
--- a/docs/0.18/clipboard.html
+++ b/docs/0.18/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                                  0.18
                                  Edit
                                  Clipboard
                                  Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                                  
+        
                                  0.18
                                  Edit
                                  Clipboard
                                  Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                                  
 
                                  Methods
                                  
 
                                    
 
                                  • getString
                                    • 
diff --git a/docs/0.18/clipboard/index.html b/docs/0.18/clipboard/index.html
index 7f84ceba871..bd2d9bdf529 100644
--- a/docs/0.18/clipboard/index.html
+++ b/docs/0.18/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                                    0.18
                                    Edit
                                    Clipboard
                                    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                                    
+        
                                    0.18
                                    Edit
                                    Clipboard
                                    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                                    
 
                                    Methods
                                    
 
                                      
 
                                    • getString
                                      • 
diff --git a/docs/0.18/components-and-apis.html b/docs/0.18/components-and-apis.html
index a24258531a1..56da0571658 100644
--- a/docs/0.18/components-and-apis.html
+++ b/docs/0.18/components-and-apis.html
@@ -130,7 +130,7 @@
   
                                      
     
       
                                      Picker
                                      
-      
                                      Renders the native picker component on iOS and Android.
                                      
+      
                                      Renders the native picker component on Android and iOS.
                                      
                                           
   
                                      
   
                                      
@@ -290,7 +290,7 @@
   
                                      
     
       
                                      Clipboard
                                      
-      
                                      Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                                      
+      
                                      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                                      
                                           
   
                                      
   
                                      
diff --git a/docs/0.18/components-and-apis/index.html b/docs/0.18/components-and-apis/index.html
index a24258531a1..56da0571658 100644
--- a/docs/0.18/components-and-apis/index.html
+++ b/docs/0.18/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                                      
     
       
                                      Picker
                                      
-      
                                      Renders the native picker component on iOS and Android.
                                      
+      
                                      Renders the native picker component on Android and iOS.
                                      
                                           
   
                                      
   
                                      
@@ -290,7 +290,7 @@
   
                                      
     
       
                                      Clipboard
                                      
-      
                                      Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                                      
+      
                                      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                                      
                                           
   
                                      
   
                                      
diff --git a/docs/0.18/getting-started.html b/docs/0.18/getting-started.html
index 032bb2e15a7..16b4411f672 100644
--- a/docs/0.18/getting-started.html
+++ b/docs/0.18/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                                      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                                      
 
                                      
 
                                      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                                      
-
                                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                                      
+
                                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                                      
 
                                      
   Development OS:
   
diff --git a/docs/0.18/getting-started/index.html b/docs/0.18/getting-started/index.html
index 032bb2e15a7..16b4411f672 100644
--- a/docs/0.18/getting-started/index.html
+++ b/docs/0.18/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                                      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                                      
 
                                      
 
                                      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                                      
-
                                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                                      
+
                                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                                      
 
                                      
   Development OS:
   
diff --git a/docs/0.18/images.html b/docs/0.18/images.html
index ef1de6f52cd..2d707502920 100644
--- a/docs/0.18/images.html
+++ b/docs/0.18/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                                      Edit
                                      Images
                                      Static Image Resources
                                      
-
                                      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                      
+
                                      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                      
 
                                      <Image source={require('./my-icon.png')} />
 
                                      
 
                                      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                                      
@@ -88,7 +88,7 @@
 
                                      On Windows, you might need to restart the packager if you add new images to your project.
                                      
 
                                      Here are some benefits that you get:
                                      
 
                                        
-
                                      1. Same system on iOS and Android.
                                        2. 
+
                                      2. Same system on Android and iOS.
                                        3. 
 
                                      3. Images live in the same folder as your JavaScript code. Components are self-contained.
                                        4. 
 
                                      4. No global namespace, i.e. you don't have to worry about name collisions.
                                        5. 
 
                                      5. Only the images that are actually used will be packaged into your app.
                                        6. 
diff --git a/docs/0.18/images/index.html b/docs/0.18/images/index.html
index ef1de6f52cd..2d707502920 100644
--- a/docs/0.18/images/index.html
+++ b/docs/0.18/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                                      Edit
                                      Images
                                      Static Image Resources
                                      
-
                                      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                      
+
                                      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                      
 
                                      <Image source={require('./my-icon.png')} />
 
                                      
 
                                      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                                      
@@ -88,7 +88,7 @@
 
                                      On Windows, you might need to restart the packager if you add new images to your project.
                                      
 
                                      Here are some benefits that you get:
                                      
 
                                        
-
                                      1. Same system on iOS and Android.
                                        2. 
+
                                      2. Same system on Android and iOS.
                                        3. 
 
                                      3. Images live in the same folder as your JavaScript code. Components are self-contained.
                                        4. 
 
                                      4. No global namespace, i.e. you don't have to worry about name collisions.
                                        5. 
 
                                      5. Only the images that are actually used will be packaged into your app.
                                        6. 
diff --git a/docs/0.18/navigation.html b/docs/0.18/navigation.html
index 55d3cdcc97a..a22ac1f595f 100644
--- a/docs/0.18/navigation.html
+++ b/docs/0.18/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                                      Edit
                                      Navigating Between Screens
                                      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                                      
-
                                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                                      
-
                                      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                      
+
                                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                                      
+
                                      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                      
 
                                      React Navigation
                                      
 
                                      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                                      
 
                                      The first step is to install in your project:
                                      
diff --git a/docs/0.18/navigation/index.html b/docs/0.18/navigation/index.html
index 55d3cdcc97a..a22ac1f595f 100644
--- a/docs/0.18/navigation/index.html
+++ b/docs/0.18/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                                      Edit
                                      Navigating Between Screens
                                      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                                      
-
                                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                                      
-
                                      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                      
+
                                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                                      
+
                                      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                      
 
                                      React Navigation
                                      
 
                                      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                                      
 
                                      The first step is to install in your project:
                                      
diff --git a/docs/0.18/navigator.html b/docs/0.18/navigator.html
index 5caae33d055..b22fa4cb3a7 100644
--- a/docs/0.18/navigator.html
+++ b/docs/0.18/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                                      Edit
                                      Navigator
                                      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                      
+        
                                      Edit
                                      Navigator
                                      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                      
 
                                      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                                      
 
                                      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.18/navigator/index.html b/docs/0.18/navigator/index.html
index 5caae33d055..b22fa4cb3a7 100644
--- a/docs/0.18/navigator/index.html
+++ b/docs/0.18/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                                      Edit
                                      Navigator
                                      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                      
+        
                                      Edit
                                      Navigator
                                      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                      
 
                                      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                                      
 
                                      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.18/picker.html b/docs/0.18/picker.html
index c339c5138a7..24b73536d57 100644
--- a/docs/0.18/picker.html
+++ b/docs/0.18/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                                      0.18
                                      Edit
                                      Picker
                                      Renders the native picker component on iOS and Android. Example:
                                      
+        
                                      0.18
                                      Edit
                                      Picker
                                      Renders the native picker component on Android and iOS. Example:
                                      
 
                                      <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.18/picker/index.html b/docs/0.18/picker/index.html
index c339c5138a7..24b73536d57 100644
--- a/docs/0.18/picker/index.html
+++ b/docs/0.18/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                                      0.18
                                      Edit
                                      Picker
                                      Renders the native picker component on iOS and Android. Example:
                                      
+        
                                      0.18
                                      Edit
                                      Picker
                                      Renders the native picker component on Android and iOS. Example:
                                      
 
                                      <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.18/platform-specific-code.html b/docs/0.18/platform-specific-code.html
index f77d2a9c5ab..ea4fae9eb91 100644
--- a/docs/0.18/platform-specific-code.html
+++ b/docs/0.18/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                                      Edit
                                      Platform Specific Code
                                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                                      
+        
                                      Edit
                                      Platform Specific Code
                                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                                      
 
                                      React Native provides two ways to organize your code and separate it by platform:
                                      
 
                                        
 
                                      • Using the Platform module.
                                        • 
diff --git a/docs/0.18/platform-specific-code/index.html b/docs/0.18/platform-specific-code/index.html
index f77d2a9c5ab..ea4fae9eb91 100644
--- a/docs/0.18/platform-specific-code/index.html
+++ b/docs/0.18/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                                      Edit
                                      Platform Specific Code
                                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                                      
+        
                                      Edit
                                      Platform Specific Code
                                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                                      
 
                                      React Native provides two ways to organize your code and separate it by platform:
                                      
 
                                        
 
                                      • Using the Platform module.
                                        • 
diff --git a/docs/0.19/accessibility.html b/docs/0.19/accessibility.html
index c790aa9a56e..cbfeb317a5d 100644
--- a/docs/0.19/accessibility.html
+++ b/docs/0.19/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                                      Edit
                                      Accessibility
                                      Native App Accessibility (iOS and Android)
                                      
-
                                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                      
+        
                                      Edit
                                      Accessibility
                                      Native App Accessibility (Android and iOS)
                                      
+
                                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                      
 
                                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                                      
 
                                      Making Apps Accessible
                                      
 
                                      Accessibility properties
                                      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                                      
-
                                      ← AnimationsImproving User Experience →
                                      Edit
                                      Accessibility
                                      Native App Accessibility (iOS and Android)
                                      
-
                                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                      
+        
                                      Edit
                                      Accessibility
                                      Native App Accessibility (Android and iOS)
                                      
+
                                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                      
 
                                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                                      
 
                                      Making Apps Accessible
                                      
 
                                      Accessibility properties
                                      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                                      
-
                                      ← AnimationsImproving User Experience →
                                      0.19
                                      Edit
                                      Alert
                                      Use Alert to display an alert dialog.
                                      
-
                                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                                      
+
                                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                                      
 
                                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                                      
 
                                      On iOS, you can specify any number of buttons.
                                      
 
                                      On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                                      
@@ -25,7 +25,7 @@
 
                                      Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                                      
 
                                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                                      
 
                                      Example usage:
                                      
-
                                      // Works on both iOS and Android
+
                                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.19/alert/index.html b/docs/0.19/alert/index.html
index d10519ed8d6..171130cf5d8 100644
--- a/docs/0.19/alert/index.html
+++ b/docs/0.19/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
                                      0.19
                                      Edit
                                      Alert
                                      Use Alert to display an alert dialog.
                                      
-
                                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                                      
+
                                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                                      
 
                                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                                      
 
                                      On iOS, you can specify any number of buttons.
                                      
 
                                      On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                                      
@@ -25,7 +25,7 @@
 
                                      Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                                      
 
                                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                                      
 
                                      Example usage:
                                      
-
                                      // Works on both iOS and Android
+
                                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.19/clipboard.html b/docs/0.19/clipboard.html
index 3214aa1401e..3d21ed8230a 100644
--- a/docs/0.19/clipboard.html
+++ b/docs/0.19/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                                      0.19
                                      Edit
                                      Clipboard
                                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                                      
+        
                                      0.19
                                      Edit
                                      Clipboard
                                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                                      
 
                                      Methods
                                      
 
                                        
 
                                      • getString
                                        • 
diff --git a/docs/0.19/clipboard/index.html b/docs/0.19/clipboard/index.html
index 3214aa1401e..3d21ed8230a 100644
--- a/docs/0.19/clipboard/index.html
+++ b/docs/0.19/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                                        0.19
                                        Edit
                                        Clipboard
                                        Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                                        
+        
                                        0.19
                                        Edit
                                        Clipboard
                                        Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                                        
 
                                        Methods
                                        
 
                                          
 
                                        • getString
                                          • 
diff --git a/docs/0.19/components-and-apis.html b/docs/0.19/components-and-apis.html
index eb6caa87675..b6abc17311f 100644
--- a/docs/0.19/components-and-apis.html
+++ b/docs/0.19/components-and-apis.html
@@ -130,7 +130,7 @@
   
                                          
     
       
                                          Picker
                                          
-      
                                          Renders the native picker component on iOS and Android.
                                          
+      
                                          Renders the native picker component on Android and iOS.
                                          
                                               
   
                                          
   
                                          
@@ -290,7 +290,7 @@
   
                                          
     
       
                                          Clipboard
                                          
-      
                                          Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                                          
+      
                                          Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                                          
                                               
   
                                          
   
                                          
diff --git a/docs/0.19/components-and-apis/index.html b/docs/0.19/components-and-apis/index.html
index eb6caa87675..b6abc17311f 100644
--- a/docs/0.19/components-and-apis/index.html
+++ b/docs/0.19/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                                          
     
       
                                          Picker
                                          
-      
                                          Renders the native picker component on iOS and Android.
                                          
+      
                                          Renders the native picker component on Android and iOS.
                                          
                                               
   
                                          
   
                                          
@@ -290,7 +290,7 @@
   
                                          
     
       
                                          Clipboard
                                          
-      
                                          Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                                          
+      
                                          Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                                          
                                               
   
                                          
   
                                          
diff --git a/docs/0.19/getting-started.html b/docs/0.19/getting-started.html
index 340c836f9d9..594278cd3a4 100644
--- a/docs/0.19/getting-started.html
+++ b/docs/0.19/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                                          If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                                          
 
                                          
 
                                          Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                                          
-
                                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                                          
+
                                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                                          
 
                                          
   Development OS:
   
diff --git a/docs/0.19/getting-started/index.html b/docs/0.19/getting-started/index.html
index 340c836f9d9..594278cd3a4 100644
--- a/docs/0.19/getting-started/index.html
+++ b/docs/0.19/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                                          If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                                          
 
                                          
 
                                          Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                                          
-
                                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                                          
+
                                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                                          
 
                                          
   Development OS:
   
diff --git a/docs/0.19/images.html b/docs/0.19/images.html
index 6dd1c6b246b..962bb8c00fe 100644
--- a/docs/0.19/images.html
+++ b/docs/0.19/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                                          Edit
                                          Images
                                          Static Image Resources
                                          
-
                                          React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                          
+
                                          React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                          
 
                                          <Image source={require('./my-icon.png')} />
 
                                          
 
                                          The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                                          
@@ -88,7 +88,7 @@
 
                                          On Windows, you might need to restart the packager if you add new images to your project.
                                          
 
                                          Here are some benefits that you get:
                                          
 
                                            
-
                                          1. Same system on iOS and Android.
                                            2. 
+
                                          2. Same system on Android and iOS.
                                            3. 
 
                                          3. Images live in the same folder as your JavaScript code. Components are self-contained.
                                            4. 
 
                                          4. No global namespace, i.e. you don't have to worry about name collisions.
                                            5. 
 
                                          5. Only the images that are actually used will be packaged into your app.
                                            6. 
diff --git a/docs/0.19/images/index.html b/docs/0.19/images/index.html
index 6dd1c6b246b..962bb8c00fe 100644
--- a/docs/0.19/images/index.html
+++ b/docs/0.19/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                                          Edit
                                          Images
                                          Static Image Resources
                                          
-
                                          React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                          
+
                                          React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                          
 
                                          <Image source={require('./my-icon.png')} />
 
                                          
 
                                          The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                                          
@@ -88,7 +88,7 @@
 
                                          On Windows, you might need to restart the packager if you add new images to your project.
                                          
 
                                          Here are some benefits that you get:
                                          
 
                                            
-
                                          1. Same system on iOS and Android.
                                            2. 
+
                                          2. Same system on Android and iOS.
                                            3. 
 
                                          3. Images live in the same folder as your JavaScript code. Components are self-contained.
                                            4. 
 
                                          4. No global namespace, i.e. you don't have to worry about name collisions.
                                            5. 
 
                                          5. Only the images that are actually used will be packaged into your app.
                                            6. 
diff --git a/docs/0.19/navigation.html b/docs/0.19/navigation.html
index 7deebefff80..d41b2fee8de 100644
--- a/docs/0.19/navigation.html
+++ b/docs/0.19/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                                          Edit
                                          Navigating Between Screens
                                          Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                                          
-
                                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                                          
-
                                          If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                          
+
                                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                                          
+
                                          If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                          
 
                                          React Navigation
                                          
 
                                          The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                                          
 
                                          The first step is to install in your project:
                                          
diff --git a/docs/0.19/navigation/index.html b/docs/0.19/navigation/index.html
index 7deebefff80..d41b2fee8de 100644
--- a/docs/0.19/navigation/index.html
+++ b/docs/0.19/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                                          Edit
                                          Navigating Between Screens
                                          Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                                          
-
                                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                                          
-
                                          If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                          
+
                                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                                          
+
                                          If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                          
 
                                          React Navigation
                                          
 
                                          The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                                          
 
                                          The first step is to install in your project:
                                          
diff --git a/docs/0.19/navigator.html b/docs/0.19/navigator.html
index 92047a1b2c5..f3031e26402 100644
--- a/docs/0.19/navigator.html
+++ b/docs/0.19/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                                          Edit
                                          Navigator
                                          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                          
+        
                                          Edit
                                          Navigator
                                          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                          
 
                                          To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                                          
 
                                          import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.19/navigator/index.html b/docs/0.19/navigator/index.html
index 92047a1b2c5..f3031e26402 100644
--- a/docs/0.19/navigator/index.html
+++ b/docs/0.19/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                                          Edit
                                          Navigator
                                          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                          
+        
                                          Edit
                                          Navigator
                                          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                          
 
                                          To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                                          
 
                                          import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.19/picker.html b/docs/0.19/picker.html
index a03fc954f19..f8c11aec620 100644
--- a/docs/0.19/picker.html
+++ b/docs/0.19/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                                          Edit
                                          Picker
                                          Renders the native picker component on iOS and Android. Example:
                                          
+        
                                          Edit
                                          Picker
                                          Renders the native picker component on Android and iOS. Example:
                                          
 
                                          <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.19/picker/index.html b/docs/0.19/picker/index.html
index a03fc954f19..f8c11aec620 100644
--- a/docs/0.19/picker/index.html
+++ b/docs/0.19/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                                          Edit
                                          Picker
                                          Renders the native picker component on iOS and Android. Example:
                                          
+        
                                          Edit
                                          Picker
                                          Renders the native picker component on Android and iOS. Example:
                                          
 
                                          <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.19/platform-specific-code.html b/docs/0.19/platform-specific-code.html
index cf45ae0838d..20a3faa50a6 100644
--- a/docs/0.19/platform-specific-code.html
+++ b/docs/0.19/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                                          Edit
                                          Platform Specific Code
                                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                                          
+        
                                          Edit
                                          Platform Specific Code
                                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                                          
 
                                          React Native provides two ways to organize your code and separate it by platform:
                                          
 
                                            
 
                                          • Using the Platform module.
                                            • 
diff --git a/docs/0.19/platform-specific-code/index.html b/docs/0.19/platform-specific-code/index.html
index cf45ae0838d..20a3faa50a6 100644
--- a/docs/0.19/platform-specific-code/index.html
+++ b/docs/0.19/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                                          Edit
                                          Platform Specific Code
                                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                                          
+        
                                          Edit
                                          Platform Specific Code
                                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                                          
 
                                          React Native provides two ways to organize your code and separate it by platform:
                                          
 
                                            
 
                                          • Using the Platform module.
                                            • 
diff --git a/docs/0.20/accessibility.html b/docs/0.20/accessibility.html
index 188a684ab86..887ce3f3ad3 100644
--- a/docs/0.20/accessibility.html
+++ b/docs/0.20/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                                          Edit
                                          Accessibility
                                          Native App Accessibility (iOS and Android)
                                          
-
                                          Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                          
+        
                                          Edit
                                          Accessibility
                                          Native App Accessibility (Android and iOS)
                                          
+
                                          Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                          
 
                                          In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                                          
 
                                          Making Apps Accessible
                                          
 
                                          Accessibility properties
                                          
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                                      
-
                                      ← AnimationsImproving User Experience →
                                      Edit
                                      Accessibility
                                      Native App Accessibility (iOS and Android)
                                      
-
                                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                      
+        
                                      Edit
                                      Accessibility
                                      Native App Accessibility (Android and iOS)
                                      
+
                                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                      
 
                                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                                      
 
                                      Making Apps Accessible
                                      
 
                                      Accessibility properties
                                      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                                  
-
                                  ← AnimationsImproving User Experience →
                                  0.20
                                  Edit
                                  Alert
                                  Use Alert to display an alert dialog.
                                  
-
                                  This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                                  
+
                                  This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                                  
 
                                  Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                                  
 
                                  On iOS, you can specify any number of buttons.
                                  
 
                                  On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                                  
@@ -25,7 +25,7 @@
 
                                  Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                                  
 
                                  Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                                  
 
                                  Example usage:
                                  
-
                                  // Works on both iOS and Android
+
                                  // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.20/alert/index.html b/docs/0.20/alert/index.html
index 84553239158..1d76270881e 100644
--- a/docs/0.20/alert/index.html
+++ b/docs/0.20/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
                                  0.20
                                  Edit
                                  Alert
                                  Use Alert to display an alert dialog.
                                  
-
                                  This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                                  
+
                                  This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                                  
 
                                  Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                                  
 
                                  On iOS, you can specify any number of buttons.
                                  
 
                                  On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                                  
@@ -25,7 +25,7 @@
 
                                  Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                                  
 
                                  Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                                  
 
                                  Example usage:
                                  
-
                                  // Works on both iOS and Android
+
                                  // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.20/clipboard.html b/docs/0.20/clipboard.html
index 3f9626722df..b61dab4561e 100644
--- a/docs/0.20/clipboard.html
+++ b/docs/0.20/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                                  Edit
                                  Clipboard
                                  Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                                  
+        
                                  Edit
                                  Clipboard
                                  Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                                  
 
                                  Methods
                                  
 
                                    
 
                                  • getString
                                    • 
diff --git a/docs/0.20/clipboard/index.html b/docs/0.20/clipboard/index.html
index 3f9626722df..b61dab4561e 100644
--- a/docs/0.20/clipboard/index.html
+++ b/docs/0.20/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                                  Edit
                                  Clipboard
                                  Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                                  
+        
                                  Edit
                                  Clipboard
                                  Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                                  
 
                                  Methods
                                  
 
                                    
 
                                  • getString
                                    • 
diff --git a/docs/0.20/components-and-apis.html b/docs/0.20/components-and-apis.html
index 8d16cd5ff10..643df546b23 100644
--- a/docs/0.20/components-and-apis.html
+++ b/docs/0.20/components-and-apis.html
@@ -130,7 +130,7 @@
   
                                    
     
       
                                    Picker
                                    
-      
                                    Renders the native picker component on iOS and Android.
                                    
+      
                                    Renders the native picker component on Android and iOS.
                                    
                                         
   
                                    
   
                                    
@@ -290,7 +290,7 @@
   
                                    
     
       
                                    Clipboard
                                    
-      
                                    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                                    
+      
                                    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                                    
                                         
   
                                    
   
                                    
diff --git a/docs/0.20/components-and-apis/index.html b/docs/0.20/components-and-apis/index.html
index 8d16cd5ff10..643df546b23 100644
--- a/docs/0.20/components-and-apis/index.html
+++ b/docs/0.20/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                                    
     
       
                                    Picker
                                    
-      
                                    Renders the native picker component on iOS and Android.
                                    
+      
                                    Renders the native picker component on Android and iOS.
                                    
                                         
   
                                    
   
                                    
@@ -290,7 +290,7 @@
   
                                    
     
       
                                    Clipboard
                                    
-      
                                    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                                    
+      
                                    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                                    
                                         
   
                                    
   
                                    
diff --git a/docs/0.20/getting-started.html b/docs/0.20/getting-started.html
index 805dc193113..d4b0187def3 100644
--- a/docs/0.20/getting-started.html
+++ b/docs/0.20/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                                    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                                    
 
                                    
 
                                    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                                    
-
                                    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                                    
+
                                    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                                    
 
                                    
   Development OS:
   
diff --git a/docs/0.20/getting-started/index.html b/docs/0.20/getting-started/index.html
index 805dc193113..d4b0187def3 100644
--- a/docs/0.20/getting-started/index.html
+++ b/docs/0.20/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                                    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                                    
 
                                    
 
                                    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                                    
-
                                    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                                    
+
                                    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                                    
 
                                    
   Development OS:
   
diff --git a/docs/0.20/images.html b/docs/0.20/images.html
index 5f163b206ec..e3befbabee4 100644
--- a/docs/0.20/images.html
+++ b/docs/0.20/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                                    Edit
                                    Images
                                    Static Image Resources
                                    
-
                                    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                    
+
                                    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                    
 
                                    <Image source={require('./my-icon.png')} />
 
                                    
 
                                    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                                    
@@ -88,7 +88,7 @@
 
                                    On Windows, you might need to restart the packager if you add new images to your project.
                                    
 
                                    Here are some benefits that you get:
                                    
 
                                      
-
                                    1. Same system on iOS and Android.
                                      2. 
+
                                    2. Same system on Android and iOS.
                                      3. 
 
                                    3. Images live in the same folder as your JavaScript code. Components are self-contained.
                                      4. 
 
                                    4. No global namespace, i.e. you don't have to worry about name collisions.
                                      5. 
 
                                    5. Only the images that are actually used will be packaged into your app.
                                      6. 
diff --git a/docs/0.20/images/index.html b/docs/0.20/images/index.html
index 5f163b206ec..e3befbabee4 100644
--- a/docs/0.20/images/index.html
+++ b/docs/0.20/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                                    Edit
                                    Images
                                    Static Image Resources
                                    
-
                                    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                    
+
                                    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                    
 
                                    <Image source={require('./my-icon.png')} />
 
                                    
 
                                    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                                    
@@ -88,7 +88,7 @@
 
                                    On Windows, you might need to restart the packager if you add new images to your project.
                                    
 
                                    Here are some benefits that you get:
                                    
 
                                      
-
                                    1. Same system on iOS and Android.
                                      2. 
+
                                    2. Same system on Android and iOS.
                                      3. 
 
                                    3. Images live in the same folder as your JavaScript code. Components are self-contained.
                                      4. 
 
                                    4. No global namespace, i.e. you don't have to worry about name collisions.
                                      5. 
 
                                    5. Only the images that are actually used will be packaged into your app.
                                      6. 
diff --git a/docs/0.20/navigation.html b/docs/0.20/navigation.html
index ae515775c2e..b72de0486f8 100644
--- a/docs/0.20/navigation.html
+++ b/docs/0.20/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                                    Edit
                                    Navigating Between Screens
                                    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                                    
-
                                    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                                    
-
                                    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                    
+
                                    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                                    
+
                                    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                    
 
                                    React Navigation
                                    
 
                                    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                                    
 
                                    The first step is to install in your project:
                                    
diff --git a/docs/0.20/navigation/index.html b/docs/0.20/navigation/index.html
index ae515775c2e..b72de0486f8 100644
--- a/docs/0.20/navigation/index.html
+++ b/docs/0.20/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                                    Edit
                                    Navigating Between Screens
                                    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                                    
-
                                    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                                    
-
                                    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                    
+
                                    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                                    
+
                                    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                    
 
                                    React Navigation
                                    
 
                                    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                                    
 
                                    The first step is to install in your project:
                                    
diff --git a/docs/0.20/navigator.html b/docs/0.20/navigator.html
index 307c3fd1f22..ffa1601bae2 100644
--- a/docs/0.20/navigator.html
+++ b/docs/0.20/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                                    Edit
                                    Navigator
                                    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                    
+        
                                    Edit
                                    Navigator
                                    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                    
 
                                    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                                    
 
                                    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.20/navigator/index.html b/docs/0.20/navigator/index.html
index 307c3fd1f22..ffa1601bae2 100644
--- a/docs/0.20/navigator/index.html
+++ b/docs/0.20/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                                    Edit
                                    Navigator
                                    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                    
+        
                                    Edit
                                    Navigator
                                    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                    
 
                                    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                                    
 
                                    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.20/picker.html b/docs/0.20/picker.html
index eb144932db7..c518b30ab99 100644
--- a/docs/0.20/picker.html
+++ b/docs/0.20/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                                    Edit
                                    Picker
                                    Renders the native picker component on iOS and Android. Example:
                                    
+        
                                    Edit
                                    Picker
                                    Renders the native picker component on Android and iOS. Example:
                                    
 
                                    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.20/picker/index.html b/docs/0.20/picker/index.html
index eb144932db7..c518b30ab99 100644
--- a/docs/0.20/picker/index.html
+++ b/docs/0.20/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                                    Edit
                                    Picker
                                    Renders the native picker component on iOS and Android. Example:
                                    
+        
                                    Edit
                                    Picker
                                    Renders the native picker component on Android and iOS. Example:
                                    
 
                                    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.20/platform-specific-code.html b/docs/0.20/platform-specific-code.html
index 1b7c87b38f8..78dafc3e3f0 100644
--- a/docs/0.20/platform-specific-code.html
+++ b/docs/0.20/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                                    Edit
                                    Platform Specific Code
                                    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                                    
+        
                                    Edit
                                    Platform Specific Code
                                    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                                    
 
                                    React Native provides two ways to organize your code and separate it by platform:
                                    
 
                                      
 
                                    • Using the Platform module.
                                      • 
diff --git a/docs/0.20/platform-specific-code/index.html b/docs/0.20/platform-specific-code/index.html
index 1b7c87b38f8..78dafc3e3f0 100644
--- a/docs/0.20/platform-specific-code/index.html
+++ b/docs/0.20/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                                    Edit
                                    Platform Specific Code
                                    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                                    
+        
                                    Edit
                                    Platform Specific Code
                                    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                                    
 
                                    React Native provides two ways to organize your code and separate it by platform:
                                    
 
                                      
 
                                    • Using the Platform module.
                                      • 
diff --git a/docs/0.21/accessibility.html b/docs/0.21/accessibility.html
index 4dc0cec19f7..6df6b9f4c3b 100644
--- a/docs/0.21/accessibility.html
+++ b/docs/0.21/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                                    Edit
                                    Accessibility
                                    Native App Accessibility (iOS and Android)
                                    
-
                                    Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                    
+        
                                    Edit
                                    Accessibility
                                    Native App Accessibility (Android and iOS)
                                    
+
                                    Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                    
 
                                    In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                                    
 
                                    Making Apps Accessible
                                    
 
                                    Accessibility properties
                                    
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                                  
-
                                  ← AnimationsImproving User Experience →
                                  Edit
                                  Accessibility
                                  Native App Accessibility (iOS and Android)
                                  
-
                                  Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                  
+        
                                  Edit
                                  Accessibility
                                  Native App Accessibility (Android and iOS)
                                  
+
                                  Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                  
 
                                  In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                                  
 
                                  Making Apps Accessible
                                  
 
                                  Accessibility properties
                                  
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                              
-
                              ← AnimationsImproving User Experience →
                              0.21
                              Edit
                              Alert
                              Use Alert to display an alert dialog.
                              
-
                              This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                              
+
                              This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                              
 
                              Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                              
 
                              On iOS, you can specify any number of buttons.
                              
 
                              On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                              
@@ -25,7 +25,7 @@
 
                              Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                              
 
                              Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                              
 
                              Example usage:
                              
-
                              // Works on both iOS and Android
+
                              // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.21/alert/index.html b/docs/0.21/alert/index.html
index 4be4136b252..74d97fb8dc2 100644
--- a/docs/0.21/alert/index.html
+++ b/docs/0.21/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
                              0.21
                              Edit
                              Alert
                              Use Alert to display an alert dialog.
                              
-
                              This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                              
+
                              This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                              
 
                              Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                              
 
                              On iOS, you can specify any number of buttons.
                              
 
                              On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                              
@@ -25,7 +25,7 @@
 
                              Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                              
 
                              Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                              
 
                              Example usage:
                              
-
                              // Works on both iOS and Android
+
                              // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.21/clipboard.html b/docs/0.21/clipboard.html
index 4e568546757..8f37d8c3618 100644
--- a/docs/0.21/clipboard.html
+++ b/docs/0.21/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                              Edit
                              Clipboard
                              Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                              
+        
                              Edit
                              Clipboard
                              Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                              
 
                              Methods
                              
 
                                
 
                              • getString
                                • 
diff --git a/docs/0.21/clipboard/index.html b/docs/0.21/clipboard/index.html
index 4e568546757..8f37d8c3618 100644
--- a/docs/0.21/clipboard/index.html
+++ b/docs/0.21/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                              Edit
                              Clipboard
                              Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                              
+        
                              Edit
                              Clipboard
                              Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                              
 
                              Methods
                              
 
                                
 
                              • getString
                                • 
diff --git a/docs/0.21/components-and-apis.html b/docs/0.21/components-and-apis.html
index 23ea7632f46..b5f595333e8 100644
--- a/docs/0.21/components-and-apis.html
+++ b/docs/0.21/components-and-apis.html
@@ -130,7 +130,7 @@
   
                                
     
       
                                Picker
                                
-      
                                Renders the native picker component on iOS and Android.
                                
+      
                                Renders the native picker component on Android and iOS.
                                
                                     
   
                                
   
                                
@@ -290,7 +290,7 @@
   
                                
     
       
                                Clipboard
                                
-      
                                Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                                
+      
                                Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                                
                                     
   
                                
   
                                
diff --git a/docs/0.21/components-and-apis/index.html b/docs/0.21/components-and-apis/index.html
index 23ea7632f46..b5f595333e8 100644
--- a/docs/0.21/components-and-apis/index.html
+++ b/docs/0.21/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                                
     
       
                                Picker
                                
-      
                                Renders the native picker component on iOS and Android.
                                
+      
                                Renders the native picker component on Android and iOS.
                                
                                     
   
                                
   
                                
@@ -290,7 +290,7 @@
   
                                
     
       
                                Clipboard
                                
-      
                                Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                                
+      
                                Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                                
                                     
   
                                
   
                                
diff --git a/docs/0.21/getting-started.html b/docs/0.21/getting-started.html
index b99ed070664..d6409ca6baa 100644
--- a/docs/0.21/getting-started.html
+++ b/docs/0.21/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                                If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                                
 
                                
 
                                Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                                
-
                                The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                                
+
                                The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                                
 
                                
   Development OS:
   
diff --git a/docs/0.21/getting-started/index.html b/docs/0.21/getting-started/index.html
index b99ed070664..d6409ca6baa 100644
--- a/docs/0.21/getting-started/index.html
+++ b/docs/0.21/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                                If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                                
 
                                
 
                                Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                                
-
                                The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                                
+
                                The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                                
 
                                
   Development OS:
   
diff --git a/docs/0.21/images.html b/docs/0.21/images.html
index b0d8baea360..fc9c7f3e92f 100644
--- a/docs/0.21/images.html
+++ b/docs/0.21/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                                Edit
                                Images
                                Static Image Resources
                                
-
                                React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                
+
                                React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                
 
                                <Image source={require('./my-icon.png')} />
 
                                
 
                                The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                                
@@ -88,7 +88,7 @@
 
                                On Windows, you might need to restart the packager if you add new images to your project.
                                
 
                                Here are some benefits that you get:
                                
 
                                  
-
                                1. Same system on iOS and Android.
                                  2. 
+
                                2. Same system on Android and iOS.
                                  3. 
 
                                3. Images live in the same folder as your JavaScript code. Components are self-contained.
                                  4. 
 
                                4. No global namespace, i.e. you don't have to worry about name collisions.
                                  5. 
 
                                5. Only the images that are actually used will be packaged into your app.
                                  6. 
diff --git a/docs/0.21/images/index.html b/docs/0.21/images/index.html
index b0d8baea360..fc9c7f3e92f 100644
--- a/docs/0.21/images/index.html
+++ b/docs/0.21/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                                Edit
                                Images
                                Static Image Resources
                                
-
                                React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                
+
                                React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                
 
                                <Image source={require('./my-icon.png')} />
 
                                
 
                                The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                                
@@ -88,7 +88,7 @@
 
                                On Windows, you might need to restart the packager if you add new images to your project.
                                
 
                                Here are some benefits that you get:
                                
 
                                  
-
                                1. Same system on iOS and Android.
                                  2. 
+
                                2. Same system on Android and iOS.
                                  3. 
 
                                3. Images live in the same folder as your JavaScript code. Components are self-contained.
                                  4. 
 
                                4. No global namespace, i.e. you don't have to worry about name collisions.
                                  5. 
 
                                5. Only the images that are actually used will be packaged into your app.
                                  6. 
diff --git a/docs/0.21/navigation.html b/docs/0.21/navigation.html
index 71035b0a7ad..1028119784e 100644
--- a/docs/0.21/navigation.html
+++ b/docs/0.21/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                                Edit
                                Navigating Between Screens
                                Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                                
-
                                This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                                
-
                                If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                
+
                                This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                                
+
                                If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                
 
                                React Navigation
                                
 
                                The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                                
 
                                The first step is to install in your project:
                                
diff --git a/docs/0.21/navigation/index.html b/docs/0.21/navigation/index.html
index 71035b0a7ad..1028119784e 100644
--- a/docs/0.21/navigation/index.html
+++ b/docs/0.21/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                                Edit
                                Navigating Between Screens
                                Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                                
-
                                This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                                
-
                                If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                
+
                                This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                                
+
                                If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                
 
                                React Navigation
                                
 
                                The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                                
 
                                The first step is to install in your project:
                                
diff --git a/docs/0.21/navigator.html b/docs/0.21/navigator.html
index 945ce28fbdb..126e89a4b5a 100644
--- a/docs/0.21/navigator.html
+++ b/docs/0.21/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                                Edit
                                Navigator
                                Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                
+        
                                Edit
                                Navigator
                                Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                
 
                                To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                                
 
                                import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.21/navigator/index.html b/docs/0.21/navigator/index.html
index 945ce28fbdb..126e89a4b5a 100644
--- a/docs/0.21/navigator/index.html
+++ b/docs/0.21/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                                Edit
                                Navigator
                                Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                
+        
                                Edit
                                Navigator
                                Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                
 
                                To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                                
 
                                import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.21/picker.html b/docs/0.21/picker.html
index e6632382362..8fb001f4ff3 100644
--- a/docs/0.21/picker.html
+++ b/docs/0.21/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                                Edit
                                Picker
                                Renders the native picker component on iOS and Android. Example:
                                
+        
                                Edit
                                Picker
                                Renders the native picker component on Android and iOS. Example:
                                
 
                                <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.21/picker/index.html b/docs/0.21/picker/index.html
index e6632382362..8fb001f4ff3 100644
--- a/docs/0.21/picker/index.html
+++ b/docs/0.21/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                                Edit
                                Picker
                                Renders the native picker component on iOS and Android. Example:
                                
+        
                                Edit
                                Picker
                                Renders the native picker component on Android and iOS. Example:
                                
 
                                <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.21/platform-specific-code.html b/docs/0.21/platform-specific-code.html
index a9187ce2f0d..7a440776e8b 100644
--- a/docs/0.21/platform-specific-code.html
+++ b/docs/0.21/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                                Edit
                                Platform Specific Code
                                When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                                
+        
                                Edit
                                Platform Specific Code
                                When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                                
 
                                React Native provides two ways to organize your code and separate it by platform:
                                
 
                                  
 
                                • Using the Platform module.
                                  • 
diff --git a/docs/0.21/platform-specific-code/index.html b/docs/0.21/platform-specific-code/index.html
index a9187ce2f0d..7a440776e8b 100644
--- a/docs/0.21/platform-specific-code/index.html
+++ b/docs/0.21/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                                Edit
                                Platform Specific Code
                                When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                                
+        
                                Edit
                                Platform Specific Code
                                When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                                
 
                                React Native provides two ways to organize your code and separate it by platform:
                                
 
                                  
 
                                • Using the Platform module.
                                  • 
diff --git a/docs/0.22/accessibility.html b/docs/0.22/accessibility.html
index 39c055340ff..90a6e7d89f5 100644
--- a/docs/0.22/accessibility.html
+++ b/docs/0.22/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                                Edit
                                Accessibility
                                Native App Accessibility (iOS and Android)
                                
-
                                Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                
+        
                                Edit
                                Accessibility
                                Native App Accessibility (Android and iOS)
                                
+
                                Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                
 
                                In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                                
 
                                Making Apps Accessible
                                
 
                                Accessibility properties
                                
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                              
-
                              ← AnimationsImproving User Experience →
                              Edit
                              Accessibility
                              Native App Accessibility (iOS and Android)
                              
-
                              Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                              
+        
                              Edit
                              Accessibility
                              Native App Accessibility (Android and iOS)
                              
+
                              Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                              
 
                              In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                              
 
                              Making Apps Accessible
                              
 
                              Accessibility properties
                              
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                          
-
                          ← AnimationsImproving User Experience →
                          0.22
                          Edit
                          Alert
                          Use Alert to display an alert dialog.
                          
-
                          This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                          
+
                          This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                          
 
                          Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                          
 
                          On iOS, you can specify any number of buttons.
                          
 
                          On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                          
@@ -25,7 +25,7 @@
 
                          Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                          
 
                          Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                          
 
                          Example usage:
                          
-
                          // Works on both iOS and Android
+
                          // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.22/alert/index.html b/docs/0.22/alert/index.html
index 57d69e706c0..55c0ad10d4f 100644
--- a/docs/0.22/alert/index.html
+++ b/docs/0.22/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
                          0.22
                          Edit
                          Alert
                          Use Alert to display an alert dialog.
                          
-
                          This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                          
+
                          This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                          
 
                          Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                          
 
                          On iOS, you can specify any number of buttons.
                          
 
                          On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                          
@@ -25,7 +25,7 @@
 
                          Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                          
 
                          Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                          
 
                          Example usage:
                          
-
                          // Works on both iOS and Android
+
                          // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.22/clipboard.html b/docs/0.22/clipboard.html
index a172e6b3b2f..9c04a0b9064 100644
--- a/docs/0.22/clipboard.html
+++ b/docs/0.22/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                          Edit
                          Clipboard
                          Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                          
+        
                          Edit
                          Clipboard
                          Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                          
 
                          Methods
                          
 
                            
 
                          • getString
                            • 
diff --git a/docs/0.22/clipboard/index.html b/docs/0.22/clipboard/index.html
index a172e6b3b2f..9c04a0b9064 100644
--- a/docs/0.22/clipboard/index.html
+++ b/docs/0.22/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                          Edit
                          Clipboard
                          Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                          
+        
                          Edit
                          Clipboard
                          Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                          
 
                          Methods
                          
 
                            
 
                          • getString
                            • 
diff --git a/docs/0.22/components-and-apis.html b/docs/0.22/components-and-apis.html
index e16ead04199..a48c5066713 100644
--- a/docs/0.22/components-and-apis.html
+++ b/docs/0.22/components-and-apis.html
@@ -130,7 +130,7 @@
   
                            
     
       
                            Picker
                            
-      
                            Renders the native picker component on iOS and Android.
                            
+      
                            Renders the native picker component on Android and iOS.
                            
                                 
   
                            
   
                            
@@ -290,7 +290,7 @@
   
                            
     
       
                            Clipboard
                            
-      
                            Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                            
+      
                            Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                            
                                 
   
                            
   
                            
diff --git a/docs/0.22/components-and-apis/index.html b/docs/0.22/components-and-apis/index.html
index e16ead04199..a48c5066713 100644
--- a/docs/0.22/components-and-apis/index.html
+++ b/docs/0.22/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                            
     
       
                            Picker
                            
-      
                            Renders the native picker component on iOS and Android.
                            
+      
                            Renders the native picker component on Android and iOS.
                            
                                 
   
                            
   
                            
@@ -290,7 +290,7 @@
   
                            
     
       
                            Clipboard
                            
-      
                            Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                            
+      
                            Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                            
                                 
   
                            
   
                            
diff --git a/docs/0.22/getting-started.html b/docs/0.22/getting-started.html
index 9702625614e..292a1a2c37a 100644
--- a/docs/0.22/getting-started.html
+++ b/docs/0.22/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                            If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                            
 
                            
 
                            Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                            
-
                            The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                            
+
                            The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                            
 
                            
   Development OS:
   
diff --git a/docs/0.22/getting-started/index.html b/docs/0.22/getting-started/index.html
index 9702625614e..292a1a2c37a 100644
--- a/docs/0.22/getting-started/index.html
+++ b/docs/0.22/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                            If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                            
 
                            
 
                            Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                            
-
                            The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                            
+
                            The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                            
 
                            
   Development OS:
   
diff --git a/docs/0.22/images.html b/docs/0.22/images.html
index 352aac056fd..370c64a493c 100644
--- a/docs/0.22/images.html
+++ b/docs/0.22/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                            Edit
                            Images
                            Static Image Resources
                            
-
                            React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                            
+
                            React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                            
 
                            <Image source={require('./my-icon.png')} />
 
                            
 
                            The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                            
@@ -88,7 +88,7 @@
 
                            On Windows, you might need to restart the packager if you add new images to your project.
                            
 
                            Here are some benefits that you get:
                            
 
                              
-
                            1. Same system on iOS and Android.
                              2. 
+
                            2. Same system on Android and iOS.
                              3. 
 
                            3. Images live in the same folder as your JavaScript code. Components are self-contained.
                              4. 
 
                            4. No global namespace, i.e. you don't have to worry about name collisions.
                              5. 
 
                            5. Only the images that are actually used will be packaged into your app.
                              6. 
diff --git a/docs/0.22/images/index.html b/docs/0.22/images/index.html
index 352aac056fd..370c64a493c 100644
--- a/docs/0.22/images/index.html
+++ b/docs/0.22/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                            Edit
                            Images
                            Static Image Resources
                            
-
                            React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                            
+
                            React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                            
 
                            <Image source={require('./my-icon.png')} />
 
                            
 
                            The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                            
@@ -88,7 +88,7 @@
 
                            On Windows, you might need to restart the packager if you add new images to your project.
                            
 
                            Here are some benefits that you get:
                            
 
                              
-
                            1. Same system on iOS and Android.
                              2. 
+
                            2. Same system on Android and iOS.
                              3. 
 
                            3. Images live in the same folder as your JavaScript code. Components are self-contained.
                              4. 
 
                            4. No global namespace, i.e. you don't have to worry about name collisions.
                              5. 
 
                            5. Only the images that are actually used will be packaged into your app.
                              6. 
diff --git a/docs/0.22/navigation.html b/docs/0.22/navigation.html
index fe73b553f59..cdb5e675270 100644
--- a/docs/0.22/navigation.html
+++ b/docs/0.22/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                            Edit
                            Navigating Between Screens
                            Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                            
-
                            This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                            
-
                            If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                            
+
                            This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                            
+
                            If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                            
 
                            React Navigation
                            
 
                            The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                            
 
                            The first step is to install in your project:
                            
diff --git a/docs/0.22/navigation/index.html b/docs/0.22/navigation/index.html
index fe73b553f59..cdb5e675270 100644
--- a/docs/0.22/navigation/index.html
+++ b/docs/0.22/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                            Edit
                            Navigating Between Screens
                            Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                            
-
                            This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                            
-
                            If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                            
+
                            This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                            
+
                            If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                            
 
                            React Navigation
                            
 
                            The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                            
 
                            The first step is to install in your project:
                            
diff --git a/docs/0.22/navigator.html b/docs/0.22/navigator.html
index fb19ac8f505..361ca691dde 100644
--- a/docs/0.22/navigator.html
+++ b/docs/0.22/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                            Edit
                            Navigator
                            Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                            
+        
                            Edit
                            Navigator
                            Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                            
 
                            To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                            
 
                            import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.22/navigator/index.html b/docs/0.22/navigator/index.html
index fb19ac8f505..361ca691dde 100644
--- a/docs/0.22/navigator/index.html
+++ b/docs/0.22/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                            Edit
                            Navigator
                            Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                            
+        
                            Edit
                            Navigator
                            Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                            
 
                            To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                            
 
                            import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.22/picker.html b/docs/0.22/picker.html
index e50922f13e4..7e29d568ffd 100644
--- a/docs/0.22/picker.html
+++ b/docs/0.22/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                            Edit
                            Picker
                            Renders the native picker component on iOS and Android. Example:
                            
+        
                            Edit
                            Picker
                            Renders the native picker component on Android and iOS. Example:
                            
 
                            <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.22/picker/index.html b/docs/0.22/picker/index.html
index e50922f13e4..7e29d568ffd 100644
--- a/docs/0.22/picker/index.html
+++ b/docs/0.22/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                            Edit
                            Picker
                            Renders the native picker component on iOS and Android. Example:
                            
+        
                            Edit
                            Picker
                            Renders the native picker component on Android and iOS. Example:
                            
 
                            <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.22/platform-specific-code.html b/docs/0.22/platform-specific-code.html
index 70ef33dda2e..1e2b888c101 100644
--- a/docs/0.22/platform-specific-code.html
+++ b/docs/0.22/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                            Edit
                            Platform Specific Code
                            When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                            
+        
                            Edit
                            Platform Specific Code
                            When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                            
 
                            React Native provides two ways to organize your code and separate it by platform:
                            
 
                              
 
                            • Using the Platform module.
                              • 
diff --git a/docs/0.22/platform-specific-code/index.html b/docs/0.22/platform-specific-code/index.html
index 70ef33dda2e..1e2b888c101 100644
--- a/docs/0.22/platform-specific-code/index.html
+++ b/docs/0.22/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                            Edit
                            Platform Specific Code
                            When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                            
+        
                            Edit
                            Platform Specific Code
                            When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                            
 
                            React Native provides two ways to organize your code and separate it by platform:
                            
 
                              
 
                            • Using the Platform module.
                              • 
diff --git a/docs/0.23/accessibility.html b/docs/0.23/accessibility.html
index 4e6a4944c44..47233399df7 100644
--- a/docs/0.23/accessibility.html
+++ b/docs/0.23/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                            Edit
                            Accessibility
                            Native App Accessibility (iOS and Android)
                            
-
                            Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                            
+        
                            Edit
                            Accessibility
                            Native App Accessibility (Android and iOS)
                            
+
                            Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                            
 
                            In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                            
 
                            Making Apps Accessible
                            
 
                            Accessibility properties
                            
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                          
-
                          ← AnimationsImproving User Experience →
                          Edit
                          Accessibility
                          Native App Accessibility (iOS and Android)
                          
-
                          Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                          
+        
                          Edit
                          Accessibility
                          Native App Accessibility (Android and iOS)
                          
+
                          Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                          
 
                          In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                          
 
                          Making Apps Accessible
                          
 
                          Accessibility properties
                          
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                      
-
                      ← AnimationsImproving User Experience →
                      0.23
                      Edit
                      Alert
                      Use Alert to display an alert dialog.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                      
 
                      On iOS, you can specify any number of buttons.
                      
 
                      On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                      
@@ -25,7 +25,7 @@
 
                      Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                      
 
                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                      
 
                      Example usage:
                      
-
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.23/alert/index.html b/docs/0.23/alert/index.html
index 2d727927974..8c0abd72ef2 100644
--- a/docs/0.23/alert/index.html
+++ b/docs/0.23/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
                      0.23
                      Edit
                      Alert
                      Use Alert to display an alert dialog.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                      
 
                      On iOS, you can specify any number of buttons.
                      
 
                      On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                      
@@ -25,7 +25,7 @@
 
                      Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                      
 
                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                      
 
                      Example usage:
                      
-
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.23/clipboard.html b/docs/0.23/clipboard.html
index 3c4ad50b84e..363bb1a8165 100644
--- a/docs/0.23/clipboard.html
+++ b/docs/0.23/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.23/clipboard/index.html b/docs/0.23/clipboard/index.html
index 3c4ad50b84e..363bb1a8165 100644
--- a/docs/0.23/clipboard/index.html
+++ b/docs/0.23/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.23/components-and-apis.html b/docs/0.23/components-and-apis.html
index c581eb0f174..3c6a72d61d4 100644
--- a/docs/0.23/components-and-apis.html
+++ b/docs/0.23/components-and-apis.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.23/components-and-apis/index.html b/docs/0.23/components-and-apis/index.html
index c581eb0f174..3c6a72d61d4 100644
--- a/docs/0.23/components-and-apis/index.html
+++ b/docs/0.23/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.23/getting-started.html b/docs/0.23/getting-started.html
index 540d4ba4289..47528532b83 100644
--- a/docs/0.23/getting-started.html
+++ b/docs/0.23/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.23/getting-started/index.html b/docs/0.23/getting-started/index.html
index 540d4ba4289..47528532b83 100644
--- a/docs/0.23/getting-started/index.html
+++ b/docs/0.23/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.23/images.html b/docs/0.23/images.html
index 145e9601116..0ba725822d1 100644
--- a/docs/0.23/images.html
+++ b/docs/0.23/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.23/images/index.html b/docs/0.23/images/index.html
index 145e9601116..0ba725822d1 100644
--- a/docs/0.23/images/index.html
+++ b/docs/0.23/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.23/navigation.html b/docs/0.23/navigation.html
index 5fa294d0905..828e9820ab4 100644
--- a/docs/0.23/navigation.html
+++ b/docs/0.23/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.23/navigation/index.html b/docs/0.23/navigation/index.html
index 5fa294d0905..828e9820ab4 100644
--- a/docs/0.23/navigation/index.html
+++ b/docs/0.23/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.23/navigator.html b/docs/0.23/navigator.html
index 528c5cc1622..e13741d9465 100644
--- a/docs/0.23/navigator.html
+++ b/docs/0.23/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                        Edit
                        Navigator
                        Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                        
+        
                        Edit
                        Navigator
                        Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                        
 
                        To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                        
 
                        import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.23/navigator/index.html b/docs/0.23/navigator/index.html
index 528c5cc1622..e13741d9465 100644
--- a/docs/0.23/navigator/index.html
+++ b/docs/0.23/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                        Edit
                        Navigator
                        Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                        
+        
                        Edit
                        Navigator
                        Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                        
 
                        To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                        
 
                        import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.23/picker.html b/docs/0.23/picker.html
index 9ae3c1fa2ab..155960f2c47 100644
--- a/docs/0.23/picker.html
+++ b/docs/0.23/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.23/picker/index.html b/docs/0.23/picker/index.html
index 9ae3c1fa2ab..155960f2c47 100644
--- a/docs/0.23/picker/index.html
+++ b/docs/0.23/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.23/platform-specific-code.html b/docs/0.23/platform-specific-code.html
index 947931ffcf0..8a66bf9cf04 100644
--- a/docs/0.23/platform-specific-code.html
+++ b/docs/0.23/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.23/platform-specific-code/index.html b/docs/0.23/platform-specific-code/index.html
index 947931ffcf0..8a66bf9cf04 100644
--- a/docs/0.23/platform-specific-code/index.html
+++ b/docs/0.23/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.24/accessibility.html b/docs/0.24/accessibility.html
index 89a5f81624d..8bb7796d8fb 100644
--- a/docs/0.24/accessibility.html
+++ b/docs/0.24/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                        Edit
                        Accessibility
                        Native App Accessibility (iOS and Android)
                        
-
                        Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
+        
                        Edit
                        Accessibility
                        Native App Accessibility (Android and iOS)
                        
+
                        Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
 
                        In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                        
 
                        Making Apps Accessible
                        
 
                        Accessibility properties
                        
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                      
-
                      ← AnimationsImproving User Experience →
                      Edit
                      Accessibility
                      Native App Accessibility (iOS and Android)
                      
-
                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
+        
                      Edit
                      Accessibility
                      Native App Accessibility (Android and iOS)
                      
+
                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
 
                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                      
 
                      Making Apps Accessible
                      
 
                      Accessibility properties
                      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                  
-
                  ← AnimationsImproving User Experience →
                  0.24
                  Edit
                  Alert
                  Use Alert to display an alert dialog.
                  
-
                  This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                  
+
                  This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                  
 
                  Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                  
 
                  On iOS, you can specify any number of buttons.
                  
 
                  On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                  
@@ -25,7 +25,7 @@
 
                  Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                  
 
                  Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                  
 
                  Example usage:
                  
-
                  // Works on both iOS and Android
+
                  // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.24/alert/index.html b/docs/0.24/alert/index.html
index f3fb8da9286..f6966e0c4a8 100644
--- a/docs/0.24/alert/index.html
+++ b/docs/0.24/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
                  0.24
                  Edit
                  Alert
                  Use Alert to display an alert dialog.
                  
-
                  This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                  
+
                  This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                  
 
                  Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                  
 
                  On iOS, you can specify any number of buttons.
                  
 
                  On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                  
@@ -25,7 +25,7 @@
 
                  Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                  
 
                  Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                  
 
                  Example usage:
                  
-
                  // Works on both iOS and Android
+
                  // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.24/clipboard.html b/docs/0.24/clipboard.html
index 3cb755c06c2..86de5a41158 100644
--- a/docs/0.24/clipboard.html
+++ b/docs/0.24/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                  Edit
                  Clipboard
                  Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                  
+        
                  Edit
                  Clipboard
                  Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                  
 
                  Methods
                  
 
                    
 
                  • getString
                    • 
diff --git a/docs/0.24/clipboard/index.html b/docs/0.24/clipboard/index.html
index 3cb755c06c2..86de5a41158 100644
--- a/docs/0.24/clipboard/index.html
+++ b/docs/0.24/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                  Edit
                  Clipboard
                  Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                  
+        
                  Edit
                  Clipboard
                  Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                  
 
                  Methods
                  
 
                    
 
                  • getString
                    • 
diff --git a/docs/0.24/components-and-apis.html b/docs/0.24/components-and-apis.html
index 9db0711818b..68a6b62cd24 100644
--- a/docs/0.24/components-and-apis.html
+++ b/docs/0.24/components-and-apis.html
@@ -130,7 +130,7 @@
   
                    
     
       
                    Picker
                    
-      
                    Renders the native picker component on iOS and Android.
                    
+      
                    Renders the native picker component on Android and iOS.
                    
                         
   
                    
   
                    
@@ -290,7 +290,7 @@
   
                    
     
       
                    Clipboard
                    
-      
                    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                    
+      
                    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                    
                         
   
                    
   
                    
diff --git a/docs/0.24/components-and-apis/index.html b/docs/0.24/components-and-apis/index.html
index 9db0711818b..68a6b62cd24 100644
--- a/docs/0.24/components-and-apis/index.html
+++ b/docs/0.24/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                    
     
       
                    Picker
                    
-      
                    Renders the native picker component on iOS and Android.
                    
+      
                    Renders the native picker component on Android and iOS.
                    
                         
   
                    
   
                    
@@ -290,7 +290,7 @@
   
                    
     
       
                    Clipboard
                    
-      
                    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                    
+      
                    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                    
                         
   
                    
   
                    
diff --git a/docs/0.24/getting-started.html b/docs/0.24/getting-started.html
index a6e1d9e7a71..feb2c76f1da 100644
--- a/docs/0.24/getting-started.html
+++ b/docs/0.24/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                    
 
                    
 
                    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                    
-
                    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                    
+
                    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                    
 
                    
   Development OS:
   
diff --git a/docs/0.24/getting-started/index.html b/docs/0.24/getting-started/index.html
index a6e1d9e7a71..feb2c76f1da 100644
--- a/docs/0.24/getting-started/index.html
+++ b/docs/0.24/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                    
 
                    
 
                    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                    
-
                    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                    
+
                    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                    
 
                    
   Development OS:
   
diff --git a/docs/0.24/images.html b/docs/0.24/images.html
index 2f29a8fe7bb..bd517ada057 100644
--- a/docs/0.24/images.html
+++ b/docs/0.24/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                    Edit
                    Images
                    Static Image Resources
                    
-
                    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                    
+
                    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                    
 
                    <Image source={require('./my-icon.png')} />
 
                    
 
                    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                    
@@ -88,7 +88,7 @@
 
                    On Windows, you might need to restart the packager if you add new images to your project.
                    
 
                    Here are some benefits that you get:
                    
 
                      
-
                    1. Same system on iOS and Android.
                      2. 
+
                    2. Same system on Android and iOS.
                      3. 
 
                    3. Images live in the same folder as your JavaScript code. Components are self-contained.
                      4. 
 
                    4. No global namespace, i.e. you don't have to worry about name collisions.
                      5. 
 
                    5. Only the images that are actually used will be packaged into your app.
                      6. 
diff --git a/docs/0.24/images/index.html b/docs/0.24/images/index.html
index 2f29a8fe7bb..bd517ada057 100644
--- a/docs/0.24/images/index.html
+++ b/docs/0.24/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                    Edit
                    Images
                    Static Image Resources
                    
-
                    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                    
+
                    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                    
 
                    <Image source={require('./my-icon.png')} />
 
                    
 
                    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                    
@@ -88,7 +88,7 @@
 
                    On Windows, you might need to restart the packager if you add new images to your project.
                    
 
                    Here are some benefits that you get:
                    
 
                      
-
                    1. Same system on iOS and Android.
                      2. 
+
                    2. Same system on Android and iOS.
                      3. 
 
                    3. Images live in the same folder as your JavaScript code. Components are self-contained.
                      4. 
 
                    4. No global namespace, i.e. you don't have to worry about name collisions.
                      5. 
 
                    5. Only the images that are actually used will be packaged into your app.
                      6. 
diff --git a/docs/0.24/navigation.html b/docs/0.24/navigation.html
index 226bc2e9d02..089ffb60bc2 100644
--- a/docs/0.24/navigation.html
+++ b/docs/0.24/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                    Edit
                    Navigating Between Screens
                    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                    
-
                    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                    
-
                    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                    
+
                    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                    
+
                    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                    
 
                    React Navigation
                    
 
                    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                    
 
                    The first step is to install in your project:
                    
diff --git a/docs/0.24/navigation/index.html b/docs/0.24/navigation/index.html
index 226bc2e9d02..089ffb60bc2 100644
--- a/docs/0.24/navigation/index.html
+++ b/docs/0.24/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                    Edit
                    Navigating Between Screens
                    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                    
-
                    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                    
-
                    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                    
+
                    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                    
+
                    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                    
 
                    React Navigation
                    
 
                    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                    
 
                    The first step is to install in your project:
                    
diff --git a/docs/0.24/navigator.html b/docs/0.24/navigator.html
index a076f87ba2d..3d9713022ef 100644
--- a/docs/0.24/navigator.html
+++ b/docs/0.24/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                    Edit
                    Navigator
                    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                    
+        
                    Edit
                    Navigator
                    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                    
 
                    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                    
 
                    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.24/navigator/index.html b/docs/0.24/navigator/index.html
index a076f87ba2d..3d9713022ef 100644
--- a/docs/0.24/navigator/index.html
+++ b/docs/0.24/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                    Edit
                    Navigator
                    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                    
+        
                    Edit
                    Navigator
                    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                    
 
                    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                    
 
                    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.24/picker.html b/docs/0.24/picker.html
index 3cbaf163075..f022ab1d98d 100644
--- a/docs/0.24/picker.html
+++ b/docs/0.24/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                    Edit
                    Picker
                    Renders the native picker component on iOS and Android. Example:
                    
+        
                    Edit
                    Picker
                    Renders the native picker component on Android and iOS. Example:
                    
 
                    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.24/picker/index.html b/docs/0.24/picker/index.html
index 3cbaf163075..f022ab1d98d 100644
--- a/docs/0.24/picker/index.html
+++ b/docs/0.24/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                    Edit
                    Picker
                    Renders the native picker component on iOS and Android. Example:
                    
+        
                    Edit
                    Picker
                    Renders the native picker component on Android and iOS. Example:
                    
 
                    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.24/platform-specific-code.html b/docs/0.24/platform-specific-code.html
index 8b496dce90e..bbee9d211de 100644
--- a/docs/0.24/platform-specific-code.html
+++ b/docs/0.24/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                    Edit
                    Platform Specific Code
                    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                    
+        
                    Edit
                    Platform Specific Code
                    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                    
 
                    React Native provides two ways to organize your code and separate it by platform:
                    
 
                      
 
                    • Using the Platform module.
                      • 
diff --git a/docs/0.24/platform-specific-code/index.html b/docs/0.24/platform-specific-code/index.html
index 8b496dce90e..bbee9d211de 100644
--- a/docs/0.24/platform-specific-code/index.html
+++ b/docs/0.24/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                    Edit
                    Platform Specific Code
                    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                    
+        
                    Edit
                    Platform Specific Code
                    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                    
 
                    React Native provides two ways to organize your code and separate it by platform:
                    
 
                      
 
                    • Using the Platform module.
                      • 
diff --git a/docs/0.25/accessibility.html b/docs/0.25/accessibility.html
index 0f247f6f259..f4f1261a16c 100644
--- a/docs/0.25/accessibility.html
+++ b/docs/0.25/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                    Edit
                    Accessibility
                    Native App Accessibility (iOS and Android)
                    
-
                    Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                    
+        
                    Edit
                    Accessibility
                    Native App Accessibility (Android and iOS)
                    
+
                    Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                    
 
                    In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                    
 
                    Making Apps Accessible
                    
 
                    Accessibility properties
                    
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                  
-
                  ← AnimationsImproving User Experience →
                  Edit
                  Accessibility
                  Native App Accessibility (iOS and Android)
                  
-
                  Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                  
+        
                  Edit
                  Accessibility
                  Native App Accessibility (Android and iOS)
                  
+
                  Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                  
 
                  In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                  
 
                  Making Apps Accessible
                  
 
                  Accessibility properties
                  
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
              
-
              ← AnimationsImproving User Experience →
              0.25
              Edit
              Alert
              Use Alert to display an alert dialog.
              
-
              This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
              
+
              This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
              
 
              Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
              
 
              On iOS, you can specify any number of buttons.
              
 
              On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
              
@@ -25,7 +25,7 @@
 
              Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
              
 
              Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
              
 
              Example usage:
              
-
              // Works on both iOS and Android
+
              // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.25/alert/index.html b/docs/0.25/alert/index.html
index 63bfe314507..892fdd0e671 100644
--- a/docs/0.25/alert/index.html
+++ b/docs/0.25/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
              0.25
              Edit
              Alert
              Use Alert to display an alert dialog.
              
-
              This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
              
+
              This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
              
 
              Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
              
 
              On iOS, you can specify any number of buttons.
              
 
              On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
              
@@ -25,7 +25,7 @@
 
              Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
              
 
              Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
              
 
              Example usage:
              
-
              // Works on both iOS and Android
+
              // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.25/clipboard.html b/docs/0.25/clipboard.html
index ccd8c07ed35..9de994a90a6 100644
--- a/docs/0.25/clipboard.html
+++ b/docs/0.25/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
              Edit
              Clipboard
              Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
              
+        
              Edit
              Clipboard
              Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
              
 
              Methods
              
 
                
 
              • getString
                • 
diff --git a/docs/0.25/clipboard/index.html b/docs/0.25/clipboard/index.html
index ccd8c07ed35..9de994a90a6 100644
--- a/docs/0.25/clipboard/index.html
+++ b/docs/0.25/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
              Edit
              Clipboard
              Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
              
+        
              Edit
              Clipboard
              Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
              
 
              Methods
              
 
                
 
              • getString
                • 
diff --git a/docs/0.25/components-and-apis.html b/docs/0.25/components-and-apis.html
index 2001a6da664..328c76dcc47 100644
--- a/docs/0.25/components-and-apis.html
+++ b/docs/0.25/components-and-apis.html
@@ -130,7 +130,7 @@
   
                
     
       
                Picker
                
-      
                Renders the native picker component on iOS and Android.
                
+      
                Renders the native picker component on Android and iOS.
                
                     
   
                
   
                
@@ -290,7 +290,7 @@
   
                
     
       
                Clipboard
                
-      
                Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                
+      
                Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                
                     
   
                
   
                
diff --git a/docs/0.25/components-and-apis/index.html b/docs/0.25/components-and-apis/index.html
index 2001a6da664..328c76dcc47 100644
--- a/docs/0.25/components-and-apis/index.html
+++ b/docs/0.25/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                
     
       
                Picker
                
-      
                Renders the native picker component on iOS and Android.
                
+      
                Renders the native picker component on Android and iOS.
                
                     
   
                
   
                
@@ -290,7 +290,7 @@
   
                
     
       
                Clipboard
                
-      
                Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                
+      
                Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                
                     
   
                
   
                
diff --git a/docs/0.25/getting-started.html b/docs/0.25/getting-started.html
index 598f0784143..48d98d3a67a 100644
--- a/docs/0.25/getting-started.html
+++ b/docs/0.25/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                
 
                
 
                Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                
-
                The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                
+
                The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                
 
                
   Development OS:
   
diff --git a/docs/0.25/getting-started/index.html b/docs/0.25/getting-started/index.html
index 598f0784143..48d98d3a67a 100644
--- a/docs/0.25/getting-started/index.html
+++ b/docs/0.25/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                
 
                
 
                Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                
-
                The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                
+
                The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                
 
                
   Development OS:
   
diff --git a/docs/0.25/images.html b/docs/0.25/images.html
index 0e3c4793df3..403676ee1c7 100644
--- a/docs/0.25/images.html
+++ b/docs/0.25/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                Edit
                Images
                Static Image Resources
                
-
                React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                
+
                React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                
 
                <Image source={require('./my-icon.png')} />
 
                
 
                The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                
@@ -88,7 +88,7 @@
 
                On Windows, you might need to restart the packager if you add new images to your project.
                
 
                Here are some benefits that you get:
                
 
                  
-
                1. Same system on iOS and Android.
                  2. 
+
                2. Same system on Android and iOS.
                  3. 
 
                3. Images live in the same folder as your JavaScript code. Components are self-contained.
                  4. 
 
                4. No global namespace, i.e. you don't have to worry about name collisions.
                  5. 
 
                5. Only the images that are actually used will be packaged into your app.
                  6. 
diff --git a/docs/0.25/images/index.html b/docs/0.25/images/index.html
index 0e3c4793df3..403676ee1c7 100644
--- a/docs/0.25/images/index.html
+++ b/docs/0.25/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                Edit
                Images
                Static Image Resources
                
-
                React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                
+
                React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                
 
                <Image source={require('./my-icon.png')} />
 
                
 
                The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                
@@ -88,7 +88,7 @@
 
                On Windows, you might need to restart the packager if you add new images to your project.
                
 
                Here are some benefits that you get:
                
 
                  
-
                1. Same system on iOS and Android.
                  2. 
+
                2. Same system on Android and iOS.
                  3. 
 
                3. Images live in the same folder as your JavaScript code. Components are self-contained.
                  4. 
 
                4. No global namespace, i.e. you don't have to worry about name collisions.
                  5. 
 
                5. Only the images that are actually used will be packaged into your app.
                  6. 
diff --git a/docs/0.25/navigation.html b/docs/0.25/navigation.html
index a01b11541ed..6fe749244c4 100644
--- a/docs/0.25/navigation.html
+++ b/docs/0.25/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                Edit
                Navigating Between Screens
                Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                
-
                This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                
-
                If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                
+
                This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                
+
                If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                
 
                React Navigation
                
 
                The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                
 
                The first step is to install in your project:
                
diff --git a/docs/0.25/navigation/index.html b/docs/0.25/navigation/index.html
index a01b11541ed..6fe749244c4 100644
--- a/docs/0.25/navigation/index.html
+++ b/docs/0.25/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                Edit
                Navigating Between Screens
                Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                
-
                This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                
-
                If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                
+
                This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                
+
                If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                
 
                React Navigation
                
 
                The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                
 
                The first step is to install in your project:
                
diff --git a/docs/0.25/navigator.html b/docs/0.25/navigator.html
index fce3170694d..3dada1d1d45 100644
--- a/docs/0.25/navigator.html
+++ b/docs/0.25/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                Edit
                Navigator
                Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                
+        
                Edit
                Navigator
                Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                
 
                To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                
 
                import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.25/navigator/index.html b/docs/0.25/navigator/index.html
index fce3170694d..3dada1d1d45 100644
--- a/docs/0.25/navigator/index.html
+++ b/docs/0.25/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                Edit
                Navigator
                Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                
+        
                Edit
                Navigator
                Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                
 
                To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                
 
                import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.25/picker.html b/docs/0.25/picker.html
index 102de304104..55d7ac76cb2 100644
--- a/docs/0.25/picker.html
+++ b/docs/0.25/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                Edit
                Picker
                Renders the native picker component on iOS and Android. Example:
                
+        
                Edit
                Picker
                Renders the native picker component on Android and iOS. Example:
                
 
                <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.25/picker/index.html b/docs/0.25/picker/index.html
index 102de304104..55d7ac76cb2 100644
--- a/docs/0.25/picker/index.html
+++ b/docs/0.25/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                Edit
                Picker
                Renders the native picker component on iOS and Android. Example:
                
+        
                Edit
                Picker
                Renders the native picker component on Android and iOS. Example:
                
 
                <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.25/platform-specific-code.html b/docs/0.25/platform-specific-code.html
index 04be00bcb2a..70de3c13e0e 100644
--- a/docs/0.25/platform-specific-code.html
+++ b/docs/0.25/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                Edit
                Platform Specific Code
                When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                
+        
                Edit
                Platform Specific Code
                When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                
 
                React Native provides two ways to organize your code and separate it by platform:
                
 
                  
 
                • Using the Platform module.
                  • 
diff --git a/docs/0.25/platform-specific-code/index.html b/docs/0.25/platform-specific-code/index.html
index 04be00bcb2a..70de3c13e0e 100644
--- a/docs/0.25/platform-specific-code/index.html
+++ b/docs/0.25/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                Edit
                Platform Specific Code
                When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                
+        
                Edit
                Platform Specific Code
                When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                
 
                React Native provides two ways to organize your code and separate it by platform:
                
 
                  
 
                • Using the Platform module.
                  • 
diff --git a/docs/0.26/accessibility.html b/docs/0.26/accessibility.html
index a4f6dc15e7e..cf2381cfcff 100644
--- a/docs/0.26/accessibility.html
+++ b/docs/0.26/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                Edit
                Accessibility
                Native App Accessibility (iOS and Android)
                
-
                Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                
+        
                Edit
                Accessibility
                Native App Accessibility (Android and iOS)
                
+
                Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                
 
                In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                
 
                Making Apps Accessible
                
 
                Accessibility properties
                
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
              
-
              ← AnimationsImproving User Experience →
              Edit
              Accessibility
              Native App Accessibility (iOS and Android)
              
-
              Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
              
+        
              Edit
              Accessibility
              Native App Accessibility (Android and iOS)
              
+
              Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
              
 
              In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
              
 
              Making Apps Accessible
              
 
              Accessibility properties
              
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
          
-
          ← AnimationsImproving User Experience →
          0.26
          Edit
          Alert
          Use Alert to display an alert dialog.
          
-
          This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
          
+
          This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
          
 
          Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
          
 
          On iOS, you can specify any number of buttons.
          
 
          On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
          
@@ -25,7 +25,7 @@
 
          Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
          
 
          Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
          
 
          Example usage:
          
-
          // Works on both iOS and Android
+
          // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.26/alert/index.html b/docs/0.26/alert/index.html
index 0dd81b138c1..d76769f91e9 100644
--- a/docs/0.26/alert/index.html
+++ b/docs/0.26/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
          0.26
          Edit
          Alert
          Use Alert to display an alert dialog.
          
-
          This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
          
+
          This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
          
 
          Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
          
 
          On iOS, you can specify any number of buttons.
          
 
          On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
          
@@ -25,7 +25,7 @@
 
          Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
          
 
          Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
          
 
          Example usage:
          
-
          // Works on both iOS and Android
+
          // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.26/clipboard.html b/docs/0.26/clipboard.html
index 431bb573eb0..f1ae05a4ec7 100644
--- a/docs/0.26/clipboard.html
+++ b/docs/0.26/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
          Edit
          Clipboard
          Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
          
+        
          Edit
          Clipboard
          Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
          
 
          Methods
          
 
            
 
          • getString
            • 
diff --git a/docs/0.26/clipboard/index.html b/docs/0.26/clipboard/index.html
index 431bb573eb0..f1ae05a4ec7 100644
--- a/docs/0.26/clipboard/index.html
+++ b/docs/0.26/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
          Edit
          Clipboard
          Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
          
+        
          Edit
          Clipboard
          Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
          
 
          Methods
          
 
            
 
          • getString
            • 
diff --git a/docs/0.26/components-and-apis.html b/docs/0.26/components-and-apis.html
index 4e1d14f87f0..a00afe4a52a 100644
--- a/docs/0.26/components-and-apis.html
+++ b/docs/0.26/components-and-apis.html
@@ -130,7 +130,7 @@
   
            
     
       
            Picker
            
-      
            Renders the native picker component on iOS and Android.
            
+      
            Renders the native picker component on Android and iOS.
            
                 
   
            
   
            
@@ -290,7 +290,7 @@
   
            
     
       
            Clipboard
            
-      
            Provides an interface for setting and getting content from the clipboard on both iOS and Android.
            
+      
            Provides an interface for setting and getting content from the clipboard on both Android and iOS.
            
                 
   
            
   
            
diff --git a/docs/0.26/components-and-apis/index.html b/docs/0.26/components-and-apis/index.html
index 4e1d14f87f0..a00afe4a52a 100644
--- a/docs/0.26/components-and-apis/index.html
+++ b/docs/0.26/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
            
     
       
            Picker
            
-      
            Renders the native picker component on iOS and Android.
            
+      
            Renders the native picker component on Android and iOS.
            
                 
   
            
   
            
@@ -290,7 +290,7 @@
   
            
     
       
            Clipboard
            
-      
            Provides an interface for setting and getting content from the clipboard on both iOS and Android.
            
+      
            Provides an interface for setting and getting content from the clipboard on both Android and iOS.
            
                 
   
            
   
            
diff --git a/docs/0.26/getting-started.html b/docs/0.26/getting-started.html
index 3456424a859..578e731b29e 100644
--- a/docs/0.26/getting-started.html
+++ b/docs/0.26/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
            If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
            
 
            
 
            Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
            
-
            The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
            
+
            The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
            
 
            
   Development OS:
   
diff --git a/docs/0.26/getting-started/index.html b/docs/0.26/getting-started/index.html
index 3456424a859..578e731b29e 100644
--- a/docs/0.26/getting-started/index.html
+++ b/docs/0.26/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
            If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
            
 
            
 
            Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
            
-
            The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
            
+
            The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
            
 
            
   Development OS:
   
diff --git a/docs/0.26/images.html b/docs/0.26/images.html
index a25e11efe0e..4ea2fbc60e9 100644
--- a/docs/0.26/images.html
+++ b/docs/0.26/images.html
@@ -69,7 +69,7 @@
               }
             });
         
            Edit
            Images
            Static Image Resources
            
-
            React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
            
+
            React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
            
 
            <Image source={require('./my-icon.png')} />
 
            
 
            The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
            
@@ -88,7 +88,7 @@
 
            On Windows, you might need to restart the packager if you add new images to your project.
            
 
            Here are some benefits that you get:
            
 
              
-
            1. Same system on iOS and Android.
              2. 
+
            2. Same system on Android and iOS.
              3. 
 
            3. Images live in the same folder as your JavaScript code. Components are self-contained.
              4. 
 
            4. No global namespace, i.e. you don't have to worry about name collisions.
              5. 
 
            5. Only the images that are actually used will be packaged into your app.
              6. 
diff --git a/docs/0.26/images/index.html b/docs/0.26/images/index.html
index a25e11efe0e..4ea2fbc60e9 100644
--- a/docs/0.26/images/index.html
+++ b/docs/0.26/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
            Edit
            Images
            Static Image Resources
            
-
            React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
            
+
            React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
            
 
            <Image source={require('./my-icon.png')} />
 
            
 
            The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
            
@@ -88,7 +88,7 @@
 
            On Windows, you might need to restart the packager if you add new images to your project.
            
 
            Here are some benefits that you get:
            
 
              
-
            1. Same system on iOS and Android.
              2. 
+
            2. Same system on Android and iOS.
              3. 
 
            3. Images live in the same folder as your JavaScript code. Components are self-contained.
              4. 
 
            4. No global namespace, i.e. you don't have to worry about name collisions.
              5. 
 
            5. Only the images that are actually used will be packaged into your app.
              6. 
diff --git a/docs/0.26/navigation.html b/docs/0.26/navigation.html
index e8860959efd..95b4fd3a75f 100644
--- a/docs/0.26/navigation.html
+++ b/docs/0.26/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
            Edit
            Navigating Between Screens
            Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
            
-
            This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
            
-
            If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
            
+
            This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
            
+
            If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
            
 
            React Navigation
            
 
            The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
            
 
            The first step is to install in your project:
            
diff --git a/docs/0.26/navigation/index.html b/docs/0.26/navigation/index.html
index e8860959efd..95b4fd3a75f 100644
--- a/docs/0.26/navigation/index.html
+++ b/docs/0.26/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
            Edit
            Navigating Between Screens
            Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
            
-
            This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
            
-
            If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
            
+
            This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
            
+
            If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
            
 
            React Navigation
            
 
            The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
            
 
            The first step is to install in your project:
            
diff --git a/docs/0.26/navigator.html b/docs/0.26/navigator.html
index ae4f9b1b1e4..9e9eb0931af 100644
--- a/docs/0.26/navigator.html
+++ b/docs/0.26/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
            Edit
            Navigator
            Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
            
+        
            Edit
            Navigator
            Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
            
 
            To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
            
 
            import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.26/navigator/index.html b/docs/0.26/navigator/index.html
index ae4f9b1b1e4..9e9eb0931af 100644
--- a/docs/0.26/navigator/index.html
+++ b/docs/0.26/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
            Edit
            Navigator
            Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
            
+        
            Edit
            Navigator
            Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
            
 
            To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
            
 
            import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.26/picker.html b/docs/0.26/picker.html
index bd2367c9c16..b4bb280eb29 100644
--- a/docs/0.26/picker.html
+++ b/docs/0.26/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
            Edit
            Picker
            Renders the native picker component on iOS and Android. Example:
            
+        
            Edit
            Picker
            Renders the native picker component on Android and iOS. Example:
            
 
            <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.26/picker/index.html b/docs/0.26/picker/index.html
index bd2367c9c16..b4bb280eb29 100644
--- a/docs/0.26/picker/index.html
+++ b/docs/0.26/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
            Edit
            Picker
            Renders the native picker component on iOS and Android. Example:
            
+        
            Edit
            Picker
            Renders the native picker component on Android and iOS. Example:
            
 
            <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.26/platform-specific-code.html b/docs/0.26/platform-specific-code.html
index 7e31be5ddac..aeb46a9fb4e 100644
--- a/docs/0.26/platform-specific-code.html
+++ b/docs/0.26/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
            Edit
            Platform Specific Code
            When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
            
+        
            Edit
            Platform Specific Code
            When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
            
 
            React Native provides two ways to organize your code and separate it by platform:
            
 
              
 
            • Using the Platform module.
              • 
diff --git a/docs/0.26/platform-specific-code/index.html b/docs/0.26/platform-specific-code/index.html
index 7e31be5ddac..aeb46a9fb4e 100644
--- a/docs/0.26/platform-specific-code/index.html
+++ b/docs/0.26/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
            Edit
            Platform Specific Code
            When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
            
+        
            Edit
            Platform Specific Code
            When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
            
 
            React Native provides two ways to organize your code and separate it by platform:
            
 
              
 
            • Using the Platform module.
              • 
diff --git a/docs/0.27/accessibility.html b/docs/0.27/accessibility.html
index 196f0835e2d..41130d8041a 100644
--- a/docs/0.27/accessibility.html
+++ b/docs/0.27/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
            Edit
            Accessibility
            Native App Accessibility (iOS and Android)
            
-
            Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
            
+        
            Edit
            Accessibility
            Native App Accessibility (Android and iOS)
            
+
            Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
            
 
            In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
            
 
            Making Apps Accessible
            
 
            Accessibility properties
            
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
          
-
          ← AnimationsImproving User Experience →
          Edit
          Accessibility
          Native App Accessibility (iOS and Android)
          
-
          Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
          
+        
          Edit
          Accessibility
          Native App Accessibility (Android and iOS)
          
+
          Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
          
 
          In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
          
 
          Making Apps Accessible
          
 
          Accessibility properties
          
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
      
-
      ← AnimationsImproving User Experience →
      0.27
      Edit
      Alert
      Use Alert to display an alert dialog.
      
-
      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
      
+
      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
      
 
      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
      
 
      On iOS, you can specify any number of buttons.
      
 
      On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
      
@@ -25,7 +25,7 @@
 
      Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
      
 
      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
      
 
      Example usage:
      
-
      // Works on both iOS and Android
+
      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.27/alert/index.html b/docs/0.27/alert/index.html
index 9c87aaef556..74932440392 100644
--- a/docs/0.27/alert/index.html
+++ b/docs/0.27/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
      0.27
      Edit
      Alert
      Use Alert to display an alert dialog.
      
-
      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
      
+
      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
      
 
      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
      
 
      On iOS, you can specify any number of buttons.
      
 
      On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
      
@@ -25,7 +25,7 @@
 
      Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
      
 
      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
      
 
      Example usage:
      
-
      // Works on both iOS and Android
+
      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.27/clipboard.html b/docs/0.27/clipboard.html
index 50c9f81c54c..4bea38834f4 100644
--- a/docs/0.27/clipboard.html
+++ b/docs/0.27/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
      Edit
      Clipboard
      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
      
+        
      Edit
      Clipboard
      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
      
 
      Methods
      
 
        
 
      • getString
        • 
diff --git a/docs/0.27/clipboard/index.html b/docs/0.27/clipboard/index.html
index 50c9f81c54c..4bea38834f4 100644
--- a/docs/0.27/clipboard/index.html
+++ b/docs/0.27/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
      Edit
      Clipboard
      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
      
+        
      Edit
      Clipboard
      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
      
 
      Methods
      
 
        
 
      • getString
        • 
diff --git a/docs/0.27/components-and-apis.html b/docs/0.27/components-and-apis.html
index 8ea9ca0f065..8c5d87030ea 100644
--- a/docs/0.27/components-and-apis.html
+++ b/docs/0.27/components-and-apis.html
@@ -130,7 +130,7 @@
   
        
     
       
        Picker
        
-      
        Renders the native picker component on iOS and Android.
        
+      
        Renders the native picker component on Android and iOS.
        
             
   
        
   
        
@@ -290,7 +290,7 @@
   
        
     
       
        Clipboard
        
-      
        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
        
+      
        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
        
             
   
        
   
        
diff --git a/docs/0.27/components-and-apis/index.html b/docs/0.27/components-and-apis/index.html
index 8ea9ca0f065..8c5d87030ea 100644
--- a/docs/0.27/components-and-apis/index.html
+++ b/docs/0.27/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
        
     
       
        Picker
        
-      
        Renders the native picker component on iOS and Android.
        
+      
        Renders the native picker component on Android and iOS.
        
             
   
        
   
        
@@ -290,7 +290,7 @@
   
        
     
       
        Clipboard
        
-      
        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
        
+      
        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
        
             
   
        
   
        
diff --git a/docs/0.27/getting-started.html b/docs/0.27/getting-started.html
index 01a3f607ae5..bc2091b7eeb 100644
--- a/docs/0.27/getting-started.html
+++ b/docs/0.27/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
        
 
        
 
        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
        
-
        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
        
+
        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
        
 
        
   Development OS:
   
diff --git a/docs/0.27/getting-started/index.html b/docs/0.27/getting-started/index.html
index 01a3f607ae5..bc2091b7eeb 100644
--- a/docs/0.27/getting-started/index.html
+++ b/docs/0.27/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
        
 
        
 
        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
        
-
        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
        
+
        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
        
 
        
   Development OS:
   
diff --git a/docs/0.27/images.html b/docs/0.27/images.html
index eb0d8eb1673..ec9d743222d 100644
--- a/docs/0.27/images.html
+++ b/docs/0.27/images.html
@@ -69,7 +69,7 @@
               }
             });
         
        Edit
        Images
        Static Image Resources
        
-
        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
        
+
        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
        
 
        <Image source={require('./my-icon.png')} />
 
        
 
        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
        
@@ -88,7 +88,7 @@
 
        On Windows, you might need to restart the packager if you add new images to your project.
        
 
        Here are some benefits that you get:
        
 
          
-
        1. Same system on iOS and Android.
          2. 
+
        2. Same system on Android and iOS.
          3. 
 
        3. Images live in the same folder as your JavaScript code. Components are self-contained.
          4. 
 
        4. No global namespace, i.e. you don't have to worry about name collisions.
          5. 
 
        5. Only the images that are actually used will be packaged into your app.
          6. 
diff --git a/docs/0.27/images/index.html b/docs/0.27/images/index.html
index eb0d8eb1673..ec9d743222d 100644
--- a/docs/0.27/images/index.html
+++ b/docs/0.27/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
        Edit
        Images
        Static Image Resources
        
-
        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
        
+
        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
        
 
        <Image source={require('./my-icon.png')} />
 
        
 
        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
        
@@ -88,7 +88,7 @@
 
        On Windows, you might need to restart the packager if you add new images to your project.
        
 
        Here are some benefits that you get:
        
 
          
-
        1. Same system on iOS and Android.
          2. 
+
        2. Same system on Android and iOS.
          3. 
 
        3. Images live in the same folder as your JavaScript code. Components are self-contained.
          4. 
 
        4. No global namespace, i.e. you don't have to worry about name collisions.
          5. 
 
        5. Only the images that are actually used will be packaged into your app.
          6. 
diff --git a/docs/0.27/navigation.html b/docs/0.27/navigation.html
index eac42222516..55314700e56 100644
--- a/docs/0.27/navigation.html
+++ b/docs/0.27/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
        Edit
        Navigating Between Screens
        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
        
-
        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
        
-
        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
        
+
        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
        
+
        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
        
 
        React Navigation
        
 
        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
        
 
        The first step is to install in your project:
        
diff --git a/docs/0.27/navigation/index.html b/docs/0.27/navigation/index.html
index eac42222516..55314700e56 100644
--- a/docs/0.27/navigation/index.html
+++ b/docs/0.27/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
        Edit
        Navigating Between Screens
        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
        
-
        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
        
-
        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
        
+
        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
        
+
        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
        
 
        React Navigation
        
 
        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
        
 
        The first step is to install in your project:
        
diff --git a/docs/0.27/navigator.html b/docs/0.27/navigator.html
index 505d107c5d6..864832b2c6d 100644
--- a/docs/0.27/navigator.html
+++ b/docs/0.27/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
        Edit
        Navigator
        Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
        
+        
        Edit
        Navigator
        Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
        
 
        To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
        
 
        import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.27/navigator/index.html b/docs/0.27/navigator/index.html
index 505d107c5d6..864832b2c6d 100644
--- a/docs/0.27/navigator/index.html
+++ b/docs/0.27/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
        Edit
        Navigator
        Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
        
+        
        Edit
        Navigator
        Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
        
 
        To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
        
 
        import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.27/picker.html b/docs/0.27/picker.html
index c2a6f3cf8d3..9f9eaec5c70 100644
--- a/docs/0.27/picker.html
+++ b/docs/0.27/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
        Edit
        Picker
        Renders the native picker component on iOS and Android. Example:
        
+        
        Edit
        Picker
        Renders the native picker component on Android and iOS. Example:
        
 
        <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.27/picker/index.html b/docs/0.27/picker/index.html
index c2a6f3cf8d3..9f9eaec5c70 100644
--- a/docs/0.27/picker/index.html
+++ b/docs/0.27/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
        Edit
        Picker
        Renders the native picker component on iOS and Android. Example:
        
+        
        Edit
        Picker
        Renders the native picker component on Android and iOS. Example:
        
 
        <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.27/platform-specific-code.html b/docs/0.27/platform-specific-code.html
index 4f627f4577e..f8eb81090a9 100644
--- a/docs/0.27/platform-specific-code.html
+++ b/docs/0.27/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
        Edit
        Platform Specific Code
        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
        
+        
        Edit
        Platform Specific Code
        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
        
 
        React Native provides two ways to organize your code and separate it by platform:
        
 
          
 
        • Using the Platform module.
          • 
diff --git a/docs/0.27/platform-specific-code/index.html b/docs/0.27/platform-specific-code/index.html
index 4f627f4577e..f8eb81090a9 100644
--- a/docs/0.27/platform-specific-code/index.html
+++ b/docs/0.27/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
        Edit
        Platform Specific Code
        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
        
+        
        Edit
        Platform Specific Code
        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
        
 
        React Native provides two ways to organize your code and separate it by platform:
        
 
          
 
        • Using the Platform module.
          • 
diff --git a/docs/0.28/accessibility.html b/docs/0.28/accessibility.html
index 90fac6489b7..00feb793f80 100644
--- a/docs/0.28/accessibility.html
+++ b/docs/0.28/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
        Edit
        Accessibility
        Native App Accessibility (iOS and Android)
        
-
        Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
        
+        
        Edit
        Accessibility
        Native App Accessibility (Android and iOS)
        
+
        Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
        
 
        In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
        
 
        Making Apps Accessible
        
 
        Accessibility properties
        
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
      
-
      ← AnimationsImproving User Experience →
      Edit
      Accessibility
      Native App Accessibility (iOS and Android)
      
-
      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
      
+        
      Edit
      Accessibility
      Native App Accessibility (Android and iOS)
      
+
      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
      
 
      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
      
 
      Making Apps Accessible
      
 
      Accessibility properties
      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 

-
← AnimationsImproving User Experience →
0.28
Edit
Alert
Use Alert to display an alert dialog.

-
This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+
This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

 
Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

 
On iOS, you can specify any number of buttons.

 
On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@
 
Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

 
Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

 
Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.28/alert/index.html b/docs/0.28/alert/index.html
index 590024a9136..43fb2bc79b9 100644
--- a/docs/0.28/alert/index.html
+++ b/docs/0.28/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
0.28
Edit
Alert
Use Alert to display an alert dialog.

-
This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+
This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

 
Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

 
On iOS, you can specify any number of buttons.

 
On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@
 
Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

 
Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

 
Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.28/clipboard.html b/docs/0.28/clipboard.html
index 7a62f897704..1c221025bc7 100644
--- a/docs/0.28/clipboard.html
+++ b/docs/0.28/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.28/clipboard/index.html b/docs/0.28/clipboard/index.html
index 7a62f897704..1c221025bc7 100644
--- a/docs/0.28/clipboard/index.html
+++ b/docs/0.28/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.28/components-and-apis.html b/docs/0.28/components-and-apis.html
index ea2d2cd4758..48d59ebae2c 100644
--- a/docs/0.28/components-and-apis.html
+++ b/docs/0.28/components-and-apis.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.28/components-and-apis/index.html b/docs/0.28/components-and-apis/index.html
index ea2d2cd4758..48d59ebae2c 100644
--- a/docs/0.28/components-and-apis/index.html
+++ b/docs/0.28/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.28/getting-started.html b/docs/0.28/getting-started.html
index 6218ff9d98b..4deb87aa75b 100644
--- a/docs/0.28/getting-started.html
+++ b/docs/0.28/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.28/getting-started/index.html b/docs/0.28/getting-started/index.html
index 6218ff9d98b..4deb87aa75b 100644
--- a/docs/0.28/getting-started/index.html
+++ b/docs/0.28/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.28/images.html b/docs/0.28/images.html
index 337675f54df..55d9176adf7 100644
--- a/docs/0.28/images.html
+++ b/docs/0.28/images.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.28/images/index.html b/docs/0.28/images/index.html
index 337675f54df..55d9176adf7 100644
--- a/docs/0.28/images/index.html
+++ b/docs/0.28/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.28/navigation.html b/docs/0.28/navigation.html
index d69ff02c759..fa3502c07b5 100644
--- a/docs/0.28/navigation.html
+++ b/docs/0.28/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.28/navigation/index.html b/docs/0.28/navigation/index.html
index d69ff02c759..fa3502c07b5 100644
--- a/docs/0.28/navigation/index.html
+++ b/docs/0.28/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.28/navigator.html b/docs/0.28/navigator.html
index 05577ee47a1..63de32b4d1a 100644
--- a/docs/0.28/navigator.html
+++ b/docs/0.28/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.28/navigator/index.html b/docs/0.28/navigator/index.html
index 05577ee47a1..63de32b4d1a 100644
--- a/docs/0.28/navigator/index.html
+++ b/docs/0.28/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.28/picker.html b/docs/0.28/picker.html
index 01c083db565..92d1fc5a0ec 100644
--- a/docs/0.28/picker.html
+++ b/docs/0.28/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.28/picker/index.html b/docs/0.28/picker/index.html
index 01c083db565..92d1fc5a0ec 100644
--- a/docs/0.28/picker/index.html
+++ b/docs/0.28/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.28/platform-specific-code.html b/docs/0.28/platform-specific-code.html
index 84cf5c403b4..b84820b88fa 100644
--- a/docs/0.28/platform-specific-code.html
+++ b/docs/0.28/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.28/platform-specific-code/index.html b/docs/0.28/platform-specific-code/index.html
index 84cf5c403b4..b84820b88fa 100644
--- a/docs/0.28/platform-specific-code/index.html
+++ b/docs/0.28/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.29/accessibility.html b/docs/0.29/accessibility.html
index bb0931524c1..23004837be7 100644
--- a/docs/0.29/accessibility.html
+++ b/docs/0.29/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
    Edit
    Accessibility
    Native App Accessibility (iOS and Android)
    
-
    Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
+        
    Edit
    Accessibility
    Native App Accessibility (Android and iOS)
    
+
    Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
 
    In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
    
 
    Making Apps Accessible
    
 
    Accessibility properties
    
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 

-
← AnimationsImproving User Experience →
Edit

Accessibility

Native App Accessibility (iOS and Android)

-

Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

+
Edit

Accessibility

Native App Accessibility (Android and iOS)

+

Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

Making Apps Accessible

Accessibility properties

@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService -
← AnimationsImproving User Experience →

0.29

Edit

Alert

Use Alert to display an alert dialog.

-

This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+

This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

On iOS, you can specify any number of buttons.

On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@

Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.29/alert/index.html b/docs/0.29/alert/index.html
index d731203ae3a..9e72d0c7ded 100644
--- a/docs/0.29/alert/index.html
+++ b/docs/0.29/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
0.29
Edit
Alert
Use Alert to display an alert dialog.

-
This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+
This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

 
Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

 
On iOS, you can specify any number of buttons.

 
On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@
 
Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

 
Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

 
Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.29/clipboard.html b/docs/0.29/clipboard.html
index 59ab4b24a0e..1dc9aac1cad 100644
--- a/docs/0.29/clipboard.html
+++ b/docs/0.29/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.29/clipboard/index.html b/docs/0.29/clipboard/index.html
index 59ab4b24a0e..1dc9aac1cad 100644
--- a/docs/0.29/clipboard/index.html
+++ b/docs/0.29/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.29/components-and-apis.html b/docs/0.29/components-and-apis.html
index 8e4e5d10848..3c0e82e5b0c 100644
--- a/docs/0.29/components-and-apis.html
+++ b/docs/0.29/components-and-apis.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.29/components-and-apis/index.html b/docs/0.29/components-and-apis/index.html
index 8e4e5d10848..3c0e82e5b0c 100644
--- a/docs/0.29/components-and-apis/index.html
+++ b/docs/0.29/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.29/getting-started.html b/docs/0.29/getting-started.html
index 65dcd4b43ff..955102372e1 100644
--- a/docs/0.29/getting-started.html
+++ b/docs/0.29/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.29/getting-started/index.html b/docs/0.29/getting-started/index.html
index 65dcd4b43ff..955102372e1 100644
--- a/docs/0.29/getting-started/index.html
+++ b/docs/0.29/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.29/images.html b/docs/0.29/images.html
index feef6ca54bc..1102633f24c 100644
--- a/docs/0.29/images.html
+++ b/docs/0.29/images.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.29/images/index.html b/docs/0.29/images/index.html
index feef6ca54bc..1102633f24c 100644
--- a/docs/0.29/images/index.html
+++ b/docs/0.29/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.29/navigation.html b/docs/0.29/navigation.html
index feb43a959a4..ff4217db22f 100644
--- a/docs/0.29/navigation.html
+++ b/docs/0.29/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.29/navigation/index.html b/docs/0.29/navigation/index.html
index feb43a959a4..ff4217db22f 100644
--- a/docs/0.29/navigation/index.html
+++ b/docs/0.29/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.29/navigator.html b/docs/0.29/navigator.html
index ca8fd003332..a700e674969 100644
--- a/docs/0.29/navigator.html
+++ b/docs/0.29/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.29/navigator/index.html b/docs/0.29/navigator/index.html
index ca8fd003332..a700e674969 100644
--- a/docs/0.29/navigator/index.html
+++ b/docs/0.29/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.29/navigatorios.html b/docs/0.29/navigatorios.html
index 00f1f40977c..558eb8ae414 100644
--- a/docs/0.29/navigatorios.html
+++ b/docs/0.29/navigatorios.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    NavigatorIOS
    NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.
    
-
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.
    
+
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.
    
 
    To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.
    
 
    import React, { Component } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.29/navigatorios/index.html b/docs/0.29/navigatorios/index.html
index 00f1f40977c..558eb8ae414 100644
--- a/docs/0.29/navigatorios/index.html
+++ b/docs/0.29/navigatorios/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    NavigatorIOS
    NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.
    
-
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.
    
+
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.
    
 
    To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.
    
 
    import React, { Component } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.29/picker.html b/docs/0.29/picker.html
index 15e4dcb6c21..4cc52aeb6c1 100644
--- a/docs/0.29/picker.html
+++ b/docs/0.29/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.29/picker/index.html b/docs/0.29/picker/index.html
index 15e4dcb6c21..4cc52aeb6c1 100644
--- a/docs/0.29/picker/index.html
+++ b/docs/0.29/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.29/platform-specific-code.html b/docs/0.29/platform-specific-code.html
index 4ffc9df5785..f893ad4d25a 100644
--- a/docs/0.29/platform-specific-code.html
+++ b/docs/0.29/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.29/platform-specific-code/index.html b/docs/0.29/platform-specific-code/index.html
index 4ffc9df5785..f893ad4d25a 100644
--- a/docs/0.29/platform-specific-code/index.html
+++ b/docs/0.29/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.30/accessibility.html b/docs/0.30/accessibility.html
index b256a8ff9ae..ec3a38448bc 100644
--- a/docs/0.30/accessibility.html
+++ b/docs/0.30/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
    Edit
    Accessibility
    Native App Accessibility (iOS and Android)
    
-
    Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
+        
    Edit
    Accessibility
    Native App Accessibility (Android and iOS)
    
+
    Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
 
    In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
    
 
    Making Apps Accessible
    
 
    Accessibility properties
    
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 

-
← AnimationsImproving User Experience →
Edit

Accessibility

Native App Accessibility (iOS and Android)

-

Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

+
Edit

Accessibility

Native App Accessibility (Android and iOS)

+

Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

Making Apps Accessible

Accessibility properties

@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService -
← AnimationsImproving User Experience →

0.30

Edit

Alert

Use Alert to display an alert dialog.

-

This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+

This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

On iOS, you can specify any number of buttons.

On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@

Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.30/alert/index.html b/docs/0.30/alert/index.html
index 488681c8a73..f863b036cb4 100644
--- a/docs/0.30/alert/index.html
+++ b/docs/0.30/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
0.30
Edit
Alert
Use Alert to display an alert dialog.

-
This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+
This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

 
Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

 
On iOS, you can specify any number of buttons.

 
On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@
 
Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

 
Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

 
Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.30/clipboard.html b/docs/0.30/clipboard.html
index e5c7df15be2..71bdaa70c5b 100644
--- a/docs/0.30/clipboard.html
+++ b/docs/0.30/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.30/clipboard/index.html b/docs/0.30/clipboard/index.html
index e5c7df15be2..71bdaa70c5b 100644
--- a/docs/0.30/clipboard/index.html
+++ b/docs/0.30/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.30/components-and-apis.html b/docs/0.30/components-and-apis.html
index e0a6702aace..6d60cfbe184 100644
--- a/docs/0.30/components-and-apis.html
+++ b/docs/0.30/components-and-apis.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.30/components-and-apis/index.html b/docs/0.30/components-and-apis/index.html
index e0a6702aace..6d60cfbe184 100644
--- a/docs/0.30/components-and-apis/index.html
+++ b/docs/0.30/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.30/getting-started.html b/docs/0.30/getting-started.html
index 2fe84917f4f..5861a3a39d4 100644
--- a/docs/0.30/getting-started.html
+++ b/docs/0.30/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.30/getting-started/index.html b/docs/0.30/getting-started/index.html
index 2fe84917f4f..5861a3a39d4 100644
--- a/docs/0.30/getting-started/index.html
+++ b/docs/0.30/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.30/images.html b/docs/0.30/images.html
index 530ed6f7d3e..814487b19ae 100644
--- a/docs/0.30/images.html
+++ b/docs/0.30/images.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.30/images/index.html b/docs/0.30/images/index.html
index 530ed6f7d3e..814487b19ae 100644
--- a/docs/0.30/images/index.html
+++ b/docs/0.30/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.30/navigation.html b/docs/0.30/navigation.html
index 40b7e040a3f..1e3c94967b4 100644
--- a/docs/0.30/navigation.html
+++ b/docs/0.30/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.30/navigation/index.html b/docs/0.30/navigation/index.html
index 40b7e040a3f..1e3c94967b4 100644
--- a/docs/0.30/navigation/index.html
+++ b/docs/0.30/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.30/navigator.html b/docs/0.30/navigator.html
index 3f63a42fdfc..227864679bf 100644
--- a/docs/0.30/navigator.html
+++ b/docs/0.30/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.30/navigator/index.html b/docs/0.30/navigator/index.html
index 3f63a42fdfc..227864679bf 100644
--- a/docs/0.30/navigator/index.html
+++ b/docs/0.30/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.30/navigatorios.html b/docs/0.30/navigatorios.html
index c866983dd29..c1f5c4ba5f5 100644
--- a/docs/0.30/navigatorios.html
+++ b/docs/0.30/navigatorios.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    NavigatorIOS
    NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.
    
-
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.
    
+
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.
    
 
    To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.
    
 
    import React, { Component } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.30/navigatorios/index.html b/docs/0.30/navigatorios/index.html
index c866983dd29..c1f5c4ba5f5 100644
--- a/docs/0.30/navigatorios/index.html
+++ b/docs/0.30/navigatorios/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    NavigatorIOS
    NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.
    
-
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.
    
+
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.
    
 
    To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.
    
 
    import React, { Component } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.30/picker.html b/docs/0.30/picker.html
index ef60e8da3c8..8bf23885936 100644
--- a/docs/0.30/picker.html
+++ b/docs/0.30/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.30/picker/index.html b/docs/0.30/picker/index.html
index ef60e8da3c8..8bf23885936 100644
--- a/docs/0.30/picker/index.html
+++ b/docs/0.30/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.30/platform-specific-code.html b/docs/0.30/platform-specific-code.html
index 46bf7318da7..8c78f5a2ecc 100644
--- a/docs/0.30/platform-specific-code.html
+++ b/docs/0.30/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.30/platform-specific-code/index.html b/docs/0.30/platform-specific-code/index.html
index 46bf7318da7..8c78f5a2ecc 100644
--- a/docs/0.30/platform-specific-code/index.html
+++ b/docs/0.30/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.31/accessibility.html b/docs/0.31/accessibility.html
index c80b6dbd13b..88794a7aad5 100644
--- a/docs/0.31/accessibility.html
+++ b/docs/0.31/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
    Edit
    Accessibility
    Native App Accessibility (iOS and Android)
    
-
    Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
+        
    Edit
    Accessibility
    Native App Accessibility (Android and iOS)
    
+
    Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
 
    In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
    
 
    Making Apps Accessible
    
 
    Accessibility properties
    
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 

-
← AnimationsImproving User Experience →
Edit

Accessibility

Native App Accessibility (iOS and Android)

-

Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

+
Edit

Accessibility

Native App Accessibility (Android and iOS)

+

Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

Making Apps Accessible

Accessibility properties

@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService -
← AnimationsImproving User Experience →

0.31

Edit

Alert

Use Alert to display an alert dialog.

-

This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+

This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

On iOS, you can specify any number of buttons.

On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@

Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.31/alert/index.html b/docs/0.31/alert/index.html
index efa4f9d9137..fb49c9f75c3 100644
--- a/docs/0.31/alert/index.html
+++ b/docs/0.31/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
0.31
Edit
Alert
Use Alert to display an alert dialog.

-
This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+
This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

 
Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

 
On iOS, you can specify any number of buttons.

 
On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@
 
Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

 
Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

 
Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.31/clipboard.html b/docs/0.31/clipboard.html
index 2475ed15999..aa33376ae1d 100644
--- a/docs/0.31/clipboard.html
+++ b/docs/0.31/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.31/clipboard/index.html b/docs/0.31/clipboard/index.html
index 2475ed15999..aa33376ae1d 100644
--- a/docs/0.31/clipboard/index.html
+++ b/docs/0.31/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.31/components-and-apis.html b/docs/0.31/components-and-apis.html
index 0335a420626..3d54bf55958 100644
--- a/docs/0.31/components-and-apis.html
+++ b/docs/0.31/components-and-apis.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.31/components-and-apis/index.html b/docs/0.31/components-and-apis/index.html
index 0335a420626..3d54bf55958 100644
--- a/docs/0.31/components-and-apis/index.html
+++ b/docs/0.31/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.31/getting-started.html b/docs/0.31/getting-started.html
index 7db73a96a28..58bf27248cb 100644
--- a/docs/0.31/getting-started.html
+++ b/docs/0.31/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.31/getting-started/index.html b/docs/0.31/getting-started/index.html
index 7db73a96a28..58bf27248cb 100644
--- a/docs/0.31/getting-started/index.html
+++ b/docs/0.31/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.31/images.html b/docs/0.31/images.html
index 1dce2936c03..99359263296 100644
--- a/docs/0.31/images.html
+++ b/docs/0.31/images.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.31/images/index.html b/docs/0.31/images/index.html
index 1dce2936c03..99359263296 100644
--- a/docs/0.31/images/index.html
+++ b/docs/0.31/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.31/navigation.html b/docs/0.31/navigation.html
index ee530b599b3..55c0846dbac 100644
--- a/docs/0.31/navigation.html
+++ b/docs/0.31/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.31/navigation/index.html b/docs/0.31/navigation/index.html
index ee530b599b3..55c0846dbac 100644
--- a/docs/0.31/navigation/index.html
+++ b/docs/0.31/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.31/navigator.html b/docs/0.31/navigator.html
index 34d39991d85..e3da8d46c43 100644
--- a/docs/0.31/navigator.html
+++ b/docs/0.31/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.31/navigator/index.html b/docs/0.31/navigator/index.html
index 34d39991d85..e3da8d46c43 100644
--- a/docs/0.31/navigator/index.html
+++ b/docs/0.31/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.31/navigatorios.html b/docs/0.31/navigatorios.html
index e496c82dfb5..4551796efea 100644
--- a/docs/0.31/navigatorios.html
+++ b/docs/0.31/navigatorios.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    NavigatorIOS
    NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.
    
-
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.
    
+
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.
    
 
    To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.
    
 
    import React, { Component } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.31/navigatorios/index.html b/docs/0.31/navigatorios/index.html
index e496c82dfb5..4551796efea 100644
--- a/docs/0.31/navigatorios/index.html
+++ b/docs/0.31/navigatorios/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    NavigatorIOS
    NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.
    
-
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.
    
+
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.
    
 
    To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.
    
 
    import React, { Component } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.31/picker.html b/docs/0.31/picker.html
index 8ac83f7ae71..4182aa19b64 100644
--- a/docs/0.31/picker.html
+++ b/docs/0.31/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.31/picker/index.html b/docs/0.31/picker/index.html
index 8ac83f7ae71..4182aa19b64 100644
--- a/docs/0.31/picker/index.html
+++ b/docs/0.31/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.31/platform-specific-code.html b/docs/0.31/platform-specific-code.html
index ad28a4ea896..b03adf0fa05 100644
--- a/docs/0.31/platform-specific-code.html
+++ b/docs/0.31/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.31/platform-specific-code/index.html b/docs/0.31/platform-specific-code/index.html
index ad28a4ea896..b03adf0fa05 100644
--- a/docs/0.31/platform-specific-code/index.html
+++ b/docs/0.31/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.32/accessibility.html b/docs/0.32/accessibility.html
index 57b03d264bc..61bd61304e9 100644
--- a/docs/0.32/accessibility.html
+++ b/docs/0.32/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
    Edit
    Accessibility
    Native App Accessibility (iOS and Android)
    
-
    Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
+        
    Edit
    Accessibility
    Native App Accessibility (Android and iOS)
    
+
    Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
 
    In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
    
 
    Making Apps Accessible
    
 
    Accessibility properties
    
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 

-
← AnimationsImproving User Experience →
Edit

Accessibility

Native App Accessibility (iOS and Android)

-

Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

+
Edit

Accessibility

Native App Accessibility (Android and iOS)

+

Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

Making Apps Accessible

Accessibility properties

@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService -
← AnimationsImproving User Experience →

0.32

Edit

Alert

Use Alert to display an alert dialog.

-

This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+

This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

On iOS, you can specify any number of buttons.

On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@

Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.32/alert/index.html b/docs/0.32/alert/index.html
index bfc94ffddab..1eee9214edc 100644
--- a/docs/0.32/alert/index.html
+++ b/docs/0.32/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
0.32
Edit
Alert
Use Alert to display an alert dialog.

-
This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+
This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

 
Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

 
On iOS, you can specify any number of buttons.

 
On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@
 
Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

 
Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

 
Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.32/clipboard.html b/docs/0.32/clipboard.html
index 1f890762f36..cf102440ff1 100644
--- a/docs/0.32/clipboard.html
+++ b/docs/0.32/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.32/clipboard/index.html b/docs/0.32/clipboard/index.html
index 1f890762f36..cf102440ff1 100644
--- a/docs/0.32/clipboard/index.html
+++ b/docs/0.32/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.32/components-and-apis.html b/docs/0.32/components-and-apis.html
index e598d5ac5c0..e73b80d07f2 100644
--- a/docs/0.32/components-and-apis.html
+++ b/docs/0.32/components-and-apis.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.32/components-and-apis/index.html b/docs/0.32/components-and-apis/index.html
index e598d5ac5c0..e73b80d07f2 100644
--- a/docs/0.32/components-and-apis/index.html
+++ b/docs/0.32/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.32/getting-started.html b/docs/0.32/getting-started.html
index 9325ae34408..b0e0aa02320 100644
--- a/docs/0.32/getting-started.html
+++ b/docs/0.32/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.32/getting-started/index.html b/docs/0.32/getting-started/index.html
index 9325ae34408..b0e0aa02320 100644
--- a/docs/0.32/getting-started/index.html
+++ b/docs/0.32/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.32/images.html b/docs/0.32/images.html
index 804c71d58de..4d7c13cba8b 100644
--- a/docs/0.32/images.html
+++ b/docs/0.32/images.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.32/images/index.html b/docs/0.32/images/index.html
index 804c71d58de..4d7c13cba8b 100644
--- a/docs/0.32/images/index.html
+++ b/docs/0.32/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.32/navigation.html b/docs/0.32/navigation.html
index 0b4cecba97b..bc3c6aece77 100644
--- a/docs/0.32/navigation.html
+++ b/docs/0.32/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.32/navigation/index.html b/docs/0.32/navigation/index.html
index 0b4cecba97b..bc3c6aece77 100644
--- a/docs/0.32/navigation/index.html
+++ b/docs/0.32/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.32/navigator.html b/docs/0.32/navigator.html
index 8043522ebb3..9c61b5bc593 100644
--- a/docs/0.32/navigator.html
+++ b/docs/0.32/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.32/navigator/index.html b/docs/0.32/navigator/index.html
index 8043522ebb3..9c61b5bc593 100644
--- a/docs/0.32/navigator/index.html
+++ b/docs/0.32/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.32/navigatorios.html b/docs/0.32/navigatorios.html
index d69a87cdae5..271b4445e32 100644
--- a/docs/0.32/navigatorios.html
+++ b/docs/0.32/navigatorios.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    NavigatorIOS
    NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.
    
-
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.
    
+
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.
    
 
    To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.
    
 
    import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.32/navigatorios/index.html b/docs/0.32/navigatorios/index.html
index d69a87cdae5..271b4445e32 100644
--- a/docs/0.32/navigatorios/index.html
+++ b/docs/0.32/navigatorios/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    NavigatorIOS
    NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.
    
-
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.
    
+
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.
    
 
    To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.
    
 
    import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.32/picker.html b/docs/0.32/picker.html
index c46d9123b23..b0feb8c6088 100644
--- a/docs/0.32/picker.html
+++ b/docs/0.32/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.32/picker/index.html b/docs/0.32/picker/index.html
index c46d9123b23..b0feb8c6088 100644
--- a/docs/0.32/picker/index.html
+++ b/docs/0.32/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.32/platform-specific-code.html b/docs/0.32/platform-specific-code.html
index 86e767140ea..d93e270e322 100644
--- a/docs/0.32/platform-specific-code.html
+++ b/docs/0.32/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.32/platform-specific-code/index.html b/docs/0.32/platform-specific-code/index.html
index 86e767140ea..d93e270e322 100644
--- a/docs/0.32/platform-specific-code/index.html
+++ b/docs/0.32/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.33/accessibility.html b/docs/0.33/accessibility.html
index a686ae11b19..64c2c0c02f8 100644
--- a/docs/0.33/accessibility.html
+++ b/docs/0.33/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
    Edit
    Accessibility
    Native App Accessibility (iOS and Android)
    
-
    Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
+        
    Edit
    Accessibility
    Native App Accessibility (Android and iOS)
    
+
    Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
 
    In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
    
 
    Making Apps Accessible
    
 
    Accessibility properties
    
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 

-
← AnimationsImproving User Experience →
Edit

Accessibility

Native App Accessibility (iOS and Android)

-

Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

+
Edit

Accessibility

Native App Accessibility (Android and iOS)

+

Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

Making Apps Accessible

Accessibility properties

@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService -
← AnimationsImproving User Experience →

0.33

Edit

Alert

Use Alert to display an alert dialog.

-

This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+

This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

On iOS, you can specify any number of buttons.

On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@

Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.33/alert/index.html b/docs/0.33/alert/index.html
index 49bb09da5af..ba382d98594 100644
--- a/docs/0.33/alert/index.html
+++ b/docs/0.33/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
0.33
Edit
Alert
Use Alert to display an alert dialog.

-
This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+
This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

 
Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

 
On iOS, you can specify any number of buttons.

 
On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@
 
Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

 
Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

 
Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.33/clipboard.html b/docs/0.33/clipboard.html
index 60d7902179c..45e3428e0f0 100644
--- a/docs/0.33/clipboard.html
+++ b/docs/0.33/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.33/clipboard/index.html b/docs/0.33/clipboard/index.html
index 60d7902179c..45e3428e0f0 100644
--- a/docs/0.33/clipboard/index.html
+++ b/docs/0.33/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.33/components-and-apis.html b/docs/0.33/components-and-apis.html
index 55c67302d11..e485b19c4d7 100644
--- a/docs/0.33/components-and-apis.html
+++ b/docs/0.33/components-and-apis.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.33/components-and-apis/index.html b/docs/0.33/components-and-apis/index.html
index 55c67302d11..e485b19c4d7 100644
--- a/docs/0.33/components-and-apis/index.html
+++ b/docs/0.33/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.33/getting-started.html b/docs/0.33/getting-started.html
index bb9e7cf576d..aede492dc62 100644
--- a/docs/0.33/getting-started.html
+++ b/docs/0.33/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.33/getting-started/index.html b/docs/0.33/getting-started/index.html
index bb9e7cf576d..aede492dc62 100644
--- a/docs/0.33/getting-started/index.html
+++ b/docs/0.33/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.33/images.html b/docs/0.33/images.html
index f21b65dfd6e..6beb527ca4f 100644
--- a/docs/0.33/images.html
+++ b/docs/0.33/images.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.33/images/index.html b/docs/0.33/images/index.html
index f21b65dfd6e..6beb527ca4f 100644
--- a/docs/0.33/images/index.html
+++ b/docs/0.33/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.33/navigation.html b/docs/0.33/navigation.html
index 727b6870065..bff894dd3b2 100644
--- a/docs/0.33/navigation.html
+++ b/docs/0.33/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.33/navigation/index.html b/docs/0.33/navigation/index.html
index 727b6870065..bff894dd3b2 100644
--- a/docs/0.33/navigation/index.html
+++ b/docs/0.33/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.33/navigator.html b/docs/0.33/navigator.html
index de8173a3b89..7eb19ccec81 100644
--- a/docs/0.33/navigator.html
+++ b/docs/0.33/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.33/navigator/index.html b/docs/0.33/navigator/index.html
index de8173a3b89..7eb19ccec81 100644
--- a/docs/0.33/navigator/index.html
+++ b/docs/0.33/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.33/navigatorios.html b/docs/0.33/navigatorios.html
index 61cc5754491..3d7b5522b17 100644
--- a/docs/0.33/navigatorios.html
+++ b/docs/0.33/navigatorios.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    NavigatorIOS
    NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.
    
-
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.
    
+
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.
    
 
    To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.
    
 
    import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.33/navigatorios/index.html b/docs/0.33/navigatorios/index.html
index 61cc5754491..3d7b5522b17 100644
--- a/docs/0.33/navigatorios/index.html
+++ b/docs/0.33/navigatorios/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    NavigatorIOS
    NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.
    
-
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.
    
+
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.
    
 
    To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.
    
 
    import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.33/picker.html b/docs/0.33/picker.html
index fd86d2d7e1c..f1bdec79bee 100644
--- a/docs/0.33/picker.html
+++ b/docs/0.33/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.33/picker/index.html b/docs/0.33/picker/index.html
index fd86d2d7e1c..f1bdec79bee 100644
--- a/docs/0.33/picker/index.html
+++ b/docs/0.33/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.33/platform-specific-code.html b/docs/0.33/platform-specific-code.html
index 7a83957bd61..6e767facf70 100644
--- a/docs/0.33/platform-specific-code.html
+++ b/docs/0.33/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.33/platform-specific-code/index.html b/docs/0.33/platform-specific-code/index.html
index 7a83957bd61..6e767facf70 100644
--- a/docs/0.33/platform-specific-code/index.html
+++ b/docs/0.33/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.34/accessibility.html b/docs/0.34/accessibility.html
index 4537fe7d56c..42eade4473a 100644
--- a/docs/0.34/accessibility.html
+++ b/docs/0.34/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
    Edit
    Accessibility
    Native App Accessibility (iOS and Android)
    
-
    Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
+        
    Edit
    Accessibility
    Native App Accessibility (Android and iOS)
    
+
    Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
 
    In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
    
 
    Making Apps Accessible
    
 
    Accessibility properties
    
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 

-
← AnimationsImproving User Experience →
Edit

Accessibility

Native App Accessibility (iOS and Android)

-

Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

+
Edit

Accessibility

Native App Accessibility (Android and iOS)

+

Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

Making Apps Accessible

Accessibility properties

@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService -
← AnimationsImproving User Experience →

0.34

Edit

Alert

Use Alert to display an alert dialog.

-

This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+

This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

On iOS, you can specify any number of buttons.

On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@

Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.34/alert/index.html b/docs/0.34/alert/index.html
index 68fe28e64ad..441060425b2 100644
--- a/docs/0.34/alert/index.html
+++ b/docs/0.34/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
0.34
Edit
Alert
Use Alert to display an alert dialog.

-
This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+
This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

 
Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

 
On iOS, you can specify any number of buttons.

 
On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@
 
Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

 
Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

 
Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.34/clipboard.html b/docs/0.34/clipboard.html
index 45c38a5c18d..842e5c8c6e6 100644
--- a/docs/0.34/clipboard.html
+++ b/docs/0.34/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.34/clipboard/index.html b/docs/0.34/clipboard/index.html
index 45c38a5c18d..842e5c8c6e6 100644
--- a/docs/0.34/clipboard/index.html
+++ b/docs/0.34/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.34/components-and-apis.html b/docs/0.34/components-and-apis.html
index 0c1b8797d47..b1ca33e2e0b 100644
--- a/docs/0.34/components-and-apis.html
+++ b/docs/0.34/components-and-apis.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.34/components-and-apis/index.html b/docs/0.34/components-and-apis/index.html
index 0c1b8797d47..b1ca33e2e0b 100644
--- a/docs/0.34/components-and-apis/index.html
+++ b/docs/0.34/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.34/getting-started.html b/docs/0.34/getting-started.html
index 6e867107095..d1e5c3e6b13 100644
--- a/docs/0.34/getting-started.html
+++ b/docs/0.34/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.34/getting-started/index.html b/docs/0.34/getting-started/index.html
index 6e867107095..d1e5c3e6b13 100644
--- a/docs/0.34/getting-started/index.html
+++ b/docs/0.34/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.34/images.html b/docs/0.34/images.html
index b41c209e666..0af76978f09 100644
--- a/docs/0.34/images.html
+++ b/docs/0.34/images.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.34/images/index.html b/docs/0.34/images/index.html
index b41c209e666..0af76978f09 100644
--- a/docs/0.34/images/index.html
+++ b/docs/0.34/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.34/navigation.html b/docs/0.34/navigation.html
index e8a3b6f3155..431ed95f271 100644
--- a/docs/0.34/navigation.html
+++ b/docs/0.34/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.34/navigation/index.html b/docs/0.34/navigation/index.html
index e8a3b6f3155..431ed95f271 100644
--- a/docs/0.34/navigation/index.html
+++ b/docs/0.34/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.34/navigator.html b/docs/0.34/navigator.html
index e1500015b75..184591df40d 100644
--- a/docs/0.34/navigator.html
+++ b/docs/0.34/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.34/navigator/index.html b/docs/0.34/navigator/index.html
index e1500015b75..184591df40d 100644
--- a/docs/0.34/navigator/index.html
+++ b/docs/0.34/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.34/navigatorios.html b/docs/0.34/navigatorios.html
index 4e3ea1ed0fc..158afdd25df 100644
--- a/docs/0.34/navigatorios.html
+++ b/docs/0.34/navigatorios.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    NavigatorIOS
    NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.
    
-
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.
    
+
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.
    
 
    To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.
    
 
    import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.34/navigatorios/index.html b/docs/0.34/navigatorios/index.html
index 4e3ea1ed0fc..158afdd25df 100644
--- a/docs/0.34/navigatorios/index.html
+++ b/docs/0.34/navigatorios/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    NavigatorIOS
    NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.
    
-
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.
    
+
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.
    
 
    To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.
    
 
    import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.34/picker.html b/docs/0.34/picker.html
index af9e6359e58..96125f49882 100644
--- a/docs/0.34/picker.html
+++ b/docs/0.34/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.34/picker/index.html b/docs/0.34/picker/index.html
index af9e6359e58..96125f49882 100644
--- a/docs/0.34/picker/index.html
+++ b/docs/0.34/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.34/platform-specific-code.html b/docs/0.34/platform-specific-code.html
index c7ce4464591..106027dd202 100644
--- a/docs/0.34/platform-specific-code.html
+++ b/docs/0.34/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.34/platform-specific-code/index.html b/docs/0.34/platform-specific-code/index.html
index c7ce4464591..106027dd202 100644
--- a/docs/0.34/platform-specific-code/index.html
+++ b/docs/0.34/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.35/accessibility.html b/docs/0.35/accessibility.html
index 7c5b62c765f..e100ea706c7 100644
--- a/docs/0.35/accessibility.html
+++ b/docs/0.35/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
    Edit
    Accessibility
    Native App Accessibility (iOS and Android)
    
-
    Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
+        
    Edit
    Accessibility
    Native App Accessibility (Android and iOS)
    
+
    Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
 
    In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
    
 
    Making Apps Accessible
    
 
    Accessibility properties
    
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 

-
← AnimationsImproving User Experience →
Edit

Accessibility

Native App Accessibility (iOS and Android)

-

Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

+
Edit

Accessibility

Native App Accessibility (Android and iOS)

+

Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

Making Apps Accessible

Accessibility properties

@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService -
← AnimationsImproving User Experience →

0.35

Edit

Alert

Use Alert to display an alert dialog.

-

This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+

This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

On iOS, you can specify any number of buttons.

On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@

Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.35/alert/index.html b/docs/0.35/alert/index.html
index 8f469ebb16c..66d01706e36 100644
--- a/docs/0.35/alert/index.html
+++ b/docs/0.35/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
0.35
Edit
Alert
Use Alert to display an alert dialog.

-
This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+
This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

 
Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

 
On iOS, you can specify any number of buttons.

 
On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@
 
Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

 
Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

 
Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.35/clipboard.html b/docs/0.35/clipboard.html
index 7f5ffd295ed..71e7b08d5d4 100644
--- a/docs/0.35/clipboard.html
+++ b/docs/0.35/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.35/clipboard/index.html b/docs/0.35/clipboard/index.html
index 7f5ffd295ed..71e7b08d5d4 100644
--- a/docs/0.35/clipboard/index.html
+++ b/docs/0.35/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.35/components-and-apis.html b/docs/0.35/components-and-apis.html
index eaab025b355..1d6d3e73120 100644
--- a/docs/0.35/components-and-apis.html
+++ b/docs/0.35/components-and-apis.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.35/components-and-apis/index.html b/docs/0.35/components-and-apis/index.html
index eaab025b355..1d6d3e73120 100644
--- a/docs/0.35/components-and-apis/index.html
+++ b/docs/0.35/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.35/getting-started.html b/docs/0.35/getting-started.html
index d1baa9c5ace..80a038b7dbb 100644
--- a/docs/0.35/getting-started.html
+++ b/docs/0.35/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.35/getting-started/index.html b/docs/0.35/getting-started/index.html
index d1baa9c5ace..80a038b7dbb 100644
--- a/docs/0.35/getting-started/index.html
+++ b/docs/0.35/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.35/images.html b/docs/0.35/images.html
index 60da5b8caf0..3d0c22502b9 100644
--- a/docs/0.35/images.html
+++ b/docs/0.35/images.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.35/images/index.html b/docs/0.35/images/index.html
index 60da5b8caf0..3d0c22502b9 100644
--- a/docs/0.35/images/index.html
+++ b/docs/0.35/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.35/navigation.html b/docs/0.35/navigation.html
index 29823da56e7..a370169f754 100644
--- a/docs/0.35/navigation.html
+++ b/docs/0.35/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.35/navigation/index.html b/docs/0.35/navigation/index.html
index 29823da56e7..a370169f754 100644
--- a/docs/0.35/navigation/index.html
+++ b/docs/0.35/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.35/navigator.html b/docs/0.35/navigator.html
index 9872f0d851a..0cdfd6ee221 100644
--- a/docs/0.35/navigator.html
+++ b/docs/0.35/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.35/navigator/index.html b/docs/0.35/navigator/index.html
index 9872f0d851a..0cdfd6ee221 100644
--- a/docs/0.35/navigator/index.html
+++ b/docs/0.35/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.35/navigatorios.html b/docs/0.35/navigatorios.html
index de30b5172ff..48be6813e1f 100644
--- a/docs/0.35/navigatorios.html
+++ b/docs/0.35/navigatorios.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    NavigatorIOS
    NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.
    
-
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.
    
+
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.
    
 
    To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.
    
 
    import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.35/navigatorios/index.html b/docs/0.35/navigatorios/index.html
index de30b5172ff..48be6813e1f 100644
--- a/docs/0.35/navigatorios/index.html
+++ b/docs/0.35/navigatorios/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    NavigatorIOS
    NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.
    
-
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.
    
+
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.
    
 
    To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.
    
 
    import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.35/picker.html b/docs/0.35/picker.html
index 7c1e31963f2..35479cde625 100644
--- a/docs/0.35/picker.html
+++ b/docs/0.35/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.35/picker/index.html b/docs/0.35/picker/index.html
index 7c1e31963f2..35479cde625 100644
--- a/docs/0.35/picker/index.html
+++ b/docs/0.35/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.35/platform-specific-code.html b/docs/0.35/platform-specific-code.html
index a5982e28e02..84955041a6b 100644
--- a/docs/0.35/platform-specific-code.html
+++ b/docs/0.35/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.35/platform-specific-code/index.html b/docs/0.35/platform-specific-code/index.html
index a5982e28e02..84955041a6b 100644
--- a/docs/0.35/platform-specific-code/index.html
+++ b/docs/0.35/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.36/accessibility.html b/docs/0.36/accessibility.html
index 58944ea9576..551e3172de3 100644
--- a/docs/0.36/accessibility.html
+++ b/docs/0.36/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
    Edit
    Accessibility
    Native App Accessibility (iOS and Android)
    
-
    Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
+        
    Edit
    Accessibility
    Native App Accessibility (Android and iOS)
    
+
    Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
 
    In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
    
 
    Making Apps Accessible
    
 
    Accessibility properties
    
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 

-
← AnimationsImproving User Experience →
Edit

Accessibility

Native App Accessibility (iOS and Android)

-

Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

+
Edit

Accessibility

Native App Accessibility (Android and iOS)

+

Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

Making Apps Accessible

Accessibility properties

@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService -
← AnimationsImproving User Experience →

0.36

Edit

Alert

Use Alert to display an alert dialog.

-

This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+

This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

On iOS, you can specify any number of buttons.

On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@

Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.36/alert/index.html b/docs/0.36/alert/index.html
index e246649dd79..29746dcadcf 100644
--- a/docs/0.36/alert/index.html
+++ b/docs/0.36/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
0.36
Edit
Alert
Use Alert to display an alert dialog.

-
This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

+
This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

 
Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

 
On iOS, you can specify any number of buttons.

 
On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

@@ -25,7 +25,7 @@
 
Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

 
Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

 
Example usage:

-
// Works on both iOS and Android
+
// Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.36/clipboard.html b/docs/0.36/clipboard.html
index 9e862f5d9fb..dbbc9bc8259 100644
--- a/docs/0.36/clipboard.html
+++ b/docs/0.36/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.36/clipboard/index.html b/docs/0.36/clipboard/index.html
index 9e862f5d9fb..dbbc9bc8259 100644
--- a/docs/0.36/clipboard/index.html
+++ b/docs/0.36/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

+        
Edit
Clipboard
Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

 
Methods

 
    
 
  • getString
    • 
diff --git a/docs/0.36/components-and-apis.html b/docs/0.36/components-and-apis.html
index 2fb2badabca..14e332a927d 100644
--- a/docs/0.36/components-and-apis.html
+++ b/docs/0.36/components-and-apis.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.36/components-and-apis/index.html b/docs/0.36/components-and-apis/index.html
index 2fb2badabca..14e332a927d 100644
--- a/docs/0.36/components-and-apis/index.html
+++ b/docs/0.36/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
    
     
       
    Picker
    
-      
    Renders the native picker component on iOS and Android.
    
+      
    Renders the native picker component on Android and iOS.
    
         
   
    
   
    
@@ -290,7 +290,7 @@
   
    
     
       
    Clipboard
    
-      
    Provides an interface for setting and getting content from the clipboard on both iOS and Android.
    
+      
    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
    
         
   
    
   
    
diff --git a/docs/0.36/getting-started.html b/docs/0.36/getting-started.html
index 4285083bd4e..5bff09e6cba 100644
--- a/docs/0.36/getting-started.html
+++ b/docs/0.36/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.36/getting-started/index.html b/docs/0.36/getting-started/index.html
index 4285083bd4e..5bff09e6cba 100644
--- a/docs/0.36/getting-started/index.html
+++ b/docs/0.36/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
    
 
    
 
    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
    
-
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
    
+
    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
    
 
    
   Development OS:
   
diff --git a/docs/0.36/images.html b/docs/0.36/images.html
index a0dd6f6be5d..655de07c8f7 100644
--- a/docs/0.36/images.html
+++ b/docs/0.36/images.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.36/images/index.html b/docs/0.36/images/index.html
index a0dd6f6be5d..655de07c8f7 100644
--- a/docs/0.36/images/index.html
+++ b/docs/0.36/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    Images
    Static Image Resources
    
-
    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
+
    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
    
 
    <Image source={require('./my-icon.png')} />
 
    
 
    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
    
@@ -88,7 +88,7 @@
 
    On Windows, you might need to restart the packager if you add new images to your project.
    
 
    Here are some benefits that you get:
    
 
      
-
    1. Same system on iOS and Android.
      2. 
+
    2. Same system on Android and iOS.
      3. 
 
    3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. 
 
    4. No global namespace, i.e. you don't have to worry about name collisions.
      5. 
 
    5. Only the images that are actually used will be packaged into your app.
      6. 
diff --git a/docs/0.36/navigation.html b/docs/0.36/navigation.html
index 333795b8522..a3f1ca10d0a 100644
--- a/docs/0.36/navigation.html
+++ b/docs/0.36/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.36/navigation/index.html b/docs/0.36/navigation/index.html
index 333795b8522..a3f1ca10d0a 100644
--- a/docs/0.36/navigation/index.html
+++ b/docs/0.36/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
    Edit
    Navigating Between Screens
    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
    
-
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
    
-
    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
+
    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
    
+
    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
    
 
    React Navigation
    
 
    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
    
 
    The first step is to install in your project:
    
diff --git a/docs/0.36/navigator.html b/docs/0.36/navigator.html
index cc1101f8054..e8be476c3f9 100644
--- a/docs/0.36/navigator.html
+++ b/docs/0.36/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.36/navigator/index.html b/docs/0.36/navigator/index.html
index cc1101f8054..e8be476c3f9 100644
--- a/docs/0.36/navigator/index.html
+++ b/docs/0.36/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
+        
    Edit
    Navigator
    Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
    
 
    To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
    
 
    import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.36/navigatorios.html b/docs/0.36/navigatorios.html
index 6ba08f44d2f..43f6f61e675 100644
--- a/docs/0.36/navigatorios.html
+++ b/docs/0.36/navigatorios.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    NavigatorIOS
    NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.
    
-
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.
    
+
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.
    
 
    To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.
    
 
    import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.36/navigatorios/index.html b/docs/0.36/navigatorios/index.html
index 6ba08f44d2f..43f6f61e675 100644
--- a/docs/0.36/navigatorios/index.html
+++ b/docs/0.36/navigatorios/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    NavigatorIOS
    NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.
    
-
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.
    
+
    As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.
    
 
    To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.
    
 
    import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.36/picker.html b/docs/0.36/picker.html
index 93739b14d13..df6563132e8 100644
--- a/docs/0.36/picker.html
+++ b/docs/0.36/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.36/picker/index.html b/docs/0.36/picker/index.html
index 93739b14d13..df6563132e8 100644
--- a/docs/0.36/picker/index.html
+++ b/docs/0.36/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
    Edit
    Picker
    Renders the native picker component on iOS and Android. Example:
    
+        
    Edit
    Picker
    Renders the native picker component on Android and iOS. Example:
    
 
    <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.36/platform-specific-code.html b/docs/0.36/platform-specific-code.html
index 47a61b58f7f..058f6a55e8c 100644
--- a/docs/0.36/platform-specific-code.html
+++ b/docs/0.36/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.36/platform-specific-code/index.html b/docs/0.36/platform-specific-code/index.html
index 47a61b58f7f..058f6a55e8c 100644
--- a/docs/0.36/platform-specific-code/index.html
+++ b/docs/0.36/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
    
+        
    Edit
    Platform Specific Code
    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
    
 
    React Native provides two ways to organize your code and separate it by platform:
    
 
      
 
    • Using the Platform module.
      • 
diff --git a/docs/0.37/accessibility.html b/docs/0.37/accessibility.html
index e10d99c3eeb..a08a409a78e 100644
--- a/docs/0.37/accessibility.html
+++ b/docs/0.37/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
    Edit
    Accessibility
    Native App Accessibility (iOS and Android)
    
-
    Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
+        
    Edit
    Accessibility
    Native App Accessibility (Android and iOS)
    
+
    Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
    
 
    In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
    
 
    Making Apps Accessible
    
 
    Accessibility properties
    
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 

-
← AnimationsImproving User Experience →
Edit

Accessibility

Native App Accessibility (iOS and Android)

-

Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

+
Edit

Accessibility

Native App Accessibility (Android and iOS)

+

Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

Making Apps Accessible

Accessibility properties

@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService -
← AnimationsImproving User Experience →
Edit

Alert

Launches an alert dialog with the specified title and message.

Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

-

This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

+

This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

iOS

On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

Android

@@ -80,7 +80,7 @@
  • Two buttons mean 'negative', 'positive' (such as 'Cancel', 'OK')
  • Three buttons mean 'neutral', 'negative', 'positive' (such as 'Later', 'Cancel', 'OK')
    • -
    // Works on both iOS and Android
+
    // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.37/alert/index.html b/docs/0.37/alert/index.html
index b367ab5d41d..977c42de60d 100644
--- a/docs/0.37/alert/index.html
+++ b/docs/0.37/alert/index.html
@@ -70,7 +70,7 @@
             });
    Edit

    Alert

    Launches an alert dialog with the specified title and message.

    Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

    -

    This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

    +

    This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

    iOS

    On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

    Android

    @@ -80,7 +80,7 @@
  • Two buttons mean 'negative', 'positive' (such as 'Cancel', 'OK')
  • Three buttons mean 'neutral', 'negative', 'positive' (such as 'Later', 'Cancel', 'OK')
    • -
    // Works on both iOS and Android
+
    // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.37/clipboard.html b/docs/0.37/clipboard.html
index 7780b67289b..de3c727d029 100644
--- a/docs/0.37/clipboard.html
+++ b/docs/0.37/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

    +
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

    Methods

    • getString
      • diff --git a/docs/0.37/clipboard/index.html b/docs/0.37/clipboard/index.html index 7780b67289b..de3c727d029 100644 --- a/docs/0.37/clipboard/index.html +++ b/docs/0.37/clipboard/index.html @@ -1,4 +1,4 @@ -Clipboard · React Native
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

    +
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

    Methods

    • getString
      • diff --git a/docs/0.37/components-and-apis.html b/docs/0.37/components-and-apis.html index 589fbe35599..d7d807b9cd2 100644 --- a/docs/0.37/components-and-apis.html +++ b/docs/0.37/components-and-apis.html @@ -130,7 +130,7 @@

      Picker

      -

      Renders the native picker component on iOS and Android.

      +

      Renders the native picker component on Android and iOS.
      @@ -290,7 +290,7 @@

      Clipboard

      -

      Provides an interface for setting and getting content from the clipboard on both iOS and Android.

      +

      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
      diff --git a/docs/0.37/components-and-apis/index.html b/docs/0.37/components-and-apis/index.html index 589fbe35599..d7d807b9cd2 100644 --- a/docs/0.37/components-and-apis/index.html +++ b/docs/0.37/components-and-apis/index.html @@ -130,7 +130,7 @@

      Picker

      -

      Renders the native picker component on iOS and Android.

      +

      Renders the native picker component on Android and iOS.
      @@ -290,7 +290,7 @@

      Clipboard

      -

      Provides an interface for setting and getting content from the clipboard on both iOS and Android.

      +

      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
      diff --git a/docs/0.37/getting-started.html b/docs/0.37/getting-started.html index 5d6190fbffd..6358928b596 100644 --- a/docs/0.37/getting-started.html +++ b/docs/0.37/getting-started.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

      -

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

      +

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

      Development OS: diff --git a/docs/0.37/getting-started/index.html b/docs/0.37/getting-started/index.html index 5d6190fbffd..6358928b596 100644 --- a/docs/0.37/getting-started/index.html +++ b/docs/0.37/getting-started/index.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

      -

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

      +

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

      Development OS: diff --git a/docs/0.37/images.html b/docs/0.37/images.html index 455bde228bb..50b3d657c41 100644 --- a/docs/0.37/images.html +++ b/docs/0.37/images.html @@ -69,7 +69,7 @@ } });
      Edit

      Images

      Static Image Resources

      -

      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      +

      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      <Image source={require('./my-icon.png')} />

      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

      @@ -88,7 +88,7 @@

      On Windows, you might need to restart the packager if you add new images to your project.

      Here are some benefits that you get:

        -
      1. Same system on iOS and Android.
        2. +
      2. Same system on Android and iOS.
      3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. No global namespace, i.e. you don't have to worry about name collisions.
      5. Only the images that are actually used will be packaged into your app.
        6. diff --git a/docs/0.37/images/index.html b/docs/0.37/images/index.html index 455bde228bb..50b3d657c41 100644 --- a/docs/0.37/images/index.html +++ b/docs/0.37/images/index.html @@ -69,7 +69,7 @@ } });
      Edit

      Images

      Static Image Resources

      -

      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      +

      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      <Image source={require('./my-icon.png')} />

      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

      @@ -88,7 +88,7 @@

      On Windows, you might need to restart the packager if you add new images to your project.

      Here are some benefits that you get:

        -
      1. Same system on iOS and Android.
        2. +
      2. Same system on Android and iOS.
      3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. No global namespace, i.e. you don't have to worry about name collisions.
      5. Only the images that are actually used will be packaged into your app.
        6. diff --git a/docs/0.37/navigation.html b/docs/0.37/navigation.html index 7dbb172ca5a..fbc56566f28 100644 --- a/docs/0.37/navigation.html +++ b/docs/0.37/navigation.html @@ -69,8 +69,8 @@ } });
      Edit

      Navigating Between Screens

      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

      -

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

      -

      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      +

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

      +

      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      React Navigation

      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

      The first step is to install in your project:

      diff --git a/docs/0.37/navigation/index.html b/docs/0.37/navigation/index.html index 7dbb172ca5a..fbc56566f28 100644 --- a/docs/0.37/navigation/index.html +++ b/docs/0.37/navigation/index.html @@ -69,8 +69,8 @@ } });
      Edit

      Navigating Between Screens

      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

      -

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

      -

      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      +

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

      +

      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      React Navigation

      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

      The first step is to install in your project:

      diff --git a/docs/0.37/navigator.html b/docs/0.37/navigator.html index 163452f0cb2..73d948de19c 100644 --- a/docs/0.37/navigator.html +++ b/docs/0.37/navigator.html @@ -1,4 +1,4 @@ -Navigator · React Native
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      +
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.

      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.37/navigator/index.html b/docs/0.37/navigator/index.html
index 163452f0cb2..73d948de19c 100644
--- a/docs/0.37/navigator/index.html
+++ b/docs/0.37/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      +
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.

      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.37/navigatorios.html b/docs/0.37/navigatorios.html
index 68f304f76cf..c468b6d37c6 100644
--- a/docs/0.37/navigatorios.html
+++ b/docs/0.37/navigatorios.html
@@ -69,7 +69,7 @@
               }
             });
      Edit

      NavigatorIOS

      NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.

      -

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.

      +

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.

      To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.

      import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.37/navigatorios/index.html b/docs/0.37/navigatorios/index.html
index 68f304f76cf..c468b6d37c6 100644
--- a/docs/0.37/navigatorios/index.html
+++ b/docs/0.37/navigatorios/index.html
@@ -69,7 +69,7 @@
               }
             });
      Edit

      NavigatorIOS

      NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.

      -

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.

      +

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.

      To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.

      import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.37/picker.html b/docs/0.37/picker.html
index 375c07e6b50..5c3dfa89468 100644
--- a/docs/0.37/picker.html
+++ b/docs/0.37/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
      Edit

      Picker

      Renders the native picker component on iOS and Android. Example:

      +
      Edit

      Picker

      Renders the native picker component on Android and iOS. Example:

      <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.37/picker/index.html b/docs/0.37/picker/index.html
index 375c07e6b50..5c3dfa89468 100644
--- a/docs/0.37/picker/index.html
+++ b/docs/0.37/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
      Edit

      Picker

      Renders the native picker component on iOS and Android. Example:

      +
      Edit

      Picker

      Renders the native picker component on Android and iOS. Example:

      <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.37/platform-specific-code.html b/docs/0.37/platform-specific-code.html
index d59437a1b16..dc837886856 100644
--- a/docs/0.37/platform-specific-code.html
+++ b/docs/0.37/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

      +
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

      React Native provides two ways to organize your code and separate it by platform:

      • Using the Platform module.
        • diff --git a/docs/0.37/platform-specific-code/index.html b/docs/0.37/platform-specific-code/index.html index d59437a1b16..dc837886856 100644 --- a/docs/0.37/platform-specific-code/index.html +++ b/docs/0.37/platform-specific-code/index.html @@ -1,4 +1,4 @@ -Platform Specific Code · React Native
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

      +
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

      React Native provides two ways to organize your code and separate it by platform:

      • Using the Platform module.
        • diff --git a/docs/0.38/accessibility.html b/docs/0.38/accessibility.html index 99f6461bd5a..ed5a84844d2 100644 --- a/docs/0.38/accessibility.html +++ b/docs/0.38/accessibility.html @@ -1,4 +1,4 @@ -Accessibility · React Native
      Edit

      Accessibility

      Native App Accessibility (iOS and Android)

      -

      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      +
      Edit

      Accessibility

      Native App Accessibility (Android and iOS)

      +

      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

      Making Apps Accessible

      Accessibility properties

      @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService       -
      ← AnimationsImproving User Experience →
      Edit

      Accessibility

      Native App Accessibility (iOS and Android)

      -

      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      +
      Edit

      Accessibility

      Native App Accessibility (Android and iOS)

      +

      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

      Making Apps Accessible

      Accessibility properties

      @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService       -
      ← AnimationsImproving User Experience →
      Edit

      Alert

      Launches an alert dialog with the specified title and message.

      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

      -

      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

      +

      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

      iOS

      On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

      Android

      @@ -80,7 +80,7 @@
    • Two buttons mean 'negative', 'positive' (such as 'Cancel', 'OK')
    • Three buttons mean 'neutral', 'negative', 'positive' (such as 'Later', 'Cancel', 'OK')
    -
    // Works on both iOS and Android
+
    // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.38/alert/index.html b/docs/0.38/alert/index.html
index 992158c3af2..e18c7f86c43 100644
--- a/docs/0.38/alert/index.html
+++ b/docs/0.38/alert/index.html
@@ -70,7 +70,7 @@
             });
    Edit

    Alert

    Launches an alert dialog with the specified title and message.

    Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

    -

    This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

    +

    This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

    iOS

    On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

    Android

    @@ -80,7 +80,7 @@
  • Two buttons mean 'negative', 'positive' (such as 'Cancel', 'OK')
  • Three buttons mean 'neutral', 'negative', 'positive' (such as 'Later', 'Cancel', 'OK')
    • -
    // Works on both iOS and Android
+
    // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.38/clipboard.html b/docs/0.38/clipboard.html
index 1d7e08426fe..24c412a2768 100644
--- a/docs/0.38/clipboard.html
+++ b/docs/0.38/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

    +
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

    Methods

    • getString
      • diff --git a/docs/0.38/clipboard/index.html b/docs/0.38/clipboard/index.html index 1d7e08426fe..24c412a2768 100644 --- a/docs/0.38/clipboard/index.html +++ b/docs/0.38/clipboard/index.html @@ -1,4 +1,4 @@ -Clipboard · React Native
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

    +
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

    Methods

    • getString
      • diff --git a/docs/0.38/components-and-apis.html b/docs/0.38/components-and-apis.html index b6e270e5ba1..f7e013cd089 100644 --- a/docs/0.38/components-and-apis.html +++ b/docs/0.38/components-and-apis.html @@ -130,7 +130,7 @@

      Picker

      -

      Renders the native picker component on iOS and Android.

      +

      Renders the native picker component on Android and iOS.
      @@ -290,7 +290,7 @@

      Clipboard

      -

      Provides an interface for setting and getting content from the clipboard on both iOS and Android.

      +

      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
      diff --git a/docs/0.38/components-and-apis/index.html b/docs/0.38/components-and-apis/index.html index b6e270e5ba1..f7e013cd089 100644 --- a/docs/0.38/components-and-apis/index.html +++ b/docs/0.38/components-and-apis/index.html @@ -130,7 +130,7 @@

      Picker

      -

      Renders the native picker component on iOS and Android.

      +

      Renders the native picker component on Android and iOS.
      @@ -290,7 +290,7 @@

      Clipboard

      -

      Provides an interface for setting and getting content from the clipboard on both iOS and Android.

      +

      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
      diff --git a/docs/0.38/getting-started.html b/docs/0.38/getting-started.html index 20541b0b1b3..e5f6bf5e74d 100644 --- a/docs/0.38/getting-started.html +++ b/docs/0.38/getting-started.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

      -

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

      +

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

      Development OS: diff --git a/docs/0.38/getting-started/index.html b/docs/0.38/getting-started/index.html index 20541b0b1b3..e5f6bf5e74d 100644 --- a/docs/0.38/getting-started/index.html +++ b/docs/0.38/getting-started/index.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

      -

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

      +

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

      Development OS: diff --git a/docs/0.38/images.html b/docs/0.38/images.html index 959136c78c7..7b306ed3006 100644 --- a/docs/0.38/images.html +++ b/docs/0.38/images.html @@ -69,7 +69,7 @@ } });
      Edit

      Images

      Static Image Resources

      -

      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      +

      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      <Image source={require('./my-icon.png')} />

      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

      @@ -88,7 +88,7 @@

      On Windows, you might need to restart the packager if you add new images to your project.

      Here are some benefits that you get:

        -
      1. Same system on iOS and Android.
        2. +
      2. Same system on Android and iOS.
      3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. No global namespace, i.e. you don't have to worry about name collisions.
      5. Only the images that are actually used will be packaged into your app.
        6. diff --git a/docs/0.38/images/index.html b/docs/0.38/images/index.html index 959136c78c7..7b306ed3006 100644 --- a/docs/0.38/images/index.html +++ b/docs/0.38/images/index.html @@ -69,7 +69,7 @@ } });
      Edit

      Images

      Static Image Resources

      -

      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      +

      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      <Image source={require('./my-icon.png')} />

      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

      @@ -88,7 +88,7 @@

      On Windows, you might need to restart the packager if you add new images to your project.

      Here are some benefits that you get:

        -
      1. Same system on iOS and Android.
        2. +
      2. Same system on Android and iOS.
      3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. No global namespace, i.e. you don't have to worry about name collisions.
      5. Only the images that are actually used will be packaged into your app.
        6. diff --git a/docs/0.38/navigation.html b/docs/0.38/navigation.html index 0e2ff4ad1f2..2a1b25ecca5 100644 --- a/docs/0.38/navigation.html +++ b/docs/0.38/navigation.html @@ -69,8 +69,8 @@ } });
      Edit

      Navigating Between Screens

      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

      -

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

      -

      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      +

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

      +

      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      React Navigation

      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

      The first step is to install in your project:

      diff --git a/docs/0.38/navigation/index.html b/docs/0.38/navigation/index.html index 0e2ff4ad1f2..2a1b25ecca5 100644 --- a/docs/0.38/navigation/index.html +++ b/docs/0.38/navigation/index.html @@ -69,8 +69,8 @@ } });
      Edit

      Navigating Between Screens

      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

      -

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

      -

      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      +

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

      +

      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      React Navigation

      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

      The first step is to install in your project:

      diff --git a/docs/0.38/navigator.html b/docs/0.38/navigator.html index dfb9e2a6c09..c5a0c2f9925 100644 --- a/docs/0.38/navigator.html +++ b/docs/0.38/navigator.html @@ -1,4 +1,4 @@ -Navigator · React Native
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      +
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.

      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.38/navigator/index.html b/docs/0.38/navigator/index.html
index dfb9e2a6c09..c5a0c2f9925 100644
--- a/docs/0.38/navigator/index.html
+++ b/docs/0.38/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      +
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.

      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.38/navigatorios.html b/docs/0.38/navigatorios.html
index 0da9dacc53b..1e1034c2b2b 100644
--- a/docs/0.38/navigatorios.html
+++ b/docs/0.38/navigatorios.html
@@ -69,7 +69,7 @@
               }
             });
      Edit

      NavigatorIOS

      NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.

      -

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.

      +

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.

      To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.

      import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.38/navigatorios/index.html b/docs/0.38/navigatorios/index.html
index 0da9dacc53b..1e1034c2b2b 100644
--- a/docs/0.38/navigatorios/index.html
+++ b/docs/0.38/navigatorios/index.html
@@ -69,7 +69,7 @@
               }
             });
      Edit

      NavigatorIOS

      NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.

      -

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.

      +

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.

      To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.

      import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.38/picker.html b/docs/0.38/picker.html
index 9ced3074b15..f1aafc9f9a7 100644
--- a/docs/0.38/picker.html
+++ b/docs/0.38/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
      Edit

      Picker

      Renders the native picker component on iOS and Android. Example:

      +
      Edit

      Picker

      Renders the native picker component on Android and iOS. Example:

      <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.38/picker/index.html b/docs/0.38/picker/index.html
index 9ced3074b15..f1aafc9f9a7 100644
--- a/docs/0.38/picker/index.html
+++ b/docs/0.38/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
      Edit

      Picker

      Renders the native picker component on iOS and Android. Example:

      +
      Edit

      Picker

      Renders the native picker component on Android and iOS. Example:

      <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.38/platform-specific-code.html b/docs/0.38/platform-specific-code.html
index f829bd9904a..c4c8c85694e 100644
--- a/docs/0.38/platform-specific-code.html
+++ b/docs/0.38/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

      +
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

      React Native provides two ways to organize your code and separate it by platform:

      • Using the Platform module.
        • diff --git a/docs/0.38/platform-specific-code/index.html b/docs/0.38/platform-specific-code/index.html index f829bd9904a..c4c8c85694e 100644 --- a/docs/0.38/platform-specific-code/index.html +++ b/docs/0.38/platform-specific-code/index.html @@ -1,4 +1,4 @@ -Platform Specific Code · React Native
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

      +
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

      React Native provides two ways to organize your code and separate it by platform:

      • Using the Platform module.
        • diff --git a/docs/0.39/accessibility.html b/docs/0.39/accessibility.html index f34abdf489a..f83652416a5 100644 --- a/docs/0.39/accessibility.html +++ b/docs/0.39/accessibility.html @@ -1,4 +1,4 @@ -Accessibility · React Native
      Edit

      Accessibility

      Native App Accessibility (iOS and Android)

      -

      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      +
      Edit

      Accessibility

      Native App Accessibility (Android and iOS)

      +

      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

      Making Apps Accessible

      Accessibility properties

      @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService       -
      ← AnimationsImproving User Experience →
      Edit

      Accessibility

      Native App Accessibility (iOS and Android)

      -

      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      +
      Edit

      Accessibility

      Native App Accessibility (Android and iOS)

      +

      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

      Making Apps Accessible

      Accessibility properties

      @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService       -
      ← AnimationsImproving User Experience →
      Edit

      Alert

      Launches an alert dialog with the specified title and message.

      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

      -

      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

      +

      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

      iOS

      On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

      Android

      @@ -80,7 +80,7 @@
    • Two buttons mean 'negative', 'positive' (such as 'Cancel', 'OK')
    • Three buttons mean 'neutral', 'negative', 'positive' (such as 'Later', 'Cancel', 'OK')
    -
    // Works on both iOS and Android
+
    // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.39/alert/index.html b/docs/0.39/alert/index.html
index a9229333ba3..8fdd119ea3f 100644
--- a/docs/0.39/alert/index.html
+++ b/docs/0.39/alert/index.html
@@ -70,7 +70,7 @@
             });
    Edit

    Alert

    Launches an alert dialog with the specified title and message.

    Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

    -

    This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

    +

    This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

    iOS

    On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

    Android

    @@ -80,7 +80,7 @@
  • Two buttons mean 'negative', 'positive' (such as 'Cancel', 'OK')
  • Three buttons mean 'neutral', 'negative', 'positive' (such as 'Later', 'Cancel', 'OK')
    • -
    // Works on both iOS and Android
+
    // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.39/clipboard.html b/docs/0.39/clipboard.html
index 94a62adfc17..5f36893d762 100644
--- a/docs/0.39/clipboard.html
+++ b/docs/0.39/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

    +
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

    Methods

    • getString
      • diff --git a/docs/0.39/clipboard/index.html b/docs/0.39/clipboard/index.html index 94a62adfc17..5f36893d762 100644 --- a/docs/0.39/clipboard/index.html +++ b/docs/0.39/clipboard/index.html @@ -1,4 +1,4 @@ -Clipboard · React Native
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

    +
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

    Methods

    • getString
      • diff --git a/docs/0.39/components-and-apis.html b/docs/0.39/components-and-apis.html index 1f3d68e1aed..ce3dd4f532e 100644 --- a/docs/0.39/components-and-apis.html +++ b/docs/0.39/components-and-apis.html @@ -130,7 +130,7 @@

      Picker

      -

      Renders the native picker component on iOS and Android.

      +

      Renders the native picker component on Android and iOS.
      @@ -290,7 +290,7 @@

      Clipboard

      -

      Provides an interface for setting and getting content from the clipboard on both iOS and Android.

      +

      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
      diff --git a/docs/0.39/components-and-apis/index.html b/docs/0.39/components-and-apis/index.html index 1f3d68e1aed..ce3dd4f532e 100644 --- a/docs/0.39/components-and-apis/index.html +++ b/docs/0.39/components-and-apis/index.html @@ -130,7 +130,7 @@

      Picker

      -

      Renders the native picker component on iOS and Android.

      +

      Renders the native picker component on Android and iOS.
      @@ -290,7 +290,7 @@

      Clipboard

      -

      Provides an interface for setting and getting content from the clipboard on both iOS and Android.

      +

      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
      diff --git a/docs/0.39/getting-started.html b/docs/0.39/getting-started.html index 9c6862a7d25..57fd0dcba31 100644 --- a/docs/0.39/getting-started.html +++ b/docs/0.39/getting-started.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

      -

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

      +

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

      Development OS: diff --git a/docs/0.39/getting-started/index.html b/docs/0.39/getting-started/index.html index 9c6862a7d25..57fd0dcba31 100644 --- a/docs/0.39/getting-started/index.html +++ b/docs/0.39/getting-started/index.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

      -

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

      +

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

      Development OS: diff --git a/docs/0.39/images.html b/docs/0.39/images.html index 37c347a181f..440d5fdca75 100644 --- a/docs/0.39/images.html +++ b/docs/0.39/images.html @@ -69,7 +69,7 @@ } });
      Edit

      Images

      Static Image Resources

      -

      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      +

      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      <Image source={require('./my-icon.png')} />

      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

      @@ -88,7 +88,7 @@

      On Windows, you might need to restart the packager if you add new images to your project.

      Here are some benefits that you get:

        -
      1. Same system on iOS and Android.
        2. +
      2. Same system on Android and iOS.
      3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. No global namespace, i.e. you don't have to worry about name collisions.
      5. Only the images that are actually used will be packaged into your app.
        6. diff --git a/docs/0.39/images/index.html b/docs/0.39/images/index.html index 37c347a181f..440d5fdca75 100644 --- a/docs/0.39/images/index.html +++ b/docs/0.39/images/index.html @@ -69,7 +69,7 @@ } });
      Edit

      Images

      Static Image Resources

      -

      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      +

      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      <Image source={require('./my-icon.png')} />

      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

      @@ -88,7 +88,7 @@

      On Windows, you might need to restart the packager if you add new images to your project.

      Here are some benefits that you get:

        -
      1. Same system on iOS and Android.
        2. +
      2. Same system on Android and iOS.
      3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. No global namespace, i.e. you don't have to worry about name collisions.
      5. Only the images that are actually used will be packaged into your app.
        6. diff --git a/docs/0.39/navigation.html b/docs/0.39/navigation.html index 609dca825fd..21034e6cbfa 100644 --- a/docs/0.39/navigation.html +++ b/docs/0.39/navigation.html @@ -69,8 +69,8 @@ } });
      Edit

      Navigating Between Screens

      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

      -

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

      -

      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      +

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

      +

      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      React Navigation

      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

      The first step is to install in your project:

      diff --git a/docs/0.39/navigation/index.html b/docs/0.39/navigation/index.html index 609dca825fd..21034e6cbfa 100644 --- a/docs/0.39/navigation/index.html +++ b/docs/0.39/navigation/index.html @@ -69,8 +69,8 @@ } });
      Edit

      Navigating Between Screens

      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

      -

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

      -

      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      +

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

      +

      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      React Navigation

      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

      The first step is to install in your project:

      diff --git a/docs/0.39/navigator.html b/docs/0.39/navigator.html index ce9e31b7eb0..93608bafa0a 100644 --- a/docs/0.39/navigator.html +++ b/docs/0.39/navigator.html @@ -1,4 +1,4 @@ -Navigator · React Native
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      +
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.

      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.39/navigator/index.html b/docs/0.39/navigator/index.html
index ce9e31b7eb0..93608bafa0a 100644
--- a/docs/0.39/navigator/index.html
+++ b/docs/0.39/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      +
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.

      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.39/navigatorios.html b/docs/0.39/navigatorios.html
index 16f0ee53ced..35ae77be720 100644
--- a/docs/0.39/navigatorios.html
+++ b/docs/0.39/navigatorios.html
@@ -69,7 +69,7 @@
               }
             });
      Edit

      NavigatorIOS

      NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.

      -

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.

      +

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.

      To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.

      import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.39/navigatorios/index.html b/docs/0.39/navigatorios/index.html
index 16f0ee53ced..35ae77be720 100644
--- a/docs/0.39/navigatorios/index.html
+++ b/docs/0.39/navigatorios/index.html
@@ -69,7 +69,7 @@
               }
             });
      Edit

      NavigatorIOS

      NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.

      -

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.

      +

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.

      To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.

      import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.39/picker.html b/docs/0.39/picker.html
index 83b8f37b773..560a3867956 100644
--- a/docs/0.39/picker.html
+++ b/docs/0.39/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
      Edit

      Picker

      Renders the native picker component on iOS and Android. Example:

      +
      Edit

      Picker

      Renders the native picker component on Android and iOS. Example:

      <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.39/picker/index.html b/docs/0.39/picker/index.html
index 83b8f37b773..560a3867956 100644
--- a/docs/0.39/picker/index.html
+++ b/docs/0.39/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
      Edit

      Picker

      Renders the native picker component on iOS and Android. Example:

      +
      Edit

      Picker

      Renders the native picker component on Android and iOS. Example:

      <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.39/platform-specific-code.html b/docs/0.39/platform-specific-code.html
index 429b88634ec..bf21d764a2d 100644
--- a/docs/0.39/platform-specific-code.html
+++ b/docs/0.39/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

      +
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

      React Native provides two ways to organize your code and separate it by platform:

      • Using the Platform module.
        • diff --git a/docs/0.39/platform-specific-code/index.html b/docs/0.39/platform-specific-code/index.html index 429b88634ec..bf21d764a2d 100644 --- a/docs/0.39/platform-specific-code/index.html +++ b/docs/0.39/platform-specific-code/index.html @@ -1,4 +1,4 @@ -Platform Specific Code · React Native
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

      +
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

      React Native provides two ways to organize your code and separate it by platform:

      • Using the Platform module.
        • diff --git a/docs/0.40/accessibility.html b/docs/0.40/accessibility.html index ac4609918ab..fea4abeef9c 100644 --- a/docs/0.40/accessibility.html +++ b/docs/0.40/accessibility.html @@ -1,4 +1,4 @@ -Accessibility · React Native
      Edit

      Accessibility

      Native App Accessibility (iOS and Android)

      -

      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      +
      Edit

      Accessibility

      Native App Accessibility (Android and iOS)

      +

      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

      Making Apps Accessible

      Accessibility properties

      @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService       -
      ← AnimationsImproving User Experience →
      Edit

      Accessibility

      Native App Accessibility (iOS and Android)

      -

      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      +
      Edit

      Accessibility

      Native App Accessibility (Android and iOS)

      +

      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

      Making Apps Accessible

      Accessibility properties

      @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService       -
      ← AnimationsImproving User Experience →
      Edit

      Alert

      Launches an alert dialog with the specified title and message.

      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

      -

      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

      +

      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

      iOS

      On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

      Android

      @@ -80,7 +80,7 @@
    • Two buttons mean 'negative', 'positive' (such as 'Cancel', 'OK')
    • Three buttons mean 'neutral', 'negative', 'positive' (such as 'Later', 'Cancel', 'OK')
    -
    // Works on both iOS and Android
+
    // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.40/alert/index.html b/docs/0.40/alert/index.html
index 9e45f398a45..7e415018f72 100644
--- a/docs/0.40/alert/index.html
+++ b/docs/0.40/alert/index.html
@@ -70,7 +70,7 @@
             });
    Edit

    Alert

    Launches an alert dialog with the specified title and message.

    Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

    -

    This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

    +

    This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

    iOS

    On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

    Android

    @@ -80,7 +80,7 @@
  • Two buttons mean 'negative', 'positive' (such as 'Cancel', 'OK')
  • Three buttons mean 'neutral', 'negative', 'positive' (such as 'Later', 'Cancel', 'OK')
    • -
    // Works on both iOS and Android
+
    // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.40/clipboard.html b/docs/0.40/clipboard.html
index 1a691415ad1..f19a338664e 100644
--- a/docs/0.40/clipboard.html
+++ b/docs/0.40/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

    +
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

    Methods

    • getString
      • diff --git a/docs/0.40/clipboard/index.html b/docs/0.40/clipboard/index.html index 1a691415ad1..f19a338664e 100644 --- a/docs/0.40/clipboard/index.html +++ b/docs/0.40/clipboard/index.html @@ -1,4 +1,4 @@ -Clipboard · React Native
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

    +
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

    Methods

    • getString
      • diff --git a/docs/0.40/components-and-apis.html b/docs/0.40/components-and-apis.html index 44c6234d50b..7959281bce3 100644 --- a/docs/0.40/components-and-apis.html +++ b/docs/0.40/components-and-apis.html @@ -130,7 +130,7 @@

      Picker

      -

      Renders the native picker component on iOS and Android.

      +

      Renders the native picker component on Android and iOS.
      @@ -290,7 +290,7 @@

      Clipboard

      -

      Provides an interface for setting and getting content from the clipboard on both iOS and Android.

      +

      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
      diff --git a/docs/0.40/components-and-apis/index.html b/docs/0.40/components-and-apis/index.html index 44c6234d50b..7959281bce3 100644 --- a/docs/0.40/components-and-apis/index.html +++ b/docs/0.40/components-and-apis/index.html @@ -130,7 +130,7 @@

      Picker

      -

      Renders the native picker component on iOS and Android.

      +

      Renders the native picker component on Android and iOS.
      @@ -290,7 +290,7 @@

      Clipboard

      -

      Provides an interface for setting and getting content from the clipboard on both iOS and Android.

      +

      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
      diff --git a/docs/0.40/getting-started.html b/docs/0.40/getting-started.html index 49fa98a4873..fa8b2d078ef 100644 --- a/docs/0.40/getting-started.html +++ b/docs/0.40/getting-started.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

      -

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

      +

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

      Development OS: diff --git a/docs/0.40/getting-started/index.html b/docs/0.40/getting-started/index.html index 49fa98a4873..fa8b2d078ef 100644 --- a/docs/0.40/getting-started/index.html +++ b/docs/0.40/getting-started/index.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

      -

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

      +

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

      Development OS: diff --git a/docs/0.40/images.html b/docs/0.40/images.html index 40e406e7412..3b8a872ca75 100644 --- a/docs/0.40/images.html +++ b/docs/0.40/images.html @@ -69,7 +69,7 @@ } });
      Edit

      Images

      Static Image Resources

      -

      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      +

      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      <Image source={require('./my-icon.png')} />

      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

      @@ -88,7 +88,7 @@

      On Windows, you might need to restart the packager if you add new images to your project.

      Here are some benefits that you get:

        -
      1. Same system on iOS and Android.
        2. +
      2. Same system on Android and iOS.
      3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. No global namespace, i.e. you don't have to worry about name collisions.
      5. Only the images that are actually used will be packaged into your app.
        6. diff --git a/docs/0.40/images/index.html b/docs/0.40/images/index.html index 40e406e7412..3b8a872ca75 100644 --- a/docs/0.40/images/index.html +++ b/docs/0.40/images/index.html @@ -69,7 +69,7 @@ } });
      Edit

      Images

      Static Image Resources

      -

      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      +

      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      <Image source={require('./my-icon.png')} />

      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

      @@ -88,7 +88,7 @@

      On Windows, you might need to restart the packager if you add new images to your project.

      Here are some benefits that you get:

        -
      1. Same system on iOS and Android.
        2. +
      2. Same system on Android and iOS.
      3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. No global namespace, i.e. you don't have to worry about name collisions.
      5. Only the images that are actually used will be packaged into your app.
        6. diff --git a/docs/0.40/navigation.html b/docs/0.40/navigation.html index 7bd3b4b770e..d5992cd9de8 100644 --- a/docs/0.40/navigation.html +++ b/docs/0.40/navigation.html @@ -69,8 +69,8 @@ } });
      Edit

      Navigating Between Screens

      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

      -

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

      -

      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      +

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

      +

      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      React Navigation

      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

      The first step is to install in your project:

      diff --git a/docs/0.40/navigation/index.html b/docs/0.40/navigation/index.html index 7bd3b4b770e..d5992cd9de8 100644 --- a/docs/0.40/navigation/index.html +++ b/docs/0.40/navigation/index.html @@ -69,8 +69,8 @@ } });
      Edit

      Navigating Between Screens

      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

      -

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

      -

      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      +

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

      +

      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      React Navigation

      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

      The first step is to install in your project:

      diff --git a/docs/0.40/navigator.html b/docs/0.40/navigator.html index 04d78aabd5b..f433a1d1a6a 100644 --- a/docs/0.40/navigator.html +++ b/docs/0.40/navigator.html @@ -1,4 +1,4 @@ -Navigator · React Native
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      +
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.

      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.40/navigator/index.html b/docs/0.40/navigator/index.html
index 04d78aabd5b..f433a1d1a6a 100644
--- a/docs/0.40/navigator/index.html
+++ b/docs/0.40/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      +
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.

      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.40/navigatorios.html b/docs/0.40/navigatorios.html
index 7263244dffc..f6618474bd9 100644
--- a/docs/0.40/navigatorios.html
+++ b/docs/0.40/navigatorios.html
@@ -69,7 +69,7 @@
               }
             });
      Edit

      NavigatorIOS

      NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.

      -

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.

      +

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.

      To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.

      import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.40/navigatorios/index.html b/docs/0.40/navigatorios/index.html
index 7263244dffc..f6618474bd9 100644
--- a/docs/0.40/navigatorios/index.html
+++ b/docs/0.40/navigatorios/index.html
@@ -69,7 +69,7 @@
               }
             });
      Edit

      NavigatorIOS

      NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.

      -

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.

      +

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.

      To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.

      import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.40/picker.html b/docs/0.40/picker.html
index fd8480d5a53..359005f9155 100644
--- a/docs/0.40/picker.html
+++ b/docs/0.40/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
      Edit

      Picker

      Renders the native picker component on iOS and Android. Example:

      +
      Edit

      Picker

      Renders the native picker component on Android and iOS. Example:

      <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.40/picker/index.html b/docs/0.40/picker/index.html
index fd8480d5a53..359005f9155 100644
--- a/docs/0.40/picker/index.html
+++ b/docs/0.40/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
      Edit

      Picker

      Renders the native picker component on iOS and Android. Example:

      +
      Edit

      Picker

      Renders the native picker component on Android and iOS. Example:

      <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.40/platform-specific-code.html b/docs/0.40/platform-specific-code.html
index 4e8e5480058..4965161102f 100644
--- a/docs/0.40/platform-specific-code.html
+++ b/docs/0.40/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

      +
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

      React Native provides two ways to organize your code and separate it by platform:

      • Using the Platform module.
        • diff --git a/docs/0.40/platform-specific-code/index.html b/docs/0.40/platform-specific-code/index.html index 4e8e5480058..4965161102f 100644 --- a/docs/0.40/platform-specific-code/index.html +++ b/docs/0.40/platform-specific-code/index.html @@ -1,4 +1,4 @@ -Platform Specific Code · React Native
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

      +
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

      React Native provides two ways to organize your code and separate it by platform:

      • Using the Platform module.
        • diff --git a/docs/0.41/accessibility.html b/docs/0.41/accessibility.html index 02881e45118..0896c6f1a50 100644 --- a/docs/0.41/accessibility.html +++ b/docs/0.41/accessibility.html @@ -1,4 +1,4 @@ -Accessibility · React Native
      Edit

      Accessibility

      Native App Accessibility (iOS and Android)

      -

      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      +
      Edit

      Accessibility

      Native App Accessibility (Android and iOS)

      +

      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

      Making Apps Accessible

      Accessibility properties

      @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService       -
      ← AnimationsImproving User Experience →
      Edit

      Accessibility

      Native App Accessibility (iOS and Android)

      -

      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      +
      Edit

      Accessibility

      Native App Accessibility (Android and iOS)

      +

      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

      Making Apps Accessible

      Accessibility properties

      @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService       -
      ← AnimationsImproving User Experience →
      Edit

      Alert

      Launches an alert dialog with the specified title and message.

      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

      -

      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

      +

      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

      iOS

      On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

      Android

      @@ -82,7 +82,7 @@

    Note that by default alerts on Android can be dismissed by clicking outside of their alert box. To prevent this behavior, you can provide an optional options parameter { cancelable: false } to the Alert method.

    Example usage:

    -
    // Works on both iOS and Android
+
    // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.41/alert/index.html b/docs/0.41/alert/index.html
index 0293c28c87a..ca162457a2c 100644
--- a/docs/0.41/alert/index.html
+++ b/docs/0.41/alert/index.html
@@ -70,7 +70,7 @@
             });
    Edit

    Alert

    Launches an alert dialog with the specified title and message.

    Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

    -

    This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

    +

    This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

    iOS

    On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

    Android

    @@ -82,7 +82,7 @@

    Note that by default alerts on Android can be dismissed by clicking outside of their alert box. To prevent this behavior, you can provide an optional options parameter { cancelable: false } to the Alert method.

    Example usage:

    -
    // Works on both iOS and Android
+
    // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.41/clipboard.html b/docs/0.41/clipboard.html
index f76e43f2083..a8ee0239720 100644
--- a/docs/0.41/clipboard.html
+++ b/docs/0.41/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

    +
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

    Methods

    • getString
      • diff --git a/docs/0.41/clipboard/index.html b/docs/0.41/clipboard/index.html index f76e43f2083..a8ee0239720 100644 --- a/docs/0.41/clipboard/index.html +++ b/docs/0.41/clipboard/index.html @@ -1,4 +1,4 @@ -Clipboard · React Native
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

    +
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

    Methods

    • getString
      • diff --git a/docs/0.41/components-and-apis.html b/docs/0.41/components-and-apis.html index 1c4e8354ea9..c199098dc20 100644 --- a/docs/0.41/components-and-apis.html +++ b/docs/0.41/components-and-apis.html @@ -130,7 +130,7 @@

      Picker

      -

      Renders the native picker component on iOS and Android.

      +

      Renders the native picker component on Android and iOS.
      @@ -290,7 +290,7 @@

      Clipboard

      -

      Provides an interface for setting and getting content from the clipboard on both iOS and Android.

      +

      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
      diff --git a/docs/0.41/components-and-apis/index.html b/docs/0.41/components-and-apis/index.html index 1c4e8354ea9..c199098dc20 100644 --- a/docs/0.41/components-and-apis/index.html +++ b/docs/0.41/components-and-apis/index.html @@ -130,7 +130,7 @@

      Picker

      -

      Renders the native picker component on iOS and Android.

      +

      Renders the native picker component on Android and iOS.
      @@ -290,7 +290,7 @@

      Clipboard

      -

      Provides an interface for setting and getting content from the clipboard on both iOS and Android.

      +

      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
      diff --git a/docs/0.41/getting-started.html b/docs/0.41/getting-started.html index 469ce125db2..aecf26fe5c9 100644 --- a/docs/0.41/getting-started.html +++ b/docs/0.41/getting-started.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

      -

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

      +

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

      Development OS: diff --git a/docs/0.41/getting-started/index.html b/docs/0.41/getting-started/index.html index 469ce125db2..aecf26fe5c9 100644 --- a/docs/0.41/getting-started/index.html +++ b/docs/0.41/getting-started/index.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

      -

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

      +

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

      Development OS: diff --git a/docs/0.41/images.html b/docs/0.41/images.html index 904e991fb5f..6e4ad79dfd9 100644 --- a/docs/0.41/images.html +++ b/docs/0.41/images.html @@ -69,7 +69,7 @@ } });
      Edit

      Images

      Static Image Resources

      -

      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      +

      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      <Image source={require('./my-icon.png')} />

      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

      @@ -88,7 +88,7 @@

      On Windows, you might need to restart the packager if you add new images to your project.

      Here are some benefits that you get:

        -
      1. Same system on iOS and Android.
        2. +
      2. Same system on Android and iOS.
      3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. No global namespace, i.e. you don't have to worry about name collisions.
      5. Only the images that are actually used will be packaged into your app.
        6. diff --git a/docs/0.41/images/index.html b/docs/0.41/images/index.html index 904e991fb5f..6e4ad79dfd9 100644 --- a/docs/0.41/images/index.html +++ b/docs/0.41/images/index.html @@ -69,7 +69,7 @@ } });
      Edit

      Images

      Static Image Resources

      -

      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      +

      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      <Image source={require('./my-icon.png')} />

      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

      @@ -88,7 +88,7 @@

      On Windows, you might need to restart the packager if you add new images to your project.

      Here are some benefits that you get:

        -
      1. Same system on iOS and Android.
        2. +
      2. Same system on Android and iOS.
      3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. No global namespace, i.e. you don't have to worry about name collisions.
      5. Only the images that are actually used will be packaged into your app.
        6. diff --git a/docs/0.41/navigation.html b/docs/0.41/navigation.html index 79c1ad7dd00..c9b5823a9c4 100644 --- a/docs/0.41/navigation.html +++ b/docs/0.41/navigation.html @@ -69,8 +69,8 @@ } });
      Edit

      Navigating Between Screens

      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

      -

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

      -

      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      +

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

      +

      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      React Navigation

      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

      The first step is to install in your project:

      diff --git a/docs/0.41/navigation/index.html b/docs/0.41/navigation/index.html index 79c1ad7dd00..c9b5823a9c4 100644 --- a/docs/0.41/navigation/index.html +++ b/docs/0.41/navigation/index.html @@ -69,8 +69,8 @@ } });
      Edit

      Navigating Between Screens

      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

      -

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

      -

      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      +

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

      +

      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      React Navigation

      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

      The first step is to install in your project:

      diff --git a/docs/0.41/navigator.html b/docs/0.41/navigator.html index 97a356221a7..7a05b8f785f 100644 --- a/docs/0.41/navigator.html +++ b/docs/0.41/navigator.html @@ -1,4 +1,4 @@ -Navigator · React Native
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      +
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.

      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.41/navigator/index.html b/docs/0.41/navigator/index.html
index 97a356221a7..7a05b8f785f 100644
--- a/docs/0.41/navigator/index.html
+++ b/docs/0.41/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      +
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.

      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.41/navigatorios.html b/docs/0.41/navigatorios.html
index e1b906e0efa..c529a22977a 100644
--- a/docs/0.41/navigatorios.html
+++ b/docs/0.41/navigatorios.html
@@ -69,7 +69,7 @@
               }
             });
      Edit

      NavigatorIOS

      NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.

      -

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.

      +

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.

      To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.

      import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.41/navigatorios/index.html b/docs/0.41/navigatorios/index.html
index e1b906e0efa..c529a22977a 100644
--- a/docs/0.41/navigatorios/index.html
+++ b/docs/0.41/navigatorios/index.html
@@ -69,7 +69,7 @@
               }
             });
      Edit

      NavigatorIOS

      NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.

      -

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.

      +

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.

      To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.

      import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.41/picker.html b/docs/0.41/picker.html
index 370deef4695..c46409ed089 100644
--- a/docs/0.41/picker.html
+++ b/docs/0.41/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
      Edit

      Picker

      Renders the native picker component on iOS and Android. Example:

      +
      Edit

      Picker

      Renders the native picker component on Android and iOS. Example:

      <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.41/picker/index.html b/docs/0.41/picker/index.html
index 370deef4695..c46409ed089 100644
--- a/docs/0.41/picker/index.html
+++ b/docs/0.41/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
      Edit

      Picker

      Renders the native picker component on iOS and Android. Example:

      +
      Edit

      Picker

      Renders the native picker component on Android and iOS. Example:

      <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.41/platform-specific-code.html b/docs/0.41/platform-specific-code.html
index 82af0626468..66f0878a485 100644
--- a/docs/0.41/platform-specific-code.html
+++ b/docs/0.41/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

      +
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

      React Native provides two ways to organize your code and separate it by platform:

      • Using the Platform module.
        • diff --git a/docs/0.41/platform-specific-code/index.html b/docs/0.41/platform-specific-code/index.html index 82af0626468..66f0878a485 100644 --- a/docs/0.41/platform-specific-code/index.html +++ b/docs/0.41/platform-specific-code/index.html @@ -1,4 +1,4 @@ -Platform Specific Code · React Native
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

      +
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

      React Native provides two ways to organize your code and separate it by platform:

      • Using the Platform module.
        • diff --git a/docs/0.42/accessibility.html b/docs/0.42/accessibility.html index 5918571cc95..f3e6166bb51 100644 --- a/docs/0.42/accessibility.html +++ b/docs/0.42/accessibility.html @@ -1,4 +1,4 @@ -Accessibility · React Native
      Edit

      Accessibility

      Native App Accessibility (iOS and Android)

      -

      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      +
      Edit

      Accessibility

      Native App Accessibility (Android and iOS)

      +

      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

      Making Apps Accessible

      Accessibility properties

      @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService       -
      ← AnimationsImproving User Experience →
      Edit

      Accessibility

      Native App Accessibility (iOS and Android)

      -

      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      +
      Edit

      Accessibility

      Native App Accessibility (Android and iOS)

      +

      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

      Making Apps Accessible

      Accessibility properties

      @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService       -
      ← AnimationsImproving User Experience →
      Edit

      Alert

      Launches an alert dialog with the specified title and message.

      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

      -

      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

      +

      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

      iOS

      On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

      Android

      @@ -82,7 +82,7 @@

    Note that by default alerts on Android can be dismissed by clicking outside of their alert box. To prevent this behavior, you can provide an optional options parameter { cancelable: false } to the Alert method.

    Example usage:

    -
    // Works on both iOS and Android
+
    // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.42/alert/index.html b/docs/0.42/alert/index.html
index d92d95ae200..e54fcdf5030 100644
--- a/docs/0.42/alert/index.html
+++ b/docs/0.42/alert/index.html
@@ -70,7 +70,7 @@
             });
    Edit

    Alert

    Launches an alert dialog with the specified title and message.

    Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

    -

    This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

    +

    This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

    iOS

    On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

    Android

    @@ -82,7 +82,7 @@

    Note that by default alerts on Android can be dismissed by clicking outside of their alert box. To prevent this behavior, you can provide an optional options parameter { cancelable: false } to the Alert method.

    Example usage:

    -
    // Works on both iOS and Android
+
    // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.42/clipboard.html b/docs/0.42/clipboard.html
index cf0e03bb65d..1307324c6b8 100644
--- a/docs/0.42/clipboard.html
+++ b/docs/0.42/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

    +
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

    Methods

    • getString
      • diff --git a/docs/0.42/clipboard/index.html b/docs/0.42/clipboard/index.html index cf0e03bb65d..1307324c6b8 100644 --- a/docs/0.42/clipboard/index.html +++ b/docs/0.42/clipboard/index.html @@ -1,4 +1,4 @@ -Clipboard · React Native
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

    +
    Edit

    Clipboard

    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

    Methods

    • getString
      • diff --git a/docs/0.42/components-and-apis.html b/docs/0.42/components-and-apis.html index d6311444e30..0e03039005e 100644 --- a/docs/0.42/components-and-apis.html +++ b/docs/0.42/components-and-apis.html @@ -130,7 +130,7 @@

      Picker

      -

      Renders the native picker component on iOS and Android.

      +

      Renders the native picker component on Android and iOS.
      @@ -290,7 +290,7 @@

      Clipboard

      -

      Provides an interface for setting and getting content from the clipboard on both iOS and Android.

      +

      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
      diff --git a/docs/0.42/components-and-apis/index.html b/docs/0.42/components-and-apis/index.html index d6311444e30..0e03039005e 100644 --- a/docs/0.42/components-and-apis/index.html +++ b/docs/0.42/components-and-apis/index.html @@ -130,7 +130,7 @@

      Picker

      -

      Renders the native picker component on iOS and Android.

      +

      Renders the native picker component on Android and iOS.
      @@ -290,7 +290,7 @@

      Clipboard

      -

      Provides an interface for setting and getting content from the clipboard on both iOS and Android.

      +

      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
      diff --git a/docs/0.42/getting-started.html b/docs/0.42/getting-started.html index 6e28f1c72ac..c6f9198db5e 100644 --- a/docs/0.42/getting-started.html +++ b/docs/0.42/getting-started.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

      -

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

      +

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

      Development OS: diff --git a/docs/0.42/getting-started/index.html b/docs/0.42/getting-started/index.html index 6e28f1c72ac..c6f9198db5e 100644 --- a/docs/0.42/getting-started/index.html +++ b/docs/0.42/getting-started/index.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

      -

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

      +

      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

      Development OS: diff --git a/docs/0.42/images.html b/docs/0.42/images.html index 7e2fe843be5..31e48acbfc7 100644 --- a/docs/0.42/images.html +++ b/docs/0.42/images.html @@ -69,7 +69,7 @@ } });
      Edit

      Images

      Static Image Resources

      -

      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      +

      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      <Image source={require('./my-icon.png')} />

      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

      @@ -88,7 +88,7 @@

      On Windows, you might need to restart the packager if you add new images to your project.

      Here are some benefits that you get:

        -
      1. Same system on iOS and Android.
        2. +
      2. Same system on Android and iOS.
      3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. No global namespace, i.e. you don't have to worry about name collisions.
      5. Only the images that are actually used will be packaged into your app.
        6. diff --git a/docs/0.42/images/index.html b/docs/0.42/images/index.html index 7e2fe843be5..31e48acbfc7 100644 --- a/docs/0.42/images/index.html +++ b/docs/0.42/images/index.html @@ -69,7 +69,7 @@ } });
      Edit

      Images

      Static Image Resources

      -

      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      +

      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

      <Image source={require('./my-icon.png')} />

      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

      @@ -88,7 +88,7 @@

      On Windows, you might need to restart the packager if you add new images to your project.

      Here are some benefits that you get:

        -
      1. Same system on iOS and Android.
        2. +
      2. Same system on Android and iOS.
      3. Images live in the same folder as your JavaScript code. Components are self-contained.
      4. No global namespace, i.e. you don't have to worry about name collisions.
      5. Only the images that are actually used will be packaged into your app.
        6. diff --git a/docs/0.42/navigation.html b/docs/0.42/navigation.html index 72d3f91f1dc..4947e4ccbac 100644 --- a/docs/0.42/navigation.html +++ b/docs/0.42/navigation.html @@ -69,8 +69,8 @@ } });
      Edit

      Navigating Between Screens

      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

      -

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

      -

      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      +

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

      +

      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      React Navigation

      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

      The first step is to install in your project:

      diff --git a/docs/0.42/navigation/index.html b/docs/0.42/navigation/index.html index 72d3f91f1dc..4947e4ccbac 100644 --- a/docs/0.42/navigation/index.html +++ b/docs/0.42/navigation/index.html @@ -69,8 +69,8 @@ } });
      Edit

      Navigating Between Screens

      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

      -

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

      -

      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      +

      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

      +

      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

      React Navigation

      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

      The first step is to install in your project:

      diff --git a/docs/0.42/navigator.html b/docs/0.42/navigator.html index ba0e29b5c8e..bdd37e2a5e9 100644 --- a/docs/0.42/navigator.html +++ b/docs/0.42/navigator.html @@ -1,4 +1,4 @@ -Navigator · React Native
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      +
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.

      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.42/navigator/index.html b/docs/0.42/navigator/index.html
index ba0e29b5c8e..bdd37e2a5e9 100644
--- a/docs/0.42/navigator/index.html
+++ b/docs/0.42/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      +
      Edit

      Navigator

      Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

      To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.

      import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.42/navigatorios.html b/docs/0.42/navigatorios.html
index 9460d75fbe8..8d1da9c5265 100644
--- a/docs/0.42/navigatorios.html
+++ b/docs/0.42/navigatorios.html
@@ -69,7 +69,7 @@
               }
             });
      Edit

      NavigatorIOS

      NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.

      -

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.

      +

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.

      To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.

      import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.42/navigatorios/index.html b/docs/0.42/navigatorios/index.html
index 9460d75fbe8..8d1da9c5265 100644
--- a/docs/0.42/navigatorios/index.html
+++ b/docs/0.42/navigatorios/index.html
@@ -69,7 +69,7 @@
               }
             });
      Edit

      NavigatorIOS

      NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.

      -

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.

      +

      As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.

      To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.

      import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.42/picker.html b/docs/0.42/picker.html
index 4ff7a4f14d1..2cd8f4db914 100644
--- a/docs/0.42/picker.html
+++ b/docs/0.42/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
      Edit

      Picker

      Renders the native picker component on iOS and Android. Example:

      +
      Edit

      Picker

      Renders the native picker component on Android and iOS. Example:

      <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.42/picker/index.html b/docs/0.42/picker/index.html
index 4ff7a4f14d1..2cd8f4db914 100644
--- a/docs/0.42/picker/index.html
+++ b/docs/0.42/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
      Edit

      Picker

      Renders the native picker component on iOS and Android. Example:

      +
      Edit

      Picker

      Renders the native picker component on Android and iOS. Example:

      <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.42/platform-specific-code.html b/docs/0.42/platform-specific-code.html
index a0967ea01ed..eae320311b9 100644
--- a/docs/0.42/platform-specific-code.html
+++ b/docs/0.42/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

      +
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

      React Native provides two ways to organize your code and separate it by platform:

      • Using the Platform module.
        • diff --git a/docs/0.42/platform-specific-code/index.html b/docs/0.42/platform-specific-code/index.html index a0967ea01ed..eae320311b9 100644 --- a/docs/0.42/platform-specific-code/index.html +++ b/docs/0.42/platform-specific-code/index.html @@ -1,4 +1,4 @@ -Platform Specific Code · React Native
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

      +
      Edit

      Platform Specific Code

      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

      React Native provides two ways to organize your code and separate it by platform:

      • Using the Platform module.
        • diff --git a/docs/0.43/accessibility.html b/docs/0.43/accessibility.html index be0e8860f82..acba9055c72 100644 --- a/docs/0.43/accessibility.html +++ b/docs/0.43/accessibility.html @@ -1,4 +1,4 @@ -Accessibility · React Native
      Edit

      Accessibility

      Native App Accessibility (iOS and Android)

      -

      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      +
      Edit

      Accessibility

      Native App Accessibility (Android and iOS)

      +

      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

      Making Apps Accessible

      Accessibility properties

      @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService       -
      ← AnimationsImproving User Experience →
      Edit

      Accessibility

      Native App Accessibility (iOS and Android)

      -

      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      +
      Edit

      Accessibility

      Native App Accessibility (Android and iOS)

      +

      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

      Making Apps Accessible

      Accessibility properties

      @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService       -
      ← AnimationsImproving User Experience →
      Edit

      Alert

      Launches an alert dialog with the specified title and message.

      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

      -

      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

      +

      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

      iOS

      On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

      Android

      @@ -83,7 +83,7 @@

      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

      Example usage:

      -
      // Works on both iOS and Android
+
      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.43/alert/index.html b/docs/0.43/alert/index.html
index ed36ad575c8..99391d25707 100644
--- a/docs/0.43/alert/index.html
+++ b/docs/0.43/alert/index.html
@@ -70,7 +70,7 @@
             });
      Edit

      Alert

      Launches an alert dialog with the specified title and message.

      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

      -

      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

      +

      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

      iOS

      On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

      Android

      @@ -83,7 +83,7 @@

      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

      Example usage:

      -
      // Works on both iOS and Android
+
      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.43/clipboard.html b/docs/0.43/clipboard.html
index 96cff0e788b..be843e6a047 100644
--- a/docs/0.43/clipboard.html
+++ b/docs/0.43/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
      Edit

      Clipboard

      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

      +
      Edit

      Clipboard

      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

      Methods

      • getString
        • diff --git a/docs/0.43/clipboard/index.html b/docs/0.43/clipboard/index.html index 96cff0e788b..be843e6a047 100644 --- a/docs/0.43/clipboard/index.html +++ b/docs/0.43/clipboard/index.html @@ -1,4 +1,4 @@ -Clipboard · React Native
      Edit

      Clipboard

      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

      +
      Edit

      Clipboard

      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

      Methods

      • getString
        • diff --git a/docs/0.43/components-and-apis.html b/docs/0.43/components-and-apis.html index faa3bc876d1..088fa2973c5 100644 --- a/docs/0.43/components-and-apis.html +++ b/docs/0.43/components-and-apis.html @@ -130,7 +130,7 @@

        Picker

        -

        Renders the native picker component on iOS and Android.

        +

        Renders the native picker component on Android and iOS.
        @@ -290,7 +290,7 @@

        Clipboard

        -

        Provides an interface for setting and getting content from the clipboard on both iOS and Android.

        +

        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
        diff --git a/docs/0.43/components-and-apis/index.html b/docs/0.43/components-and-apis/index.html index faa3bc876d1..088fa2973c5 100644 --- a/docs/0.43/components-and-apis/index.html +++ b/docs/0.43/components-and-apis/index.html @@ -130,7 +130,7 @@

        Picker

        -

        Renders the native picker component on iOS and Android.

        +

        Renders the native picker component on Android and iOS.
        @@ -290,7 +290,7 @@

        Clipboard

        -

        Provides an interface for setting and getting content from the clipboard on both iOS and Android.

        +

        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
        diff --git a/docs/0.43/getting-started.html b/docs/0.43/getting-started.html index 92634c97683..546d84cee4b 100644 --- a/docs/0.43/getting-started.html +++ b/docs/0.43/getting-started.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

        -

        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

        +

        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

        Development OS: diff --git a/docs/0.43/getting-started/index.html b/docs/0.43/getting-started/index.html index 92634c97683..546d84cee4b 100644 --- a/docs/0.43/getting-started/index.html +++ b/docs/0.43/getting-started/index.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

        -

        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

        +

        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

        Development OS: diff --git a/docs/0.43/images.html b/docs/0.43/images.html index e426e4b12fe..7f4ddaa9ebf 100644 --- a/docs/0.43/images.html +++ b/docs/0.43/images.html @@ -69,7 +69,7 @@ } });
        Edit

        Images

        Static Image Resources

        -

        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

        +

        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

        <Image source={require('./my-icon.png')} />

        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

        @@ -88,7 +88,7 @@

        On Windows, you might need to restart the packager if you add new images to your project.

        Here are some benefits that you get:

          -
        1. Same system on iOS and Android.
          2. +
        2. Same system on Android and iOS.
        3. Images live in the same folder as your JavaScript code. Components are self-contained.
        4. No global namespace, i.e. you don't have to worry about name collisions.
        5. Only the images that are actually used will be packaged into your app.
          6. diff --git a/docs/0.43/images/index.html b/docs/0.43/images/index.html index e426e4b12fe..7f4ddaa9ebf 100644 --- a/docs/0.43/images/index.html +++ b/docs/0.43/images/index.html @@ -69,7 +69,7 @@ } });
        Edit

        Images

        Static Image Resources

        -

        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

        +

        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

        <Image source={require('./my-icon.png')} />

        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

        @@ -88,7 +88,7 @@

        On Windows, you might need to restart the packager if you add new images to your project.

        Here are some benefits that you get:

          -
        1. Same system on iOS and Android.
          2. +
        2. Same system on Android and iOS.
        3. Images live in the same folder as your JavaScript code. Components are self-contained.
        4. No global namespace, i.e. you don't have to worry about name collisions.
        5. Only the images that are actually used will be packaged into your app.
          6. diff --git a/docs/0.43/navigation.html b/docs/0.43/navigation.html index e89b2106a94..304fc710c94 100644 --- a/docs/0.43/navigation.html +++ b/docs/0.43/navigation.html @@ -69,8 +69,8 @@ } });
        Edit

        Navigating Between Screens

        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

        -

        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

        -

        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

        +

        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

        +

        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

        React Navigation

        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

        The first step is to install in your project:

        diff --git a/docs/0.43/navigation/index.html b/docs/0.43/navigation/index.html index e89b2106a94..304fc710c94 100644 --- a/docs/0.43/navigation/index.html +++ b/docs/0.43/navigation/index.html @@ -69,8 +69,8 @@ } });
        Edit

        Navigating Between Screens

        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

        -

        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

        -

        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

        +

        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

        +

        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

        React Navigation

        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

        The first step is to install in your project:

        diff --git a/docs/0.43/navigator.html b/docs/0.43/navigator.html index 713e4fab345..3c0d846f059 100644 --- a/docs/0.43/navigator.html +++ b/docs/0.43/navigator.html @@ -1,4 +1,4 @@ -Navigator · React Native
        Edit

        Navigator

        Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

        +
        Edit

        Navigator

        Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

        To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.

        import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.43/navigator/index.html b/docs/0.43/navigator/index.html
index 713e4fab345..3c0d846f059 100644
--- a/docs/0.43/navigator/index.html
+++ b/docs/0.43/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
        Edit

        Navigator

        Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

        +
        Edit

        Navigator

        Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.

        To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.

        import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.43/navigatorios.html b/docs/0.43/navigatorios.html
index 0c3e566b481..94652805255 100644
--- a/docs/0.43/navigatorios.html
+++ b/docs/0.43/navigatorios.html
@@ -69,7 +69,7 @@
               }
             });
        Edit

        NavigatorIOS

        NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.

        -

        As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.

        +

        As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.

        To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.

        import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.43/navigatorios/index.html b/docs/0.43/navigatorios/index.html
index 0c3e566b481..94652805255 100644
--- a/docs/0.43/navigatorios/index.html
+++ b/docs/0.43/navigatorios/index.html
@@ -69,7 +69,7 @@
               }
             });
        Edit

        NavigatorIOS

        NavigatorIOS is a wrapper around UINavigationController, enabling you to implement a navigation stack. It works exactly the same as it would on a native app using UINavigationController, providing the same animations and behavior from UIKIt.

        -

        As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both iOS and Android.

        +

        As the name implies, it is only available on iOS. Take a look at Navigator for a similar solution for your cross-platform needs, or check out react-native-navigation, a component that aims to provide native navigation on both Android and iOS.

        To set up the navigator, provide the initialRoute prop with a route object. A route object is used to describe each scene that your app navigates to. initialRoute represents the first route in your navigator.

        import React, { Component, PropTypes } from 'react';
 import { NavigatorIOS, Text } from 'react-native';
diff --git a/docs/0.43/picker.html b/docs/0.43/picker.html
index af160892f34..5446d6c4316 100644
--- a/docs/0.43/picker.html
+++ b/docs/0.43/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
        Edit

        Picker

        Renders the native picker component on iOS and Android. Example:

        +
        Edit

        Picker

        Renders the native picker component on Android and iOS. Example:

        <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.43/picker/index.html b/docs/0.43/picker/index.html
index af160892f34..5446d6c4316 100644
--- a/docs/0.43/picker/index.html
+++ b/docs/0.43/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
        Edit

        Picker

        Renders the native picker component on iOS and Android. Example:

        +
        Edit

        Picker

        Renders the native picker component on Android and iOS. Example:

        <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.43/platform-specific-code.html b/docs/0.43/platform-specific-code.html
index 2bd72142251..2f602381ab7 100644
--- a/docs/0.43/platform-specific-code.html
+++ b/docs/0.43/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
        Edit

        Platform Specific Code

        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

        +
        Edit

        Platform Specific Code

        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

        React Native provides two ways to organize your code and separate it by platform:

        • Using the Platform module.
          • diff --git a/docs/0.43/platform-specific-code/index.html b/docs/0.43/platform-specific-code/index.html index 2bd72142251..2f602381ab7 100644 --- a/docs/0.43/platform-specific-code/index.html +++ b/docs/0.43/platform-specific-code/index.html @@ -1,4 +1,4 @@ -Platform Specific Code · React Native
        Edit

        Platform Specific Code

        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

        +
        Edit

        Platform Specific Code

        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

        React Native provides two ways to organize your code and separate it by platform:

        • Using the Platform module.
          • diff --git a/docs/0.44/accessibility.html b/docs/0.44/accessibility.html index c5ef0ce7793..dc20a3b8db0 100644 --- a/docs/0.44/accessibility.html +++ b/docs/0.44/accessibility.html @@ -1,4 +1,4 @@ -Accessibility · React Native
        Edit

        Accessibility

        Native App Accessibility (iOS and Android)

        -

        Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

        +
        Edit

        Accessibility

        Native App Accessibility (Android and iOS)

        +

        Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

        In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

        Making Apps Accessible

        Accessibility properties

        @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService         -
        ← AnimationsImproving User Experience →
        Edit

        Accessibility

        Native App Accessibility (iOS and Android)

        -

        Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

        +
        Edit

        Accessibility

        Native App Accessibility (Android and iOS)

        +

        Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

        In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

        Making Apps Accessible

        Accessibility properties

        @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService         -
        ← AnimationsImproving User Experience →
        Edit

        Alert

        Launches an alert dialog with the specified title and message.

        Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

        -

        This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

        +

        This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

        iOS

        On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

        Android

        @@ -83,7 +83,7 @@

        By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

        Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

        Example usage:

        -
        // Works on both iOS and Android
+
        // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.44/alert/index.html b/docs/0.44/alert/index.html
index 64e81a96979..6ac8b5665ed 100644
--- a/docs/0.44/alert/index.html
+++ b/docs/0.44/alert/index.html
@@ -70,7 +70,7 @@
             });
        Edit

        Alert

        Launches an alert dialog with the specified title and message.

        Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

        -

        This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

        +

        This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

        iOS

        On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

        Android

        @@ -83,7 +83,7 @@

        By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

        Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

        Example usage:

        -
        // Works on both iOS and Android
+
        // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.44/clipboard.html b/docs/0.44/clipboard.html
index 981cf5f9b37..39c3c6e197e 100644
--- a/docs/0.44/clipboard.html
+++ b/docs/0.44/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
        Edit

        Clipboard

        Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

        +
        Edit

        Clipboard

        Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

        Methods

        • getString
          • diff --git a/docs/0.44/clipboard/index.html b/docs/0.44/clipboard/index.html index 981cf5f9b37..39c3c6e197e 100644 --- a/docs/0.44/clipboard/index.html +++ b/docs/0.44/clipboard/index.html @@ -1,4 +1,4 @@ -Clipboard · React Native
        Edit

        Clipboard

        Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

        +
        Edit

        Clipboard

        Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

        Methods

        • getString
          • diff --git a/docs/0.44/components-and-apis.html b/docs/0.44/components-and-apis.html index 411b93b474e..ee5a9832eca 100644 --- a/docs/0.44/components-and-apis.html +++ b/docs/0.44/components-and-apis.html @@ -130,7 +130,7 @@

          Picker

          -

          Renders the native picker component on iOS and Android.

          +

          Renders the native picker component on Android and iOS.
          @@ -290,7 +290,7 @@

          Clipboard

          -

          Provides an interface for setting and getting content from the clipboard on both iOS and Android.

          +

          Provides an interface for setting and getting content from the clipboard on both Android and iOS.
          diff --git a/docs/0.44/components-and-apis/index.html b/docs/0.44/components-and-apis/index.html index 411b93b474e..ee5a9832eca 100644 --- a/docs/0.44/components-and-apis/index.html +++ b/docs/0.44/components-and-apis/index.html @@ -130,7 +130,7 @@

          Picker

          -

          Renders the native picker component on iOS and Android.

          +

          Renders the native picker component on Android and iOS.
          @@ -290,7 +290,7 @@

          Clipboard

          -

          Provides an interface for setting and getting content from the clipboard on both iOS and Android.

          +

          Provides an interface for setting and getting content from the clipboard on both Android and iOS.
          diff --git a/docs/0.44/getting-started.html b/docs/0.44/getting-started.html index a0d8e6ef400..32ec6474d0a 100644 --- a/docs/0.44/getting-started.html +++ b/docs/0.44/getting-started.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

          If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

          Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

          -

          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

          +

          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

          Development OS: diff --git a/docs/0.44/getting-started/index.html b/docs/0.44/getting-started/index.html index a0d8e6ef400..32ec6474d0a 100644 --- a/docs/0.44/getting-started/index.html +++ b/docs/0.44/getting-started/index.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

          If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

          Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

          -

          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

          +

          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

          Development OS: diff --git a/docs/0.44/images.html b/docs/0.44/images.html index da786a81795..c7538229a7e 100644 --- a/docs/0.44/images.html +++ b/docs/0.44/images.html @@ -69,7 +69,7 @@ } });
          Edit

          Images

          Static Image Resources

          -

          React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

          +

          React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

          <Image source={require('./my-icon.png')} />

          The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

          @@ -88,7 +88,7 @@

          On Windows, you might need to restart the packager if you add new images to your project.

          Here are some benefits that you get:

            -
          1. Same system on iOS and Android.
            2. +
          2. Same system on Android and iOS.
          3. Images live in the same folder as your JavaScript code. Components are self-contained.
          4. No global namespace, i.e. you don't have to worry about name collisions.
          5. Only the images that are actually used will be packaged into your app.
            6. diff --git a/docs/0.44/images/index.html b/docs/0.44/images/index.html index da786a81795..c7538229a7e 100644 --- a/docs/0.44/images/index.html +++ b/docs/0.44/images/index.html @@ -69,7 +69,7 @@ } });
          Edit

          Images

          Static Image Resources

          -

          React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

          +

          React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

          <Image source={require('./my-icon.png')} />

          The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

          @@ -88,7 +88,7 @@

          On Windows, you might need to restart the packager if you add new images to your project.

          Here are some benefits that you get:

            -
          1. Same system on iOS and Android.
            2. +
          2. Same system on Android and iOS.
          3. Images live in the same folder as your JavaScript code. Components are self-contained.
          4. No global namespace, i.e. you don't have to worry about name collisions.
          5. Only the images that are actually used will be packaged into your app.
            6. diff --git a/docs/0.44/navigation.html b/docs/0.44/navigation.html index bc137fd6629..031cf6a4d71 100644 --- a/docs/0.44/navigation.html +++ b/docs/0.44/navigation.html @@ -69,8 +69,8 @@ } });
          Edit

          Navigating Between Screens

          Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

          -

          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

          -

          If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

          +

          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

          +

          If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

          React Navigation

          The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

          The first step is to install in your project:

          diff --git a/docs/0.44/navigation/index.html b/docs/0.44/navigation/index.html index bc137fd6629..031cf6a4d71 100644 --- a/docs/0.44/navigation/index.html +++ b/docs/0.44/navigation/index.html @@ -69,8 +69,8 @@ } });
          Edit

          Navigating Between Screens

          Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

          -

          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

          -

          If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

          +

          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

          +

          If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

          React Navigation

          The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

          The first step is to install in your project:

          diff --git a/docs/0.44/picker.html b/docs/0.44/picker.html index a606449dfbc..3432b096d46 100644 --- a/docs/0.44/picker.html +++ b/docs/0.44/picker.html @@ -1,4 +1,4 @@ -Picker · React Native
          Edit

          Picker

          Renders the native picker component on iOS and Android. Example:

          +
          Edit

          Picker

          Renders the native picker component on Android and iOS. Example:

          <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.44/picker/index.html b/docs/0.44/picker/index.html
index a606449dfbc..3432b096d46 100644
--- a/docs/0.44/picker/index.html
+++ b/docs/0.44/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
          Edit

          Picker

          Renders the native picker component on iOS and Android. Example:

          +
          Edit

          Picker

          Renders the native picker component on Android and iOS. Example:

          <Picker
   selectedValue={this.state.language}
   onValueChange={(lang) => this.setState({language: lang})}>
diff --git a/docs/0.44/platform-specific-code.html b/docs/0.44/platform-specific-code.html
index 92d1344f210..b8234da408f 100644
--- a/docs/0.44/platform-specific-code.html
+++ b/docs/0.44/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
          Edit

          Platform Specific Code

          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

          +
          Edit

          Platform Specific Code

          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

          React Native provides two ways to organize your code and separate it by platform:

          • Using the Platform module.
            • diff --git a/docs/0.44/platform-specific-code/index.html b/docs/0.44/platform-specific-code/index.html index 92d1344f210..b8234da408f 100644 --- a/docs/0.44/platform-specific-code/index.html +++ b/docs/0.44/platform-specific-code/index.html @@ -1,4 +1,4 @@ -Platform Specific Code · React Native
          Edit

          Platform Specific Code

          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

          +
          Edit

          Platform Specific Code

          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

          React Native provides two ways to organize your code and separate it by platform:

          • Using the Platform module.
            • diff --git a/docs/0.45/accessibility.html b/docs/0.45/accessibility.html index d6c670cb304..c0f6418f8b5 100644 --- a/docs/0.45/accessibility.html +++ b/docs/0.45/accessibility.html @@ -1,4 +1,4 @@ -Accessibility · React Native
          Edit

          Accessibility

          Native App Accessibility (iOS and Android)

          -

          Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

          +
          Edit

          Accessibility

          Native App Accessibility (Android and iOS)

          +

          Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

          In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

          Making Apps Accessible

          Accessibility properties

          @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService           -
          ← AnimationsImproving User Experience →
          Edit

          Accessibility

          Native App Accessibility (iOS and Android)

          -

          Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

          +
          Edit

          Accessibility

          Native App Accessibility (Android and iOS)

          +

          Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

          In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

          Making Apps Accessible

          Accessibility properties

          @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService           -
          ← AnimationsImproving User Experience →
          Edit

          Alert

          Launches an alert dialog with the specified title and message.

          Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

          -

          This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

          +

          This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

          iOS

          On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

          Android

          @@ -83,7 +83,7 @@

          By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

          Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

          Example usage:

          -
          // Works on both iOS and Android
+
          // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.45/alert/index.html b/docs/0.45/alert/index.html
index 9eac161a887..a88932d28ba 100644
--- a/docs/0.45/alert/index.html
+++ b/docs/0.45/alert/index.html
@@ -70,7 +70,7 @@
             });
          Edit

          Alert

          Launches an alert dialog with the specified title and message.

          Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

          -

          This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

          +

          This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

          iOS

          On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

          Android

          @@ -83,7 +83,7 @@

          By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

          Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

          Example usage:

          -
          // Works on both iOS and Android
+
          // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.45/clipboard.html b/docs/0.45/clipboard.html
index 9df6ffa4146..c2c70139c41 100644
--- a/docs/0.45/clipboard.html
+++ b/docs/0.45/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
          Edit

          Clipboard

          Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

          +
          Edit

          Clipboard

          Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

          Methods

          • getString
            • diff --git a/docs/0.45/clipboard/index.html b/docs/0.45/clipboard/index.html index 9df6ffa4146..c2c70139c41 100644 --- a/docs/0.45/clipboard/index.html +++ b/docs/0.45/clipboard/index.html @@ -1,4 +1,4 @@ -Clipboard · React Native
          Edit

          Clipboard

          Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

          +
          Edit

          Clipboard

          Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

          Methods

          • getString
            • diff --git a/docs/0.45/components-and-apis.html b/docs/0.45/components-and-apis.html index 0f170a13717..f58f9328d1f 100644 --- a/docs/0.45/components-and-apis.html +++ b/docs/0.45/components-and-apis.html @@ -130,7 +130,7 @@

            Picker

            -

            Renders the native picker component on iOS and Android.

            +

            Renders the native picker component on Android and iOS.
            @@ -290,7 +290,7 @@

            Clipboard

            -

            Provides an interface for setting and getting content from the clipboard on both iOS and Android.

            +

            Provides an interface for setting and getting content from the clipboard on both Android and iOS.
            diff --git a/docs/0.45/components-and-apis/index.html b/docs/0.45/components-and-apis/index.html index 0f170a13717..f58f9328d1f 100644 --- a/docs/0.45/components-and-apis/index.html +++ b/docs/0.45/components-and-apis/index.html @@ -130,7 +130,7 @@

            Picker

            -

            Renders the native picker component on iOS and Android.

            +

            Renders the native picker component on Android and iOS.
            @@ -290,7 +290,7 @@

            Clipboard

            -

            Provides an interface for setting and getting content from the clipboard on both iOS and Android.

            +

            Provides an interface for setting and getting content from the clipboard on both Android and iOS.
            diff --git a/docs/0.45/getting-started.html b/docs/0.45/getting-started.html index 4948d7529a3..54b5250eb7b 100644 --- a/docs/0.45/getting-started.html +++ b/docs/0.45/getting-started.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

            If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

            Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

            -

            The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

            +

            The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

            Development OS: diff --git a/docs/0.45/getting-started/index.html b/docs/0.45/getting-started/index.html index 4948d7529a3..54b5250eb7b 100644 --- a/docs/0.45/getting-started/index.html +++ b/docs/0.45/getting-started/index.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

            If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

            Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

            -

            The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

            +

            The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

            Development OS: diff --git a/docs/0.45/images.html b/docs/0.45/images.html index 6b8280f190f..61dccd4ee8a 100644 --- a/docs/0.45/images.html +++ b/docs/0.45/images.html @@ -69,7 +69,7 @@ } });
            Edit

            Images

            Static Image Resources

            -

            React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

            +

            React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

            <Image source={require('./my-icon.png')} />

            The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

            @@ -88,7 +88,7 @@

            On Windows, you might need to restart the packager if you add new images to your project.

            Here are some benefits that you get:

              -
            1. Same system on iOS and Android.
              2. +
            2. Same system on Android and iOS.
            3. Images live in the same folder as your JavaScript code. Components are self-contained.
            4. No global namespace, i.e. you don't have to worry about name collisions.
            5. Only the images that are actually used will be packaged into your app.
              6. diff --git a/docs/0.45/images/index.html b/docs/0.45/images/index.html index 6b8280f190f..61dccd4ee8a 100644 --- a/docs/0.45/images/index.html +++ b/docs/0.45/images/index.html @@ -69,7 +69,7 @@ } });
            Edit

            Images

            Static Image Resources

            -

            React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

            +

            React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

            <Image source={require('./my-icon.png')} />

            The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

            @@ -88,7 +88,7 @@

            On Windows, you might need to restart the packager if you add new images to your project.

            Here are some benefits that you get:

              -
            1. Same system on iOS and Android.
              2. +
            2. Same system on Android and iOS.
            3. Images live in the same folder as your JavaScript code. Components are self-contained.
            4. No global namespace, i.e. you don't have to worry about name collisions.
            5. Only the images that are actually used will be packaged into your app.
              6. diff --git a/docs/0.45/navigation.html b/docs/0.45/navigation.html index 64b2958a66c..f63b94b6208 100644 --- a/docs/0.45/navigation.html +++ b/docs/0.45/navigation.html @@ -69,8 +69,8 @@ } });
            Edit

            Navigating Between Screens

            Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

            -

            This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

            -

            If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

            +

            This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

            +

            If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

            React Navigation

            The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

            The first step is to install in your project:

            diff --git a/docs/0.45/navigation/index.html b/docs/0.45/navigation/index.html index 64b2958a66c..f63b94b6208 100644 --- a/docs/0.45/navigation/index.html +++ b/docs/0.45/navigation/index.html @@ -69,8 +69,8 @@ } });
            Edit

            Navigating Between Screens

            Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

            -

            This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

            -

            If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

            +

            This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

            +

            If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

            React Navigation

            The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

            The first step is to install in your project:

            diff --git a/docs/0.45/picker.html b/docs/0.45/picker.html index 52da23c3a77..2576bdda6c5 100644 --- a/docs/0.45/picker.html +++ b/docs/0.45/picker.html @@ -1,4 +1,4 @@ -Picker · React Native
            Edit

            Picker

            Renders the native picker component on iOS and Android. Example:

            +
            Edit

            Picker

            Renders the native picker component on Android and iOS. Example:

            <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.45/picker/index.html b/docs/0.45/picker/index.html
index 52da23c3a77..2576bdda6c5 100644
--- a/docs/0.45/picker/index.html
+++ b/docs/0.45/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
            Edit

            Picker

            Renders the native picker component on iOS and Android. Example:

            +
            Edit

            Picker

            Renders the native picker component on Android and iOS. Example:

            <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.45/platform-specific-code.html b/docs/0.45/platform-specific-code.html
index cc69617c3dd..265ea885e38 100644
--- a/docs/0.45/platform-specific-code.html
+++ b/docs/0.45/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
            Edit

            Platform Specific Code

            When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

            +
            Edit

            Platform Specific Code

            When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

            React Native provides two ways to organize your code and separate it by platform:

            • Using the Platform module.
              • diff --git a/docs/0.45/platform-specific-code/index.html b/docs/0.45/platform-specific-code/index.html index cc69617c3dd..265ea885e38 100644 --- a/docs/0.45/platform-specific-code/index.html +++ b/docs/0.45/platform-specific-code/index.html @@ -1,4 +1,4 @@ -Platform Specific Code · React Native
            Edit

            Platform Specific Code

            When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

            +
            Edit

            Platform Specific Code

            When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

            React Native provides two ways to organize your code and separate it by platform:

            • Using the Platform module.
              • diff --git a/docs/0.46/accessibility.html b/docs/0.46/accessibility.html index b94371bc084..35c802157ab 100644 --- a/docs/0.46/accessibility.html +++ b/docs/0.46/accessibility.html @@ -1,4 +1,4 @@ -Accessibility · React Native
            Edit

            Accessibility

            Native App Accessibility (iOS and Android)

            -

            Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

            +
            Edit

            Accessibility

            Native App Accessibility (Android and iOS)

            +

            Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

            In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

            Making Apps Accessible

            Accessibility properties

            @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService             -
            ← AnimationsImproving User Experience →
            Edit

            Accessibility

            Native App Accessibility (iOS and Android)

            -

            Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

            +
            Edit

            Accessibility

            Native App Accessibility (Android and iOS)

            +

            Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

            In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

            Making Apps Accessible

            Accessibility properties

            @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService             -
            ← AnimationsImproving User Experience →
            Edit

            Alert

            Launches an alert dialog with the specified title and message.

            Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

            -

            This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

            +

            This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

            iOS

            On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

            Android

            @@ -83,7 +83,7 @@

            By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

            Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

            Example usage:

            -
            // Works on both iOS and Android
+
            // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.46/alert/index.html b/docs/0.46/alert/index.html
index c334346194c..23d7d7bd684 100644
--- a/docs/0.46/alert/index.html
+++ b/docs/0.46/alert/index.html
@@ -70,7 +70,7 @@
             });
            Edit

            Alert

            Launches an alert dialog with the specified title and message.

            Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

            -

            This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

            +

            This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

            iOS

            On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

            Android

            @@ -83,7 +83,7 @@

            By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

            Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

            Example usage:

            -
            // Works on both iOS and Android
+
            // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.46/clipboard.html b/docs/0.46/clipboard.html
index 5099bc4f05b..28e39e9a330 100644
--- a/docs/0.46/clipboard.html
+++ b/docs/0.46/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
            Edit

            Clipboard

            Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

            +
            Edit

            Clipboard

            Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

            Methods

            • getString
              • diff --git a/docs/0.46/clipboard/index.html b/docs/0.46/clipboard/index.html index 5099bc4f05b..28e39e9a330 100644 --- a/docs/0.46/clipboard/index.html +++ b/docs/0.46/clipboard/index.html @@ -1,4 +1,4 @@ -Clipboard · React Native
            Edit

            Clipboard

            Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

            +
            Edit

            Clipboard

            Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

            Methods

            • getString
              • diff --git a/docs/0.46/components-and-apis.html b/docs/0.46/components-and-apis.html index 59c08dbe0f1..d2a926cbab2 100644 --- a/docs/0.46/components-and-apis.html +++ b/docs/0.46/components-and-apis.html @@ -130,7 +130,7 @@

              Picker

              -

              Renders the native picker component on iOS and Android.

              +

              Renders the native picker component on Android and iOS.
              @@ -290,7 +290,7 @@

              Clipboard

              -

              Provides an interface for setting and getting content from the clipboard on both iOS and Android.

              +

              Provides an interface for setting and getting content from the clipboard on both Android and iOS.
              diff --git a/docs/0.46/components-and-apis/index.html b/docs/0.46/components-and-apis/index.html index 59c08dbe0f1..d2a926cbab2 100644 --- a/docs/0.46/components-and-apis/index.html +++ b/docs/0.46/components-and-apis/index.html @@ -130,7 +130,7 @@

              Picker

              -

              Renders the native picker component on iOS and Android.

              +

              Renders the native picker component on Android and iOS.
              @@ -290,7 +290,7 @@

              Clipboard

              -

              Provides an interface for setting and getting content from the clipboard on both iOS and Android.

              +

              Provides an interface for setting and getting content from the clipboard on both Android and iOS.
              diff --git a/docs/0.46/getting-started.html b/docs/0.46/getting-started.html index f2c62ada325..edf9304d512 100644 --- a/docs/0.46/getting-started.html +++ b/docs/0.46/getting-started.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

              If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

              Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

              -

              The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

              +

              The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

              Development OS: diff --git a/docs/0.46/getting-started/index.html b/docs/0.46/getting-started/index.html index f2c62ada325..edf9304d512 100644 --- a/docs/0.46/getting-started/index.html +++ b/docs/0.46/getting-started/index.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

              If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

              Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

              -

              The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

              +

              The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

              Development OS: diff --git a/docs/0.46/images.html b/docs/0.46/images.html index c7ec170096d..180d5fc400f 100644 --- a/docs/0.46/images.html +++ b/docs/0.46/images.html @@ -69,7 +69,7 @@ } });
              Edit

              Images

              Static Image Resources

              -

              React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

              +

              React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

              <Image source={require('./my-icon.png')} />

              The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

              @@ -88,7 +88,7 @@

              On Windows, you might need to restart the packager if you add new images to your project.

              Here are some benefits that you get:

                -
              1. Same system on iOS and Android.
                2. +
              2. Same system on Android and iOS.
              3. Images live in the same folder as your JavaScript code. Components are self-contained.
              4. No global namespace, i.e. you don't have to worry about name collisions.
              5. Only the images that are actually used will be packaged into your app.
                6. diff --git a/docs/0.46/images/index.html b/docs/0.46/images/index.html index c7ec170096d..180d5fc400f 100644 --- a/docs/0.46/images/index.html +++ b/docs/0.46/images/index.html @@ -69,7 +69,7 @@ } });
              Edit

              Images

              Static Image Resources

              -

              React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

              +

              React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

              <Image source={require('./my-icon.png')} />

              The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

              @@ -88,7 +88,7 @@

              On Windows, you might need to restart the packager if you add new images to your project.

              Here are some benefits that you get:

                -
              1. Same system on iOS and Android.
                2. +
              2. Same system on Android and iOS.
              3. Images live in the same folder as your JavaScript code. Components are self-contained.
              4. No global namespace, i.e. you don't have to worry about name collisions.
              5. Only the images that are actually used will be packaged into your app.
                6. diff --git a/docs/0.46/navigation.html b/docs/0.46/navigation.html index 708ff8bf227..b10be429298 100644 --- a/docs/0.46/navigation.html +++ b/docs/0.46/navigation.html @@ -69,8 +69,8 @@ } });
              Edit

              Navigating Between Screens

              Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

              -

              This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

              -

              If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

              +

              This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

              +

              If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

              React Navigation

              The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

              The first step is to install in your project:

              diff --git a/docs/0.46/navigation/index.html b/docs/0.46/navigation/index.html index 708ff8bf227..b10be429298 100644 --- a/docs/0.46/navigation/index.html +++ b/docs/0.46/navigation/index.html @@ -69,8 +69,8 @@ } });
              Edit

              Navigating Between Screens

              Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

              -

              This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

              -

              If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

              +

              This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

              +

              If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

              React Navigation

              The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

              The first step is to install in your project:

              diff --git a/docs/0.46/picker.html b/docs/0.46/picker.html index 8ae06049328..66042fc249d 100644 --- a/docs/0.46/picker.html +++ b/docs/0.46/picker.html @@ -1,4 +1,4 @@ -Picker · React Native
              Edit

              Picker

              Renders the native picker component on iOS and Android. Example:

              +
              Edit

              Picker

              Renders the native picker component on Android and iOS. Example:

              <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.46/picker/index.html b/docs/0.46/picker/index.html
index 8ae06049328..66042fc249d 100644
--- a/docs/0.46/picker/index.html
+++ b/docs/0.46/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
              Edit

              Picker

              Renders the native picker component on iOS and Android. Example:

              +
              Edit

              Picker

              Renders the native picker component on Android and iOS. Example:

              <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.46/platform-specific-code.html b/docs/0.46/platform-specific-code.html
index 69181487cd2..b6970f9e976 100644
--- a/docs/0.46/platform-specific-code.html
+++ b/docs/0.46/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
              Edit

              Platform Specific Code

              When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

              +
              Edit

              Platform Specific Code

              When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

              React Native provides two ways to organize your code and separate it by platform:

              • Using the Platform module.
                • diff --git a/docs/0.46/platform-specific-code/index.html b/docs/0.46/platform-specific-code/index.html index 69181487cd2..b6970f9e976 100644 --- a/docs/0.46/platform-specific-code/index.html +++ b/docs/0.46/platform-specific-code/index.html @@ -1,4 +1,4 @@ -Platform Specific Code · React Native
              Edit

              Platform Specific Code

              When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

              +
              Edit

              Platform Specific Code

              When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

              React Native provides two ways to organize your code and separate it by platform:

              • Using the Platform module.
                • diff --git a/docs/0.47/accessibility.html b/docs/0.47/accessibility.html index 2f349f09dbb..e96306df8e3 100644 --- a/docs/0.47/accessibility.html +++ b/docs/0.47/accessibility.html @@ -1,4 +1,4 @@ -Accessibility · React Native
              Edit

              Accessibility

              Native App Accessibility (iOS and Android)

              -

              Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

              +
              Edit

              Accessibility

              Native App Accessibility (Android and iOS)

              +

              Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

              In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

              Making Apps Accessible

              Accessibility properties

              @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService               -
              ← AnimationsImproving User Experience →
              Edit

              Accessibility

              Native App Accessibility (iOS and Android)

              -

              Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

              +
              Edit

              Accessibility

              Native App Accessibility (Android and iOS)

              +

              Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

              In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

              Making Apps Accessible

              Accessibility properties

              @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService               -
              ← AnimationsImproving User Experience →
              Edit

              Alert

              Launches an alert dialog with the specified title and message.

              Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

              -

              This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

              +

              This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

              iOS

              On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

              Android

              @@ -83,7 +83,7 @@

              By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

              Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

              Example usage:

              -
              // Works on both iOS and Android
+
              // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.47/alert/index.html b/docs/0.47/alert/index.html
index 9337e2c0589..f5b30b34d42 100644
--- a/docs/0.47/alert/index.html
+++ b/docs/0.47/alert/index.html
@@ -70,7 +70,7 @@
             });
              Edit

              Alert

              Launches an alert dialog with the specified title and message.

              Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

              -

              This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

              +

              This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

              iOS

              On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

              Android

              @@ -83,7 +83,7 @@

              By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

              Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

              Example usage:

              -
              // Works on both iOS and Android
+
              // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.47/clipboard.html b/docs/0.47/clipboard.html
index ca6b41f33c0..07b6dd83ba1 100644
--- a/docs/0.47/clipboard.html
+++ b/docs/0.47/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
              Edit

              Clipboard

              Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

              +
              Edit

              Clipboard

              Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

              Methods

              • getString
                • diff --git a/docs/0.47/clipboard/index.html b/docs/0.47/clipboard/index.html index ca6b41f33c0..07b6dd83ba1 100644 --- a/docs/0.47/clipboard/index.html +++ b/docs/0.47/clipboard/index.html @@ -1,4 +1,4 @@ -Clipboard · React Native
              Edit

              Clipboard

              Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

              +
              Edit

              Clipboard

              Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

              Methods

              • getString
                • diff --git a/docs/0.47/components-and-apis.html b/docs/0.47/components-and-apis.html index 53e86f11c7c..0659d9afeab 100644 --- a/docs/0.47/components-and-apis.html +++ b/docs/0.47/components-and-apis.html @@ -130,7 +130,7 @@

                Picker

                -

                Renders the native picker component on iOS and Android.

                +

                Renders the native picker component on Android and iOS.
                @@ -290,7 +290,7 @@

                Clipboard

                -

                Provides an interface for setting and getting content from the clipboard on both iOS and Android.

                +

                Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                diff --git a/docs/0.47/components-and-apis/index.html b/docs/0.47/components-and-apis/index.html index 53e86f11c7c..0659d9afeab 100644 --- a/docs/0.47/components-and-apis/index.html +++ b/docs/0.47/components-and-apis/index.html @@ -130,7 +130,7 @@

                Picker

                -

                Renders the native picker component on iOS and Android.

                +

                Renders the native picker component on Android and iOS.
                @@ -290,7 +290,7 @@

                Clipboard

                -

                Provides an interface for setting and getting content from the clipboard on both iOS and Android.

                +

                Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                diff --git a/docs/0.47/getting-started.html b/docs/0.47/getting-started.html index a0a0ead690d..6487f30ed25 100644 --- a/docs/0.47/getting-started.html +++ b/docs/0.47/getting-started.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

                If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

                Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

                -

                The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

                +

                The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

                Development OS: diff --git a/docs/0.47/getting-started/index.html b/docs/0.47/getting-started/index.html index a0a0ead690d..6487f30ed25 100644 --- a/docs/0.47/getting-started/index.html +++ b/docs/0.47/getting-started/index.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

                If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

                Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

                -

                The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

                +

                The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

                Development OS: diff --git a/docs/0.47/images.html b/docs/0.47/images.html index 0bc7dac186c..e8c2f75ccfc 100644 --- a/docs/0.47/images.html +++ b/docs/0.47/images.html @@ -69,7 +69,7 @@ } });
                Edit

                Images

                Static Image Resources

                -

                React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

                +

                React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

                <Image source={require('./my-icon.png')} />

                The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

                @@ -88,7 +88,7 @@

                On Windows, you might need to restart the packager if you add new images to your project.

                Here are some benefits that you get:

                  -
                1. Same system on iOS and Android.
                  2. +
                2. Same system on Android and iOS.
                3. Images live in the same folder as your JavaScript code. Components are self-contained.
                4. No global namespace, i.e. you don't have to worry about name collisions.
                5. Only the images that are actually used will be packaged into your app.
                  6. diff --git a/docs/0.47/images/index.html b/docs/0.47/images/index.html index 0bc7dac186c..e8c2f75ccfc 100644 --- a/docs/0.47/images/index.html +++ b/docs/0.47/images/index.html @@ -69,7 +69,7 @@ } });
                Edit

                Images

                Static Image Resources

                -

                React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

                +

                React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

                <Image source={require('./my-icon.png')} />

                The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

                @@ -88,7 +88,7 @@

                On Windows, you might need to restart the packager if you add new images to your project.

                Here are some benefits that you get:

                  -
                1. Same system on iOS and Android.
                  2. +
                2. Same system on Android and iOS.
                3. Images live in the same folder as your JavaScript code. Components are self-contained.
                4. No global namespace, i.e. you don't have to worry about name collisions.
                5. Only the images that are actually used will be packaged into your app.
                  6. diff --git a/docs/0.47/navigation.html b/docs/0.47/navigation.html index 1c3cadd4fc1..611119b01f0 100644 --- a/docs/0.47/navigation.html +++ b/docs/0.47/navigation.html @@ -69,8 +69,8 @@ } });
                Edit

                Navigating Between Screens

                Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

                -

                This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

                -

                If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

                +

                This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

                +

                If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

                React Navigation

                The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

                The first step is to install in your project:

                diff --git a/docs/0.47/navigation/index.html b/docs/0.47/navigation/index.html index 1c3cadd4fc1..611119b01f0 100644 --- a/docs/0.47/navigation/index.html +++ b/docs/0.47/navigation/index.html @@ -69,8 +69,8 @@ } });
                Edit

                Navigating Between Screens

                Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

                -

                This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

                -

                If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

                +

                This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

                +

                If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

                React Navigation

                The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

                The first step is to install in your project:

                diff --git a/docs/0.47/picker.html b/docs/0.47/picker.html index ce84ff4635c..e31888ba0c7 100644 --- a/docs/0.47/picker.html +++ b/docs/0.47/picker.html @@ -1,4 +1,4 @@ -Picker · React Native
                Edit

                Picker

                Renders the native picker component on iOS and Android. Example:

                +
                Edit

                Picker

                Renders the native picker component on Android and iOS. Example:

                <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.47/picker/index.html b/docs/0.47/picker/index.html
index ce84ff4635c..e31888ba0c7 100644
--- a/docs/0.47/picker/index.html
+++ b/docs/0.47/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                Edit

                Picker

                Renders the native picker component on iOS and Android. Example:

                +
                Edit

                Picker

                Renders the native picker component on Android and iOS. Example:

                <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.47/platform-specific-code.html b/docs/0.47/platform-specific-code.html
index b139ea79643..c66d9e726db 100644
--- a/docs/0.47/platform-specific-code.html
+++ b/docs/0.47/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                Edit

                Platform Specific Code

                When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

                +
                Edit

                Platform Specific Code

                When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

                React Native provides two ways to organize your code and separate it by platform:

                • Using the Platform module.
                  • diff --git a/docs/0.47/platform-specific-code/index.html b/docs/0.47/platform-specific-code/index.html index b139ea79643..c66d9e726db 100644 --- a/docs/0.47/platform-specific-code/index.html +++ b/docs/0.47/platform-specific-code/index.html @@ -1,4 +1,4 @@ -Platform Specific Code · React Native
                Edit

                Platform Specific Code

                When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

                +
                Edit

                Platform Specific Code

                When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

                React Native provides two ways to organize your code and separate it by platform:

                • Using the Platform module.
                  • diff --git a/docs/0.48/accessibility.html b/docs/0.48/accessibility.html index 1ea78ffe94c..017851f78ed 100644 --- a/docs/0.48/accessibility.html +++ b/docs/0.48/accessibility.html @@ -1,4 +1,4 @@ -Accessibility · React Native
                Edit

                Accessibility

                Native App Accessibility (iOS and Android)

                -

                Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                +
                Edit

                Accessibility

                Native App Accessibility (Android and iOS)

                +

                Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

                Making Apps Accessible

                Accessibility properties

                @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService                 -
                ← AnimationsImproving User Experience →
                Edit

                Accessibility

                Native App Accessibility (iOS and Android)

                -

                Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                +
                Edit

                Accessibility

                Native App Accessibility (Android and iOS)

                +

                Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

                Making Apps Accessible

                Accessibility properties

                @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService                 -
                ← AnimationsImproving User Experience →
                Edit

                Alert

                Launches an alert dialog with the specified title and message.

                Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

                -

                This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                +

                This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                iOS

                On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

                Android

                @@ -83,7 +83,7 @@

                By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                Example usage:

                -
                // Works on both iOS and Android
+
                // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.48/alert/index.html b/docs/0.48/alert/index.html
index a8be188f206..2fcaa3588c7 100644
--- a/docs/0.48/alert/index.html
+++ b/docs/0.48/alert/index.html
@@ -70,7 +70,7 @@
             });
                Edit

                Alert

                Launches an alert dialog with the specified title and message.

                Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

                -

                This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                +

                This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                iOS

                On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

                Android

                @@ -83,7 +83,7 @@

                By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                Example usage:

                -
                // Works on both iOS and Android
+
                // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.48/clipboard.html b/docs/0.48/clipboard.html
index 98bc9ed0af7..b606f797bf9 100644
--- a/docs/0.48/clipboard.html
+++ b/docs/0.48/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                Edit

                Clipboard

                Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

                +
                Edit

                Clipboard

                Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

                Methods

                • getString
                  • diff --git a/docs/0.48/clipboard/index.html b/docs/0.48/clipboard/index.html index 98bc9ed0af7..b606f797bf9 100644 --- a/docs/0.48/clipboard/index.html +++ b/docs/0.48/clipboard/index.html @@ -1,4 +1,4 @@ -Clipboard · React Native
                Edit

                Clipboard

                Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

                +
                Edit

                Clipboard

                Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

                Methods

                • getString
                  • diff --git a/docs/0.48/components-and-apis.html b/docs/0.48/components-and-apis.html index 66304d1f370..95c463133e1 100644 --- a/docs/0.48/components-and-apis.html +++ b/docs/0.48/components-and-apis.html @@ -130,7 +130,7 @@

                  Picker

                  -

                  Renders the native picker component on iOS and Android.

                  +

                  Renders the native picker component on Android and iOS.
                  @@ -290,7 +290,7 @@

                  Clipboard

                  -

                  Provides an interface for setting and getting content from the clipboard on both iOS and Android.

                  +

                  Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                  diff --git a/docs/0.48/components-and-apis/index.html b/docs/0.48/components-and-apis/index.html index 66304d1f370..95c463133e1 100644 --- a/docs/0.48/components-and-apis/index.html +++ b/docs/0.48/components-and-apis/index.html @@ -130,7 +130,7 @@

                  Picker

                  -

                  Renders the native picker component on iOS and Android.

                  +

                  Renders the native picker component on Android and iOS.
                  @@ -290,7 +290,7 @@

                  Clipboard

                  -

                  Provides an interface for setting and getting content from the clipboard on both iOS and Android.

                  +

                  Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                  diff --git a/docs/0.48/getting-started.html b/docs/0.48/getting-started.html index 20abbb040da..11e6ceb3811 100644 --- a/docs/0.48/getting-started.html +++ b/docs/0.48/getting-started.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

                  If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

                  Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

                  -

                  The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

                  +

                  The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

                  Development OS: diff --git a/docs/0.48/getting-started/index.html b/docs/0.48/getting-started/index.html index 20abbb040da..11e6ceb3811 100644 --- a/docs/0.48/getting-started/index.html +++ b/docs/0.48/getting-started/index.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

                  If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

                  Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

                  -

                  The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

                  +

                  The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

                  Development OS: diff --git a/docs/0.48/images.html b/docs/0.48/images.html index 97f27600dd6..66900ca87b6 100644 --- a/docs/0.48/images.html +++ b/docs/0.48/images.html @@ -69,7 +69,7 @@ } });
                  Edit

                  Images

                  Static Image Resources

                  -

                  React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

                  +

                  React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

                  <Image source={require('./my-icon.png')} />

                  The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

                  @@ -88,7 +88,7 @@

                  On Windows, you might need to restart the packager if you add new images to your project.

                  Here are some benefits that you get:

                    -
                  1. Same system on iOS and Android.
                    2. +
                  2. Same system on Android and iOS.
                  3. Images live in the same folder as your JavaScript code. Components are self-contained.
                  4. No global namespace, i.e. you don't have to worry about name collisions.
                  5. Only the images that are actually used will be packaged into your app.
                    6. diff --git a/docs/0.48/images/index.html b/docs/0.48/images/index.html index 97f27600dd6..66900ca87b6 100644 --- a/docs/0.48/images/index.html +++ b/docs/0.48/images/index.html @@ -69,7 +69,7 @@ } });
                  Edit

                  Images

                  Static Image Resources

                  -

                  React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

                  +

                  React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

                  <Image source={require('./my-icon.png')} />

                  The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

                  @@ -88,7 +88,7 @@

                  On Windows, you might need to restart the packager if you add new images to your project.

                  Here are some benefits that you get:

                    -
                  1. Same system on iOS and Android.
                    2. +
                  2. Same system on Android and iOS.
                  3. Images live in the same folder as your JavaScript code. Components are self-contained.
                  4. No global namespace, i.e. you don't have to worry about name collisions.
                  5. Only the images that are actually used will be packaged into your app.
                    6. diff --git a/docs/0.48/navigation.html b/docs/0.48/navigation.html index b818a52b52a..5b7df13c475 100644 --- a/docs/0.48/navigation.html +++ b/docs/0.48/navigation.html @@ -69,8 +69,8 @@ } });
                  Edit

                  Navigating Between Screens

                  Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

                  -

                  This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

                  -

                  If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

                  +

                  This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

                  +

                  If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

                  React Navigation

                  The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

                  The first step is to install in your project:

                  diff --git a/docs/0.48/navigation/index.html b/docs/0.48/navigation/index.html index b818a52b52a..5b7df13c475 100644 --- a/docs/0.48/navigation/index.html +++ b/docs/0.48/navigation/index.html @@ -69,8 +69,8 @@ } });
                  Edit

                  Navigating Between Screens

                  Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

                  -

                  This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

                  -

                  If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

                  +

                  This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

                  +

                  If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

                  React Navigation

                  The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

                  The first step is to install in your project:

                  diff --git a/docs/0.48/picker.html b/docs/0.48/picker.html index c6fb81f108d..de06b842001 100644 --- a/docs/0.48/picker.html +++ b/docs/0.48/picker.html @@ -1,4 +1,4 @@ -Picker · React Native
                  Edit

                  Picker

                  Renders the native picker component on iOS and Android. Example:

                  +
                  Edit

                  Picker

                  Renders the native picker component on Android and iOS. Example:

                  <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.48/picker/index.html b/docs/0.48/picker/index.html
index c6fb81f108d..de06b842001 100644
--- a/docs/0.48/picker/index.html
+++ b/docs/0.48/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                  Edit

                  Picker

                  Renders the native picker component on iOS and Android. Example:

                  +
                  Edit

                  Picker

                  Renders the native picker component on Android and iOS. Example:

                  <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.48/platform-specific-code.html b/docs/0.48/platform-specific-code.html
index 08596c2072c..8a2c170d3d0 100644
--- a/docs/0.48/platform-specific-code.html
+++ b/docs/0.48/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                  Edit

                  Platform Specific Code

                  When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

                  +
                  Edit

                  Platform Specific Code

                  When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

                  React Native provides two ways to organize your code and separate it by platform:

                  • Using the Platform module.
                    • diff --git a/docs/0.48/platform-specific-code/index.html b/docs/0.48/platform-specific-code/index.html index 08596c2072c..8a2c170d3d0 100644 --- a/docs/0.48/platform-specific-code/index.html +++ b/docs/0.48/platform-specific-code/index.html @@ -1,4 +1,4 @@ -Platform Specific Code · React Native
                  Edit

                  Platform Specific Code

                  When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

                  +
                  Edit

                  Platform Specific Code

                  When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

                  React Native provides two ways to organize your code and separate it by platform:

                  • Using the Platform module.
                    • diff --git a/docs/0.49/accessibility.html b/docs/0.49/accessibility.html index 94b74aad705..9d7957b9998 100644 --- a/docs/0.49/accessibility.html +++ b/docs/0.49/accessibility.html @@ -1,4 +1,4 @@ -Accessibility · React Native
                  Edit

                  Accessibility

                  Native App Accessibility (iOS and Android)

                  -

                  Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                  +
                  Edit

                  Accessibility

                  Native App Accessibility (Android and iOS)

                  +

                  Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                  In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

                  Making Apps Accessible

                  Accessibility properties

                  @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService                   -
                  ← AnimationsImproving User Experience →
                  Edit

                  Accessibility

                  Native App Accessibility (iOS and Android)

                  -

                  Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                  +
                  Edit

                  Accessibility

                  Native App Accessibility (Android and iOS)

                  +

                  Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                  In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

                  Making Apps Accessible

                  Accessibility properties

                  @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService                   -
                  ← AnimationsImproving User Experience →
                  Edit

                  Alert

                  Launches an alert dialog with the specified title and message.

                  Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

                  -

                  This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                  +

                  This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                  iOS

                  On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

                  Android

                  @@ -83,7 +83,7 @@

                  By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                  Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                  Example usage:

                  -
                  // Works on both iOS and Android
+
                  // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.49/alert/index.html b/docs/0.49/alert/index.html
index bed4e849abf..51be137a031 100644
--- a/docs/0.49/alert/index.html
+++ b/docs/0.49/alert/index.html
@@ -70,7 +70,7 @@
             });
                  Edit

                  Alert

                  Launches an alert dialog with the specified title and message.

                  Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

                  -

                  This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                  +

                  This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                  iOS

                  On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

                  Android

                  @@ -83,7 +83,7 @@

                  By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                  Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                  Example usage:

                  -
                  // Works on both iOS and Android
+
                  // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.49/clipboard.html b/docs/0.49/clipboard.html
index 6bb82711c64..ab850adbc3d 100644
--- a/docs/0.49/clipboard.html
+++ b/docs/0.49/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                  Edit

                  Clipboard

                  Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

                  +
                  Edit

                  Clipboard

                  Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

                  Methods

                  • getString
                    • diff --git a/docs/0.49/clipboard/index.html b/docs/0.49/clipboard/index.html index 6bb82711c64..ab850adbc3d 100644 --- a/docs/0.49/clipboard/index.html +++ b/docs/0.49/clipboard/index.html @@ -1,4 +1,4 @@ -Clipboard · React Native
                  Edit

                  Clipboard

                  Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

                  +
                  Edit

                  Clipboard

                  Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

                  Methods

                  • getString
                    • diff --git a/docs/0.49/components-and-apis.html b/docs/0.49/components-and-apis.html index a0b94ea4455..733c78ce764 100644 --- a/docs/0.49/components-and-apis.html +++ b/docs/0.49/components-and-apis.html @@ -130,7 +130,7 @@

                    Picker

                    -

                    Renders the native picker component on iOS and Android.

                    +

                    Renders the native picker component on Android and iOS.
                    @@ -290,7 +290,7 @@

                    Clipboard

                    -

                    Provides an interface for setting and getting content from the clipboard on both iOS and Android.

                    +

                    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                    diff --git a/docs/0.49/components-and-apis/index.html b/docs/0.49/components-and-apis/index.html index a0b94ea4455..733c78ce764 100644 --- a/docs/0.49/components-and-apis/index.html +++ b/docs/0.49/components-and-apis/index.html @@ -130,7 +130,7 @@

                    Picker

                    -

                    Renders the native picker component on iOS and Android.

                    +

                    Renders the native picker component on Android and iOS.
                    @@ -290,7 +290,7 @@

                    Clipboard

                    -

                    Provides an interface for setting and getting content from the clipboard on both iOS and Android.

                    +

                    Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                    diff --git a/docs/0.49/getting-started.html b/docs/0.49/getting-started.html index 2fa7b373298..821b80e99f5 100644 --- a/docs/0.49/getting-started.html +++ b/docs/0.49/getting-started.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

                    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

                    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

                    -

                    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

                    +

                    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

                    Development OS: diff --git a/docs/0.49/getting-started/index.html b/docs/0.49/getting-started/index.html index 2fa7b373298..821b80e99f5 100644 --- a/docs/0.49/getting-started/index.html +++ b/docs/0.49/getting-started/index.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

                    If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

                    Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

                    -

                    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

                    +

                    The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

                    Development OS: diff --git a/docs/0.49/images.html b/docs/0.49/images.html index ac03406db5b..9dd50e693a7 100644 --- a/docs/0.49/images.html +++ b/docs/0.49/images.html @@ -69,7 +69,7 @@ } });
                    Edit

                    Images

                    Static Image Resources

                    -

                    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

                    +

                    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

                    <Image source={require('./my-icon.png')} />

                    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

                    @@ -88,7 +88,7 @@

                    On Windows, you might need to restart the packager if you add new images to your project.

                    Here are some benefits that you get:

                      -
                    1. Same system on iOS and Android.
                      2. +
                    2. Same system on Android and iOS.
                    3. Images live in the same folder as your JavaScript code. Components are self-contained.
                    4. No global namespace, i.e. you don't have to worry about name collisions.
                    5. Only the images that are actually used will be packaged into your app.
                      6. diff --git a/docs/0.49/images/index.html b/docs/0.49/images/index.html index ac03406db5b..9dd50e693a7 100644 --- a/docs/0.49/images/index.html +++ b/docs/0.49/images/index.html @@ -69,7 +69,7 @@ } });
                    Edit

                    Images

                    Static Image Resources

                    -

                    React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

                    +

                    React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

                    <Image source={require('./my-icon.png')} />

                    The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

                    @@ -88,7 +88,7 @@

                    On Windows, you might need to restart the packager if you add new images to your project.

                    Here are some benefits that you get:

                      -
                    1. Same system on iOS and Android.
                      2. +
                    2. Same system on Android and iOS.
                    3. Images live in the same folder as your JavaScript code. Components are self-contained.
                    4. No global namespace, i.e. you don't have to worry about name collisions.
                    5. Only the images that are actually used will be packaged into your app.
                      6. diff --git a/docs/0.49/navigation.html b/docs/0.49/navigation.html index 08140a1a0b1..bf7f0df2f2d 100644 --- a/docs/0.49/navigation.html +++ b/docs/0.49/navigation.html @@ -69,8 +69,8 @@ } });
                    Edit

                    Navigating Between Screens

                    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

                    -

                    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

                    -

                    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

                    +

                    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

                    +

                    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

                    React Navigation

                    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

                    The first step is to install in your project:

                    diff --git a/docs/0.49/navigation/index.html b/docs/0.49/navigation/index.html index 08140a1a0b1..bf7f0df2f2d 100644 --- a/docs/0.49/navigation/index.html +++ b/docs/0.49/navigation/index.html @@ -69,8 +69,8 @@ } });
                    Edit

                    Navigating Between Screens

                    Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

                    -

                    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

                    -

                    If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

                    +

                    This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

                    +

                    If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

                    React Navigation

                    The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

                    The first step is to install in your project:

                    diff --git a/docs/0.49/picker.html b/docs/0.49/picker.html index c944fc632ed..03389dc7c99 100644 --- a/docs/0.49/picker.html +++ b/docs/0.49/picker.html @@ -1,4 +1,4 @@ -Picker · React Native
                    Edit

                    Picker

                    Renders the native picker component on iOS and Android. Example:

                    +
                    Edit

                    Picker

                    Renders the native picker component on Android and iOS. Example:

                    <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.49/picker/index.html b/docs/0.49/picker/index.html
index c944fc632ed..03389dc7c99 100644
--- a/docs/0.49/picker/index.html
+++ b/docs/0.49/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                    Edit

                    Picker

                    Renders the native picker component on iOS and Android. Example:

                    +
                    Edit

                    Picker

                    Renders the native picker component on Android and iOS. Example:

                    <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.49/platform-specific-code.html b/docs/0.49/platform-specific-code.html
index f5c3991c359..01ff083bc55 100644
--- a/docs/0.49/platform-specific-code.html
+++ b/docs/0.49/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                    Edit

                    Platform Specific Code

                    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

                    +
                    Edit

                    Platform Specific Code

                    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

                    React Native provides two ways to organize your code and separate it by platform:

                    • Using the Platform module.
                      • diff --git a/docs/0.49/platform-specific-code/index.html b/docs/0.49/platform-specific-code/index.html index f5c3991c359..01ff083bc55 100644 --- a/docs/0.49/platform-specific-code/index.html +++ b/docs/0.49/platform-specific-code/index.html @@ -1,4 +1,4 @@ -Platform Specific Code · React Native
                    Edit

                    Platform Specific Code

                    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

                    +
                    Edit

                    Platform Specific Code

                    When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

                    React Native provides two ways to organize your code and separate it by platform:

                    • Using the Platform module.
                      • diff --git a/docs/0.49/text.html b/docs/0.49/text.html index d202f30cdea..d4fb34f8425 100644 --- a/docs/0.49/text.html +++ b/docs/0.49/text.html @@ -124,7 +124,7 @@ AppRegistry.registerComponent('TextInANest', () width: 100%; " >

                    Nested text

                    -

                    Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.

                    +

                    Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.

                    Nested text

                    -

                    Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.

                    +

                    Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.

                    Edit

                    Accessibility

                    Native App Accessibility (iOS and Android)

                    -

                    Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                    +
                    Edit

                    Accessibility

                    Native App Accessibility (Android and iOS)

                    +

                    Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                    In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

                    Making Apps Accessible

                    Accessibility properties

                    @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService                     -
                    ← AnimationsImproving User Experience →
                    Edit

                    Accessibility

                    Native App Accessibility (iOS and Android)

                    -

                    Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                    +
                    Edit

                    Accessibility

                    Native App Accessibility (Android and iOS)

                    +

                    Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                    In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

                    Making Apps Accessible

                    Accessibility properties

                    @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService -
                    ← AnimationsImproving User Experience →

                    0.5

                    Edit

                    Alert

                    Use Alert to display an alert dialog.

                    -

                    This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

                    +

                    This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

                    Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

                    On iOS, you can specify any number of buttons.

                    On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

                    @@ -25,7 +25,7 @@

                    Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                    Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

                    Example usage:

                    -
                    // Works on both iOS and Android
+
                    // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.5/alert/index.html b/docs/0.5/alert/index.html
index 171c307e3ca..97cf1fb40f2 100644
--- a/docs/0.5/alert/index.html
+++ b/docs/0.5/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
                    0.5
                    Edit
                    Alert
                    Use Alert to display an alert dialog.
                    
-
                    This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                    
+
                    This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                    
 
                    Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                    
 
                    On iOS, you can specify any number of buttons.
                    
 
                    On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                    
@@ -25,7 +25,7 @@
 
                    Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                    
 
                    Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                    
 
                    Example usage:
                    
-
                    // Works on both iOS and Android
+
                    // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.5/clipboard.html b/docs/0.5/clipboard.html
index 3d03efa541e..67e752f4f67 100644
--- a/docs/0.5/clipboard.html
+++ b/docs/0.5/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                    0.5
                    Edit
                    Clipboard
                    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                    
+        
                    0.5
                    Edit
                    Clipboard
                    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                    
 
                    Methods
                    
 
                      
 
                    • getString
                      • 
diff --git a/docs/0.5/clipboard/index.html b/docs/0.5/clipboard/index.html
index 3d03efa541e..67e752f4f67 100644
--- a/docs/0.5/clipboard/index.html
+++ b/docs/0.5/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      0.5
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      0.5
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.5/components-and-apis.html b/docs/0.5/components-and-apis.html
index a986ea3d40c..b4cd09e4eaa 100644
--- a/docs/0.5/components-and-apis.html
+++ b/docs/0.5/components-and-apis.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.5/components-and-apis/index.html b/docs/0.5/components-and-apis/index.html
index a986ea3d40c..b4cd09e4eaa 100644
--- a/docs/0.5/components-and-apis/index.html
+++ b/docs/0.5/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.5/getting-started.html b/docs/0.5/getting-started.html
index 37782ba5542..e561d7addb9 100644
--- a/docs/0.5/getting-started.html
+++ b/docs/0.5/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.5/getting-started/index.html b/docs/0.5/getting-started/index.html
index 37782ba5542..e561d7addb9 100644
--- a/docs/0.5/getting-started/index.html
+++ b/docs/0.5/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.5/images.html b/docs/0.5/images.html
index b5c13c19cea..d191863b9c8 100644
--- a/docs/0.5/images.html
+++ b/docs/0.5/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.5/images/index.html b/docs/0.5/images/index.html
index b5c13c19cea..d191863b9c8 100644
--- a/docs/0.5/images/index.html
+++ b/docs/0.5/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.5/navigation.html b/docs/0.5/navigation.html
index 302aeb01639..f7ed95288aa 100644
--- a/docs/0.5/navigation.html
+++ b/docs/0.5/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.5/navigation/index.html b/docs/0.5/navigation/index.html
index 302aeb01639..f7ed95288aa 100644
--- a/docs/0.5/navigation/index.html
+++ b/docs/0.5/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.5/navigator.html b/docs/0.5/navigator.html
index 6b5aa4a480f..57594486e7c 100644
--- a/docs/0.5/navigator.html
+++ b/docs/0.5/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                        Edit
                        Navigator
                        Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                        
+        
                        Edit
                        Navigator
                        Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                        
 
                        To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                        
 
                        import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.5/navigator/index.html b/docs/0.5/navigator/index.html
index 6b5aa4a480f..57594486e7c 100644
--- a/docs/0.5/navigator/index.html
+++ b/docs/0.5/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                        Edit
                        Navigator
                        Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                        
+        
                        Edit
                        Navigator
                        Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                        
 
                        To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                        
 
                        import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.5/picker.html b/docs/0.5/picker.html
index 0cec395fc55..90082dba75a 100644
--- a/docs/0.5/picker.html
+++ b/docs/0.5/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        0.5
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        0.5
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.5/picker/index.html b/docs/0.5/picker/index.html
index 0cec395fc55..90082dba75a 100644
--- a/docs/0.5/picker/index.html
+++ b/docs/0.5/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        0.5
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        0.5
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.5/platform-specific-code.html b/docs/0.5/platform-specific-code.html
index 7861dd4f74b..bd02099cbca 100644
--- a/docs/0.5/platform-specific-code.html
+++ b/docs/0.5/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.5/platform-specific-code/index.html b/docs/0.5/platform-specific-code/index.html
index 7861dd4f74b..bd02099cbca 100644
--- a/docs/0.5/platform-specific-code/index.html
+++ b/docs/0.5/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.50/accessibility.html b/docs/0.50/accessibility.html
index c655d84ba66..7e9cef4502e 100644
--- a/docs/0.50/accessibility.html
+++ b/docs/0.50/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                        Edit
                        Accessibility
                        Native App Accessibility (iOS and Android)
                        
-
                        Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
+        
                        Edit
                        Accessibility
                        Native App Accessibility (Android and iOS)
                        
+
                        Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
 
                        In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                        
 
                        Making Apps Accessible
                        
 
                        Accessibility properties
                        
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                        
-
                        ← AnimationsImproving User Experience →
                        Edit
                        Accessibility
                        Native App Accessibility (iOS and Android)
                        
-
                        Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
+        
                        Edit
                        Accessibility
                        Native App Accessibility (Android and iOS)
                        
+
                        Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
 
                        In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                        
 
                        Making Apps Accessible
                        
 
                        Accessibility properties
                        
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                        
-
                        ← AnimationsImproving User Experience →
                        Edit
                        Alert
                        Launches an alert dialog with the specified title and message.
                        
 
                        Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
                        
-
                        This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                        
+
                        This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                        
 
                        iOS
                        
 
                        On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.
                        
 
                        Android
                        
@@ -83,7 +83,7 @@
 
                        By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                        
 
                        Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }
                        
 
                        Example usage:
                        
-
                        // Works on both iOS and Android
+
                        // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.50/alert/index.html b/docs/0.50/alert/index.html
index 584cd1cd813..e74a39f49b2 100644
--- a/docs/0.50/alert/index.html
+++ b/docs/0.50/alert/index.html
@@ -70,7 +70,7 @@
             });
         
                        Edit
                        Alert
                        Launches an alert dialog with the specified title and message.
                        
 
                        Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
                        
-
                        This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                        
+
                        This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                        
 
                        iOS
                        
 
                        On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.
                        
 
                        Android
                        
@@ -83,7 +83,7 @@
 
                        By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                        
 
                        Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }
                        
 
                        Example usage:
                        
-
                        // Works on both iOS and Android
+
                        // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.50/clipboard.html b/docs/0.50/clipboard.html
index 49e8c48b1dd..06d7687d695 100644
--- a/docs/0.50/clipboard.html
+++ b/docs/0.50/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                        Edit
                        Clipboard
                        Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                        
+        
                        Edit
                        Clipboard
                        Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                        
 
                        Methods
                        
 
                          
 
                        • getString
                          • 
diff --git a/docs/0.50/clipboard/index.html b/docs/0.50/clipboard/index.html
index 49e8c48b1dd..06d7687d695 100644
--- a/docs/0.50/clipboard/index.html
+++ b/docs/0.50/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                        Edit
                        Clipboard
                        Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                        
+        
                        Edit
                        Clipboard
                        Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                        
 
                        Methods
                        
 
                          
 
                        • getString
                          • 
diff --git a/docs/0.50/components-and-apis.html b/docs/0.50/components-and-apis.html
index 97d7169cfb9..373433e9720 100644
--- a/docs/0.50/components-and-apis.html
+++ b/docs/0.50/components-and-apis.html
@@ -130,7 +130,7 @@
   
                          
     
       
                          Picker
                          
-      
                          Renders the native picker component on iOS and Android.
                          
+      
                          Renders the native picker component on Android and iOS.
                          
                               
   
                          
   
                          
@@ -290,7 +290,7 @@
   
                          
     
       
                          Clipboard
                          
-      
                          Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                          
+      
                          Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                          
                               
   
                          
   
                          
diff --git a/docs/0.50/components-and-apis/index.html b/docs/0.50/components-and-apis/index.html
index 97d7169cfb9..373433e9720 100644
--- a/docs/0.50/components-and-apis/index.html
+++ b/docs/0.50/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                          
     
       
                          Picker
                          
-      
                          Renders the native picker component on iOS and Android.
                          
+      
                          Renders the native picker component on Android and iOS.
                          
                               
   
                          
   
                          
@@ -290,7 +290,7 @@
   
                          
     
       
                          Clipboard
                          
-      
                          Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                          
+      
                          Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                          
                               
   
                          
   
                          
diff --git a/docs/0.50/getting-started.html b/docs/0.50/getting-started.html
index 1e545356657..efa17a86829 100644
--- a/docs/0.50/getting-started.html
+++ b/docs/0.50/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                          If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                          
 
                          
 
                          Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                          
-
                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                          
+
                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                          
 
                          
   Development OS:
   
diff --git a/docs/0.50/getting-started/index.html b/docs/0.50/getting-started/index.html
index 1e545356657..efa17a86829 100644
--- a/docs/0.50/getting-started/index.html
+++ b/docs/0.50/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                          If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                          
 
                          
 
                          Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                          
-
                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                          
+
                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                          
 
                          
   Development OS:
   
diff --git a/docs/0.50/images.html b/docs/0.50/images.html
index 6735d0f07e6..fe3fef3dab8 100644
--- a/docs/0.50/images.html
+++ b/docs/0.50/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                          Edit
                          Images
                          Static Image Resources
                          
-
                          React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                          
+
                          React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                          
 
                          <Image source={require('./my-icon.png')} />
 
                          
 
                          The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                          
@@ -88,7 +88,7 @@
 
                          On Windows, you might need to restart the packager if you add new images to your project.
                          
 
                          Here are some benefits that you get:
                          
 
                            
-
                          1. Same system on iOS and Android.
                            2. 
+
                          2. Same system on Android and iOS.
                            3. 
 
                          3. Images live in the same folder as your JavaScript code. Components are self-contained.
                            4. 
 
                          4. No global namespace, i.e. you don't have to worry about name collisions.
                            5. 
 
                          5. Only the images that are actually used will be packaged into your app.
                            6. 
diff --git a/docs/0.50/images/index.html b/docs/0.50/images/index.html
index 6735d0f07e6..fe3fef3dab8 100644
--- a/docs/0.50/images/index.html
+++ b/docs/0.50/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                          Edit
                          Images
                          Static Image Resources
                          
-
                          React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                          
+
                          React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                          
 
                          <Image source={require('./my-icon.png')} />
 
                          
 
                          The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                          
@@ -88,7 +88,7 @@
 
                          On Windows, you might need to restart the packager if you add new images to your project.
                          
 
                          Here are some benefits that you get:
                          
 
                            
-
                          1. Same system on iOS and Android.
                            2. 
+
                          2. Same system on Android and iOS.
                            3. 
 
                          3. Images live in the same folder as your JavaScript code. Components are self-contained.
                            4. 
 
                          4. No global namespace, i.e. you don't have to worry about name collisions.
                            5. 
 
                          5. Only the images that are actually used will be packaged into your app.
                            6. 
diff --git a/docs/0.50/navigation.html b/docs/0.50/navigation.html
index 71f5b48fc09..0912999fea5 100644
--- a/docs/0.50/navigation.html
+++ b/docs/0.50/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                          Edit
                          Navigating Between Screens
                          Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                          
-
                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                          
-
                          If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                          
+
                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                          
+
                          If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                          
 
                          React Navigation
                          
 
                          The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                          
 
                          The first step is to install in your project:
                          
diff --git a/docs/0.50/navigation/index.html b/docs/0.50/navigation/index.html
index 71f5b48fc09..0912999fea5 100644
--- a/docs/0.50/navigation/index.html
+++ b/docs/0.50/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                          Edit
                          Navigating Between Screens
                          Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                          
-
                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                          
-
                          If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                          
+
                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                          
+
                          If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                          
 
                          React Navigation
                          
 
                          The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                          
 
                          The first step is to install in your project:
                          
diff --git a/docs/0.50/picker.html b/docs/0.50/picker.html
index 8f526aac933..2d18a807504 100644
--- a/docs/0.50/picker.html
+++ b/docs/0.50/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                          Edit
                          Picker
                          Renders the native picker component on iOS and Android. Example:
                          
+        
                          Edit
                          Picker
                          Renders the native picker component on Android and iOS. Example:
                          
 
                          <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.50/picker/index.html b/docs/0.50/picker/index.html
index 8f526aac933..2d18a807504 100644
--- a/docs/0.50/picker/index.html
+++ b/docs/0.50/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                          Edit
                          Picker
                          Renders the native picker component on iOS and Android. Example:
                          
+        
                          Edit
                          Picker
                          Renders the native picker component on Android and iOS. Example:
                          
 
                          <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.50/platform-specific-code.html b/docs/0.50/platform-specific-code.html
index 90e9c21f059..d7af45fc1fb 100644
--- a/docs/0.50/platform-specific-code.html
+++ b/docs/0.50/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                          Edit
                          Platform Specific Code
                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                          
+        
                          Edit
                          Platform Specific Code
                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                          
 
                          React Native provides two ways to organize your code and separate it by platform:
                          
 
                            
 
                          • Using the Platform module.
                            • 
diff --git a/docs/0.50/platform-specific-code/index.html b/docs/0.50/platform-specific-code/index.html
index 90e9c21f059..d7af45fc1fb 100644
--- a/docs/0.50/platform-specific-code/index.html
+++ b/docs/0.50/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                          Edit
                          Platform Specific Code
                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                          
+        
                          Edit
                          Platform Specific Code
                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                          
 
                          React Native provides two ways to organize your code and separate it by platform:
                          
 
                            
 
                          • Using the Platform module.
                            • 
diff --git a/docs/0.50/text.html b/docs/0.50/text.html
index 7c436402c3d..13653adaee2 100644
--- a/docs/0.50/text.html
+++ b/docs/0.50/text.html
@@ -124,7 +124,7 @@ AppRegistry.registerComponent('TextInANest', ()
           width: 100%;
         "
       >
                          Nested text
                          
-
                          Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                          
+
                          Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                          
 
                          Nested text
                          
-
                          Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                          
+
                          Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                          
 
                          Edit
                          Accessibility
                          Native App Accessibility (iOS and Android)
                          
-
                          Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                          
+        
                          Edit
                          Accessibility
                          Native App Accessibility (Android and iOS)
                          
+
                          Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                          
 
                          In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                          
 
                          Making Apps Accessible
                          
 
                          Accessibility properties
                          
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                    
-
                    ← AnimationsImproving User Experience →
                    Edit

                    Accessibility

                    Native App Accessibility (iOS and Android)

                    -

                    Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                    +
                    Edit

                    Accessibility

                    Native App Accessibility (Android and iOS)

                    +

                    Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                    In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

                    Making Apps Accessible

                    Accessibility properties

                    @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService                     -
                    ← AnimationsImproving User Experience →
                    Edit

                    Alert

                    Launches an alert dialog with the specified title and message.

                    Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

                    -

                    This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                    +

                    This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                    iOS

                    On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

                    Android

                    @@ -83,7 +83,7 @@

                    By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                    Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                    Example usage:

                    -
                    // Works on both iOS and Android
+
                    // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.51/alert/index.html b/docs/0.51/alert/index.html
index 68be94e5f1a..241b679c2da 100644
--- a/docs/0.51/alert/index.html
+++ b/docs/0.51/alert/index.html
@@ -70,7 +70,7 @@
             });
                    Edit

                    Alert

                    Launches an alert dialog with the specified title and message.

                    Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

                    -

                    This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                    +

                    This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                    iOS

                    On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.

                    Android

                    @@ -83,7 +83,7 @@

                    By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                    Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                    Example usage:

                    -
                    // Works on both iOS and Android
+
                    // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.51/clipboard.html b/docs/0.51/clipboard.html
index 442d1dde76e..bf00e8fc84e 100644
--- a/docs/0.51/clipboard.html
+++ b/docs/0.51/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                    Edit

                    Clipboard

                    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

                    +
                    Edit

                    Clipboard

                    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

                    Methods

                    • getString
                      • diff --git a/docs/0.51/clipboard/index.html b/docs/0.51/clipboard/index.html index 442d1dde76e..bf00e8fc84e 100644 --- a/docs/0.51/clipboard/index.html +++ b/docs/0.51/clipboard/index.html @@ -1,4 +1,4 @@ -Clipboard · React Native
                    Edit

                    Clipboard

                    Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android

                    +
                    Edit

                    Clipboard

                    Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS

                    Methods

                    • getString
                      • diff --git a/docs/0.51/components-and-apis.html b/docs/0.51/components-and-apis.html index d6bccadac7d..f9d76706826 100644 --- a/docs/0.51/components-and-apis.html +++ b/docs/0.51/components-and-apis.html @@ -130,7 +130,7 @@

                      Picker

                      -

                      Renders the native picker component on iOS and Android.

                      +

                      Renders the native picker component on Android and iOS.
                      @@ -290,7 +290,7 @@

                      Clipboard

                      -

                      Provides an interface for setting and getting content from the clipboard on both iOS and Android.

                      +

                      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                      diff --git a/docs/0.51/components-and-apis/index.html b/docs/0.51/components-and-apis/index.html index d6bccadac7d..f9d76706826 100644 --- a/docs/0.51/components-and-apis/index.html +++ b/docs/0.51/components-and-apis/index.html @@ -130,7 +130,7 @@

                      Picker

                      -

                      Renders the native picker component on iOS and Android.

                      +

                      Renders the native picker component on Android and iOS.
                      @@ -290,7 +290,7 @@

                      Clipboard

                      -

                      Provides an interface for setting and getting content from the clipboard on both iOS and Android.

                      +

                      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                      diff --git a/docs/0.51/getting-started.html b/docs/0.51/getting-started.html index b8381c028d1..0f099985a3b 100644 --- a/docs/0.51/getting-started.html +++ b/docs/0.51/getting-started.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

                      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

                      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

                      -

                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

                      +

                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

                      Development OS: diff --git a/docs/0.51/getting-started/index.html b/docs/0.51/getting-started/index.html index b8381c028d1..0f099985a3b 100644 --- a/docs/0.51/getting-started/index.html +++ b/docs/0.51/getting-started/index.html @@ -118,7 +118,7 @@ npm start # you can also use: expo start

                      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.

                      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.

                      -

                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.

                      +

                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.

                      Development OS: diff --git a/docs/0.51/images.html b/docs/0.51/images.html index 224fdf76704..bea2df9dc88 100644 --- a/docs/0.51/images.html +++ b/docs/0.51/images.html @@ -69,7 +69,7 @@ } });
                      Edit

                      Images

                      Static Image Resources

                      -

                      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

                      +

                      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

                      <Image source={require('./my-icon.png')} />

                      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

                      @@ -88,7 +88,7 @@

                      On Windows, you might need to restart the packager if you add new images to your project.

                      Here are some benefits that you get:

                        -
                      1. Same system on iOS and Android.
                        2. +
                      2. Same system on Android and iOS.
                      3. Images live in the same folder as your JavaScript code. Components are self-contained.
                      4. No global namespace, i.e. you don't have to worry about name collisions.
                      5. Only the images that are actually used will be packaged into your app.
                        6. diff --git a/docs/0.51/images/index.html b/docs/0.51/images/index.html index 224fdf76704..bea2df9dc88 100644 --- a/docs/0.51/images/index.html +++ b/docs/0.51/images/index.html @@ -69,7 +69,7 @@ } });
                      Edit

                      Images

                      Static Image Resources

                      -

                      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

                      +

                      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:

                      <Image source={require('./my-icon.png')} />

                      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.

                      @@ -88,7 +88,7 @@

                      On Windows, you might need to restart the packager if you add new images to your project.

                      Here are some benefits that you get:

                        -
                      1. Same system on iOS and Android.
                        2. +
                      2. Same system on Android and iOS.
                      3. Images live in the same folder as your JavaScript code. Components are self-contained.
                      4. No global namespace, i.e. you don't have to worry about name collisions.
                      5. Only the images that are actually used will be packaged into your app.
                        6. diff --git a/docs/0.51/navigation.html b/docs/0.51/navigation.html index b453deebeca..fa1d75d8c17 100644 --- a/docs/0.51/navigation.html +++ b/docs/0.51/navigation.html @@ -69,8 +69,8 @@ } });
                      Edit

                      Navigating Between Screens

                      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

                      -

                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

                      -

                      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

                      +

                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

                      +

                      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

                      React Navigation

                      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

                      The first step is to install in your project:

                      diff --git a/docs/0.51/navigation/index.html b/docs/0.51/navigation/index.html index b453deebeca..fa1d75d8c17 100644 --- a/docs/0.51/navigation/index.html +++ b/docs/0.51/navigation/index.html @@ -69,8 +69,8 @@ } });
                      Edit

                      Navigating Between Screens

                      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.

                      -

                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.

                      -

                      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

                      +

                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.

                      +

                      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.

                      React Navigation

                      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.

                      The first step is to install in your project:

                      diff --git a/docs/0.51/picker.html b/docs/0.51/picker.html index 707aa46b184..f6507031de1 100644 --- a/docs/0.51/picker.html +++ b/docs/0.51/picker.html @@ -1,4 +1,4 @@ -Picker · React Native
                      Edit

                      Picker

                      Renders the native picker component on iOS and Android. Example:

                      +
                      Edit

                      Picker

                      Renders the native picker component on Android and iOS. Example:

                      <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.51/picker/index.html b/docs/0.51/picker/index.html
index 707aa46b184..f6507031de1 100644
--- a/docs/0.51/picker/index.html
+++ b/docs/0.51/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                      Edit

                      Picker

                      Renders the native picker component on iOS and Android. Example:

                      +
                      Edit

                      Picker

                      Renders the native picker component on Android and iOS. Example:

                      <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.51/platform-specific-code.html b/docs/0.51/platform-specific-code.html
index af473b2a749..25e22d26a06 100644
--- a/docs/0.51/platform-specific-code.html
+++ b/docs/0.51/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                      Edit

                      Platform Specific Code

                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

                      +
                      Edit

                      Platform Specific Code

                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

                      React Native provides two ways to organize your code and separate it by platform:

                      • Using the Platform module.
                        • diff --git a/docs/0.51/platform-specific-code/index.html b/docs/0.51/platform-specific-code/index.html index af473b2a749..25e22d26a06 100644 --- a/docs/0.51/platform-specific-code/index.html +++ b/docs/0.51/platform-specific-code/index.html @@ -1,4 +1,4 @@ -Platform Specific Code · React Native
                      Edit

                      Platform Specific Code

                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.

                      +
                      Edit

                      Platform Specific Code

                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.

                      React Native provides two ways to organize your code and separate it by platform:

                      • Using the Platform module.
                        • diff --git a/docs/0.51/text.html b/docs/0.51/text.html index a9d3060e32a..8f8c259a800 100644 --- a/docs/0.51/text.html +++ b/docs/0.51/text.html @@ -124,7 +124,7 @@ AppRegistry.registerComponent('TextInANest', () width: 100%; " >

                      Nested text

                      -

                      Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.

                      +

                      Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.

                      Nested text

                      -

                      Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.

                      +

                      Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.

                      Edit

                      Accessibility

                      Native App Accessibility (iOS and Android)

                      -

                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                      +
                      Edit

                      Accessibility

                      Native App Accessibility (Android and iOS)

                      +

                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

                      Making Apps Accessible

                      Accessibility properties

                      @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService                       -
                      ← AnimationsImproving User Experience →
                      Edit

                      Accessibility

                      Native App Accessibility (iOS and Android)

                      -

                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                      +
                      Edit

                      Accessibility

                      Native App Accessibility (Android and iOS)

                      +

                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.

                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.

                      Making Apps Accessible

                      Accessibility properties

                      @@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi # enable adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService -
                      ← AnimationsImproving User Experience →
                      Edit

                      Alert

                      Launches an alert dialog with the specified title and message.

                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

                      -

                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                      +

                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                      Example

                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.52/alert/index.html b/docs/0.52/alert/index.html
index 214a8281eca..ddcc0164db8 100644
--- a/docs/0.52/alert/index.html
+++ b/docs/0.52/alert/index.html
@@ -70,7 +70,7 @@
             });
         
                      Edit
                      Alert
                      Launches an alert dialog with the specified title and message.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
 
                      Example
                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.52/clipboard.html b/docs/0.52/clipboard.html
index 42984d550ef..2b1f471e534 100644
--- a/docs/0.52/clipboard.html
+++ b/docs/0.52/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.52/clipboard/index.html b/docs/0.52/clipboard/index.html
index 42984d550ef..2b1f471e534 100644
--- a/docs/0.52/clipboard/index.html
+++ b/docs/0.52/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.52/components-and-apis.html b/docs/0.52/components-and-apis.html
index 1f3d3b2a2b3..7ebb2b83fdc 100644
--- a/docs/0.52/components-and-apis.html
+++ b/docs/0.52/components-and-apis.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.52/components-and-apis/index.html b/docs/0.52/components-and-apis/index.html
index 1f3d3b2a2b3..7ebb2b83fdc 100644
--- a/docs/0.52/components-and-apis/index.html
+++ b/docs/0.52/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.52/getting-started.html b/docs/0.52/getting-started.html
index 60aa263acdd..26d3b548a63 100644
--- a/docs/0.52/getting-started.html
+++ b/docs/0.52/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.52/getting-started/index.html b/docs/0.52/getting-started/index.html
index 60aa263acdd..26d3b548a63 100644
--- a/docs/0.52/getting-started/index.html
+++ b/docs/0.52/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.52/images.html b/docs/0.52/images.html
index 3d27e09ee77..0cacc075035 100644
--- a/docs/0.52/images.html
+++ b/docs/0.52/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.52/images/index.html b/docs/0.52/images/index.html
index 3d27e09ee77..0cacc075035 100644
--- a/docs/0.52/images/index.html
+++ b/docs/0.52/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.52/navigation.html b/docs/0.52/navigation.html
index 8918d42fce1..497fbace580 100644
--- a/docs/0.52/navigation.html
+++ b/docs/0.52/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.52/navigation/index.html b/docs/0.52/navigation/index.html
index 8918d42fce1..497fbace580 100644
--- a/docs/0.52/navigation/index.html
+++ b/docs/0.52/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.52/picker.html b/docs/0.52/picker.html
index 30c8ad424be..2cb1f9e068b 100644
--- a/docs/0.52/picker.html
+++ b/docs/0.52/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.52/picker/index.html b/docs/0.52/picker/index.html
index 30c8ad424be..2cb1f9e068b 100644
--- a/docs/0.52/picker/index.html
+++ b/docs/0.52/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.52/platform-specific-code.html b/docs/0.52/platform-specific-code.html
index 937d3591406..3d2286e3ac4 100644
--- a/docs/0.52/platform-specific-code.html
+++ b/docs/0.52/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.52/platform-specific-code/index.html b/docs/0.52/platform-specific-code/index.html
index 937d3591406..3d2286e3ac4 100644
--- a/docs/0.52/platform-specific-code/index.html
+++ b/docs/0.52/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.52/text.html b/docs/0.52/text.html
index b70329327d0..149ceb3a69d 100644
--- a/docs/0.52/text.html
+++ b/docs/0.52/text.html
@@ -124,7 +124,7 @@ AppRegistry.registerComponent('TextInANest', ()
           width: 100%;
         "
       >
                        Nested text
                        
-
                        Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
+
                        Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
 
                        Nested text
                        
-
                        Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
+
                        Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
 
                        Edit
                        Accessibility
                        Native App Accessibility (iOS and Android)
                        
-
                        Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
+        
                        Edit
                        Accessibility
                        Native App Accessibility (Android and iOS)
                        
+
                        Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
 
                        In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                        
 
                        Making Apps Accessible
                        
 
                        Accessibility properties
                        
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                      
-
                      ← AnimationsImproving User Experience →
                      Edit
                      Accessibility
                      Native App Accessibility (iOS and Android)
                      
-
                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
+        
                      Edit
                      Accessibility
                      Native App Accessibility (Android and iOS)
                      
+
                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
 
                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                      
 
                      Making Apps Accessible
                      
 
                      Accessibility properties
                      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
                      -
                      ← AnimationsImproving User Experience →
                      Edit

                      Alert

                      Launches an alert dialog with the specified title and message.

                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

                      -

                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                      +

                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                      Example

                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.53/alert/index.html b/docs/0.53/alert/index.html
index ee4de45a140..d8d5d5abfd0 100644
--- a/docs/0.53/alert/index.html
+++ b/docs/0.53/alert/index.html
@@ -70,7 +70,7 @@
             });
         
                      Edit
                      Alert
                      Launches an alert dialog with the specified title and message.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
 
                      Example
                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.53/clipboard.html b/docs/0.53/clipboard.html
index d454548c47f..4e81dc782cf 100644
--- a/docs/0.53/clipboard.html
+++ b/docs/0.53/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.53/clipboard/index.html b/docs/0.53/clipboard/index.html
index d454548c47f..4e81dc782cf 100644
--- a/docs/0.53/clipboard/index.html
+++ b/docs/0.53/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.53/components-and-apis.html b/docs/0.53/components-and-apis.html
index 6a90ff4cc9d..d777f33a24f 100644
--- a/docs/0.53/components-and-apis.html
+++ b/docs/0.53/components-and-apis.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.53/components-and-apis/index.html b/docs/0.53/components-and-apis/index.html
index 6a90ff4cc9d..d777f33a24f 100644
--- a/docs/0.53/components-and-apis/index.html
+++ b/docs/0.53/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.53/getting-started.html b/docs/0.53/getting-started.html
index ab8a07daba3..729062749ea 100644
--- a/docs/0.53/getting-started.html
+++ b/docs/0.53/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.53/getting-started/index.html b/docs/0.53/getting-started/index.html
index ab8a07daba3..729062749ea 100644
--- a/docs/0.53/getting-started/index.html
+++ b/docs/0.53/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.53/images.html b/docs/0.53/images.html
index d6bbd0d3a8d..d2b2cc43fa0 100644
--- a/docs/0.53/images.html
+++ b/docs/0.53/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.53/images/index.html b/docs/0.53/images/index.html
index d6bbd0d3a8d..d2b2cc43fa0 100644
--- a/docs/0.53/images/index.html
+++ b/docs/0.53/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.53/navigation.html b/docs/0.53/navigation.html
index 23b106303aa..fc9bf1c6493 100644
--- a/docs/0.53/navigation.html
+++ b/docs/0.53/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.53/navigation/index.html b/docs/0.53/navigation/index.html
index 23b106303aa..fc9bf1c6493 100644
--- a/docs/0.53/navigation/index.html
+++ b/docs/0.53/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.53/picker.html b/docs/0.53/picker.html
index 8304b8a4163..850a9334d64 100644
--- a/docs/0.53/picker.html
+++ b/docs/0.53/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.53/picker/index.html b/docs/0.53/picker/index.html
index 8304b8a4163..850a9334d64 100644
--- a/docs/0.53/picker/index.html
+++ b/docs/0.53/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.53/platform-specific-code.html b/docs/0.53/platform-specific-code.html
index 209a7340999..b66a95b39af 100644
--- a/docs/0.53/platform-specific-code.html
+++ b/docs/0.53/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.53/platform-specific-code/index.html b/docs/0.53/platform-specific-code/index.html
index 209a7340999..b66a95b39af 100644
--- a/docs/0.53/platform-specific-code/index.html
+++ b/docs/0.53/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.53/text.html b/docs/0.53/text.html
index ea9248d3cb6..8b25010f545 100644
--- a/docs/0.53/text.html
+++ b/docs/0.53/text.html
@@ -124,7 +124,7 @@ AppRegistry.registerComponent('TextInANest', ()
           width: 100%;
         "
       >
                        Nested text
                        
-
                        Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
+
                        Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
 
                        Nested text
                        
-
                        Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
+
                        Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
 
                        Edit
                        Accessibility
                        Native App Accessibility (iOS and Android)
                        
-
                        Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
+        
                        Edit
                        Accessibility
                        Native App Accessibility (Android and iOS)
                        
+
                        Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
 
                        In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                        
 
                        Making Apps Accessible
                        
 
                        Accessibility properties
                        
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                      
-
                      ← AnimationsImproving User Experience →
                      Edit
                      Accessibility
                      Native App Accessibility (iOS and Android)
                      
-
                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
+        
                      Edit
                      Accessibility
                      Native App Accessibility (Android and iOS)
                      
+
                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
 
                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                      
 
                      Making Apps Accessible
                      
 
                      Accessibility properties
                      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
                      -
                      ← AnimationsImproving User Experience →
                      Edit

                      Alert

                      Launches an alert dialog with the specified title and message.

                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

                      -

                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                      +

                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                      Example

                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.54/alert/index.html b/docs/0.54/alert/index.html
index 18b087bed97..b36236bfec8 100644
--- a/docs/0.54/alert/index.html
+++ b/docs/0.54/alert/index.html
@@ -70,7 +70,7 @@
             });
         
                      Edit
                      Alert
                      Launches an alert dialog with the specified title and message.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
 
                      Example
                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.54/clipboard.html b/docs/0.54/clipboard.html
index dd208d2d59e..90c733bd570 100644
--- a/docs/0.54/clipboard.html
+++ b/docs/0.54/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.54/clipboard/index.html b/docs/0.54/clipboard/index.html
index dd208d2d59e..90c733bd570 100644
--- a/docs/0.54/clipboard/index.html
+++ b/docs/0.54/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.54/components-and-apis.html b/docs/0.54/components-and-apis.html
index ae10e7d054a..72159142aae 100644
--- a/docs/0.54/components-and-apis.html
+++ b/docs/0.54/components-and-apis.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.54/components-and-apis/index.html b/docs/0.54/components-and-apis/index.html
index ae10e7d054a..72159142aae 100644
--- a/docs/0.54/components-and-apis/index.html
+++ b/docs/0.54/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.54/getting-started.html b/docs/0.54/getting-started.html
index ef6663a01ca..ef8961237c4 100644
--- a/docs/0.54/getting-started.html
+++ b/docs/0.54/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.54/getting-started/index.html b/docs/0.54/getting-started/index.html
index ef6663a01ca..ef8961237c4 100644
--- a/docs/0.54/getting-started/index.html
+++ b/docs/0.54/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.54/images.html b/docs/0.54/images.html
index dedce7f7ba1..a8cdcaaa5c3 100644
--- a/docs/0.54/images.html
+++ b/docs/0.54/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.54/images/index.html b/docs/0.54/images/index.html
index dedce7f7ba1..a8cdcaaa5c3 100644
--- a/docs/0.54/images/index.html
+++ b/docs/0.54/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.54/navigation.html b/docs/0.54/navigation.html
index 339b6f041d2..5e658fa5c58 100644
--- a/docs/0.54/navigation.html
+++ b/docs/0.54/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.54/navigation/index.html b/docs/0.54/navigation/index.html
index 339b6f041d2..5e658fa5c58 100644
--- a/docs/0.54/navigation/index.html
+++ b/docs/0.54/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.54/picker.html b/docs/0.54/picker.html
index 46576cb6ab3..1f8e284c680 100644
--- a/docs/0.54/picker.html
+++ b/docs/0.54/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.54/picker/index.html b/docs/0.54/picker/index.html
index 46576cb6ab3..1f8e284c680 100644
--- a/docs/0.54/picker/index.html
+++ b/docs/0.54/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.54/platform-specific-code.html b/docs/0.54/platform-specific-code.html
index f414e2d5f64..9d4692fe658 100644
--- a/docs/0.54/platform-specific-code.html
+++ b/docs/0.54/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.54/platform-specific-code/index.html b/docs/0.54/platform-specific-code/index.html
index f414e2d5f64..9d4692fe658 100644
--- a/docs/0.54/platform-specific-code/index.html
+++ b/docs/0.54/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.54/text.html b/docs/0.54/text.html
index 23bb4a867c4..b9941a50e66 100644
--- a/docs/0.54/text.html
+++ b/docs/0.54/text.html
@@ -124,7 +124,7 @@ AppRegistry.registerComponent('TextInANest', ()
           width: 100%;
         "
       >
                        Nested text
                        
-
                        Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
+
                        Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
 
                        Nested text
                        
-
                        Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
+
                        Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
 
                        Edit
                        Accessibility
                        Native App Accessibility (iOS and Android)
                        
-
                        Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
+        
                        Edit
                        Accessibility
                        Native App Accessibility (Android and iOS)
                        
+
                        Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
 
                        In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                        
 
                        Making Apps Accessible
                        
 
                        Accessibility properties
                        
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                      
-
                      ← AnimationsImproving User Experience →
                      Edit
                      Accessibility
                      Native App Accessibility (iOS and Android)
                      
-
                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
+        
                      Edit
                      Accessibility
                      Native App Accessibility (Android and iOS)
                      
+
                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
 
                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                      
 
                      Making Apps Accessible
                      
 
                      Accessibility properties
                      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
                      -
                      ← AnimationsImproving User Experience →
                      Edit

                      Alert

                      Launches an alert dialog with the specified title and message.

                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

                      -

                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                      +

                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                      Example

                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.55/alert/index.html b/docs/0.55/alert/index.html
index 413eca810a9..a434d46e9dd 100644
--- a/docs/0.55/alert/index.html
+++ b/docs/0.55/alert/index.html
@@ -70,7 +70,7 @@
             });
         
                      Edit
                      Alert
                      Launches an alert dialog with the specified title and message.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
 
                      Example
                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.55/clipboard.html b/docs/0.55/clipboard.html
index 1f57930662f..24b37ce2661 100644
--- a/docs/0.55/clipboard.html
+++ b/docs/0.55/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.55/clipboard/index.html b/docs/0.55/clipboard/index.html
index 1f57930662f..24b37ce2661 100644
--- a/docs/0.55/clipboard/index.html
+++ b/docs/0.55/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.55/components-and-apis.html b/docs/0.55/components-and-apis.html
index 71a9b75685e..a4b540c6dea 100644
--- a/docs/0.55/components-and-apis.html
+++ b/docs/0.55/components-and-apis.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.55/components-and-apis/index.html b/docs/0.55/components-and-apis/index.html
index 71a9b75685e..a4b540c6dea 100644
--- a/docs/0.55/components-and-apis/index.html
+++ b/docs/0.55/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.55/getting-started.html b/docs/0.55/getting-started.html
index 2468e967768..02bc623cbae 100644
--- a/docs/0.55/getting-started.html
+++ b/docs/0.55/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.55/getting-started/index.html b/docs/0.55/getting-started/index.html
index 2468e967768..02bc623cbae 100644
--- a/docs/0.55/getting-started/index.html
+++ b/docs/0.55/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.55/images.html b/docs/0.55/images.html
index 470c5544a94..40223ed5921 100644
--- a/docs/0.55/images.html
+++ b/docs/0.55/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.55/images/index.html b/docs/0.55/images/index.html
index 470c5544a94..40223ed5921 100644
--- a/docs/0.55/images/index.html
+++ b/docs/0.55/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.55/navigation.html b/docs/0.55/navigation.html
index 6698e621b9a..386557b0ebd 100644
--- a/docs/0.55/navigation.html
+++ b/docs/0.55/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.55/navigation/index.html b/docs/0.55/navigation/index.html
index 6698e621b9a..386557b0ebd 100644
--- a/docs/0.55/navigation/index.html
+++ b/docs/0.55/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.55/picker.html b/docs/0.55/picker.html
index dc1f4566a31..72684376121 100644
--- a/docs/0.55/picker.html
+++ b/docs/0.55/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   style={{ height: 50, width: 100 }}
diff --git a/docs/0.55/picker/index.html b/docs/0.55/picker/index.html
index dc1f4566a31..72684376121 100644
--- a/docs/0.55/picker/index.html
+++ b/docs/0.55/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   style={{ height: 50, width: 100 }}
diff --git a/docs/0.55/platform-specific-code.html b/docs/0.55/platform-specific-code.html
index 2fa7fd2b9aa..da397980699 100644
--- a/docs/0.55/platform-specific-code.html
+++ b/docs/0.55/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.55/platform-specific-code/index.html b/docs/0.55/platform-specific-code/index.html
index 2fa7fd2b9aa..da397980699 100644
--- a/docs/0.55/platform-specific-code/index.html
+++ b/docs/0.55/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.55/text.html b/docs/0.55/text.html
index 1b31a47e4ea..7313906c3ee 100644
--- a/docs/0.55/text.html
+++ b/docs/0.55/text.html
@@ -124,7 +124,7 @@ AppRegistry.registerComponent('TextInANest', ()
           width: 100%;
         "
       >
                        Nested text
                        
-
                        Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
+
                        Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
 
                        Nested text
                        
-
                        Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
+
                        Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
 
                        Edit
                        Accessibility
                        Native App Accessibility (iOS and Android)
                        
-
                        Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
+        
                        Edit
                        Accessibility
                        Native App Accessibility (Android and iOS)
                        
+
                        Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
 
                        In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                        
 
                        Making Apps Accessible
                        
 
                        Accessibility properties
                        
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                      
-
                      ← AnimationsImproving User Experience →
                      Edit
                      Accessibility
                      Native App Accessibility (iOS and Android)
                      
-
                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
+        
                      Edit
                      Accessibility
                      Native App Accessibility (Android and iOS)
                      
+
                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
 
                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                      
 
                      Making Apps Accessible
                      
 
                      Accessibility properties
                      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
                      -
                      ← AnimationsImproving User Experience →
                      Edit

                      Alert

                      Launches an alert dialog with the specified title and message.

                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

                      -

                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                      +

                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                      Example

                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.56/alert/index.html b/docs/0.56/alert/index.html
index 7c63c2c6ef8..abc53195315 100644
--- a/docs/0.56/alert/index.html
+++ b/docs/0.56/alert/index.html
@@ -70,7 +70,7 @@
             });
         
                      Edit
                      Alert
                      Launches an alert dialog with the specified title and message.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
 
                      Example
                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.56/clipboard.html b/docs/0.56/clipboard.html
index 1244f7ad47a..c84502cf4e1 100644
--- a/docs/0.56/clipboard.html
+++ b/docs/0.56/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.56/clipboard/index.html b/docs/0.56/clipboard/index.html
index 1244f7ad47a..c84502cf4e1 100644
--- a/docs/0.56/clipboard/index.html
+++ b/docs/0.56/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.56/components-and-apis.html b/docs/0.56/components-and-apis.html
index 63d0ba64901..22b8ec30230 100644
--- a/docs/0.56/components-and-apis.html
+++ b/docs/0.56/components-and-apis.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.56/components-and-apis/index.html b/docs/0.56/components-and-apis/index.html
index 63d0ba64901..22b8ec30230 100644
--- a/docs/0.56/components-and-apis/index.html
+++ b/docs/0.56/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.56/getting-started.html b/docs/0.56/getting-started.html
index 55a97d9cf2b..8fddde93d8c 100644
--- a/docs/0.56/getting-started.html
+++ b/docs/0.56/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.56/getting-started/index.html b/docs/0.56/getting-started/index.html
index 55a97d9cf2b..8fddde93d8c 100644
--- a/docs/0.56/getting-started/index.html
+++ b/docs/0.56/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.56/images.html b/docs/0.56/images.html
index a9a4b6bafdb..abfce23e381 100644
--- a/docs/0.56/images.html
+++ b/docs/0.56/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.56/images/index.html b/docs/0.56/images/index.html
index a9a4b6bafdb..abfce23e381 100644
--- a/docs/0.56/images/index.html
+++ b/docs/0.56/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.56/navigation.html b/docs/0.56/navigation.html
index cd3bbcaed50..6c1e5c12875 100644
--- a/docs/0.56/navigation.html
+++ b/docs/0.56/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.56/navigation/index.html b/docs/0.56/navigation/index.html
index cd3bbcaed50..6c1e5c12875 100644
--- a/docs/0.56/navigation/index.html
+++ b/docs/0.56/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.56/picker.html b/docs/0.56/picker.html
index 351786aa8e5..2bb6856da7b 100644
--- a/docs/0.56/picker.html
+++ b/docs/0.56/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   style={{ height: 50, width: 100 }}
diff --git a/docs/0.56/picker/index.html b/docs/0.56/picker/index.html
index 351786aa8e5..2bb6856da7b 100644
--- a/docs/0.56/picker/index.html
+++ b/docs/0.56/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   style={{ height: 50, width: 100 }}
diff --git a/docs/0.56/platform-specific-code.html b/docs/0.56/platform-specific-code.html
index cce4c780b7c..712164a17f8 100644
--- a/docs/0.56/platform-specific-code.html
+++ b/docs/0.56/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.56/platform-specific-code/index.html b/docs/0.56/platform-specific-code/index.html
index cce4c780b7c..712164a17f8 100644
--- a/docs/0.56/platform-specific-code/index.html
+++ b/docs/0.56/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.56/text.html b/docs/0.56/text.html
index 6cf67dd4d67..691b141480e 100644
--- a/docs/0.56/text.html
+++ b/docs/0.56/text.html
@@ -124,7 +124,7 @@ AppRegistry.registerComponent('TextInANest', ()
           width: 100%;
         "
       >
                        Nested text
                        
-
                        Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
+
                        Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
 
                        Nested text
                        
-
                        Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
+
                        Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
 
                        Edit
                        Accessibility
                        Native App Accessibility (iOS and Android)
                        
-
                        Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
+        
                        Edit
                        Accessibility
                        Native App Accessibility (Android and iOS)
                        
+
                        Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
 
                        In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                        
 
                        Making Apps Accessible
                        
 
                        Accessibility properties
                        
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                      
-
                      ← AnimationsImproving User Experience →
                      Edit
                      Accessibility
                      Native App Accessibility (iOS and Android)
                      
-
                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
+        
                      Edit
                      Accessibility
                      Native App Accessibility (Android and iOS)
                      
+
                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
 
                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                      
 
                      Making Apps Accessible
                      
 
                      Accessibility properties
                      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
                      -
                      ← AnimationsImproving User Experience →
                      Edit

                      Alert

                      Launches an alert dialog with the specified title and message.

                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

                      -

                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                      +

                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                      Example

                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.57/alert/index.html b/docs/0.57/alert/index.html
index c21d9d84182..5d1f4abcd25 100644
--- a/docs/0.57/alert/index.html
+++ b/docs/0.57/alert/index.html
@@ -70,7 +70,7 @@
             });
         
                      Edit
                      Alert
                      Launches an alert dialog with the specified title and message.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
 
                      Example
                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.57/clipboard.html b/docs/0.57/clipboard.html
index 83cb2f7472f..a1366245a64 100644
--- a/docs/0.57/clipboard.html
+++ b/docs/0.57/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.57/clipboard/index.html b/docs/0.57/clipboard/index.html
index 83cb2f7472f..a1366245a64 100644
--- a/docs/0.57/clipboard/index.html
+++ b/docs/0.57/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.57/components-and-apis.html b/docs/0.57/components-and-apis.html
index d8a0bbdda67..2220b7380a4 100644
--- a/docs/0.57/components-and-apis.html
+++ b/docs/0.57/components-and-apis.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.57/components-and-apis/index.html b/docs/0.57/components-and-apis/index.html
index d8a0bbdda67..2220b7380a4 100644
--- a/docs/0.57/components-and-apis/index.html
+++ b/docs/0.57/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.57/getting-started.html b/docs/0.57/getting-started.html
index f06b83a79b1..21860ed5f59 100644
--- a/docs/0.57/getting-started.html
+++ b/docs/0.57/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.57/getting-started/index.html b/docs/0.57/getting-started/index.html
index f06b83a79b1..21860ed5f59 100644
--- a/docs/0.57/getting-started/index.html
+++ b/docs/0.57/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.57/images.html b/docs/0.57/images.html
index 5df1e8ae2da..ec6c6ca93c0 100644
--- a/docs/0.57/images.html
+++ b/docs/0.57/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.57/images/index.html b/docs/0.57/images/index.html
index 5df1e8ae2da..ec6c6ca93c0 100644
--- a/docs/0.57/images/index.html
+++ b/docs/0.57/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.57/navigation.html b/docs/0.57/navigation.html
index cdbde15cf1d..098bf8a3dfe 100644
--- a/docs/0.57/navigation.html
+++ b/docs/0.57/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.57/navigation/index.html b/docs/0.57/navigation/index.html
index cdbde15cf1d..098bf8a3dfe 100644
--- a/docs/0.57/navigation/index.html
+++ b/docs/0.57/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.57/picker.html b/docs/0.57/picker.html
index 8aa08923aba..ad5b002ca37 100644
--- a/docs/0.57/picker.html
+++ b/docs/0.57/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   style={{ height: 50, width: 100 }}
diff --git a/docs/0.57/picker/index.html b/docs/0.57/picker/index.html
index 8aa08923aba..ad5b002ca37 100644
--- a/docs/0.57/picker/index.html
+++ b/docs/0.57/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   style={{ height: 50, width: 100 }}
diff --git a/docs/0.57/platform-specific-code.html b/docs/0.57/platform-specific-code.html
index 2bf76f770bf..174424a8fa8 100644
--- a/docs/0.57/platform-specific-code.html
+++ b/docs/0.57/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.57/platform-specific-code/index.html b/docs/0.57/platform-specific-code/index.html
index 2bf76f770bf..174424a8fa8 100644
--- a/docs/0.57/platform-specific-code/index.html
+++ b/docs/0.57/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.57/text.html b/docs/0.57/text.html
index ce727ab3beb..1e04a04a085 100644
--- a/docs/0.57/text.html
+++ b/docs/0.57/text.html
@@ -124,7 +124,7 @@ AppRegistry.registerComponent('TextInANest', ()
           width: 100%;
         "
       >
                        Nested text
                        
-
                        Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
+
                        Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
 
                        Nested text
                        
-
                        Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
+
                        Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
 
                        Edit
                        Accessibility
                        Native App Accessibility (iOS and Android)
                        
-
                        Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
+        
                        Edit
                        Accessibility
                        Native App Accessibility (Android and iOS)
                        
+
                        Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
 
                        In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                        
 
                        Making Apps Accessible
                        
 
                        Accessibility properties
                        
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                      
-
                      ← AnimationsImproving User Experience →
                      Edit
                      Accessibility
                      Native App Accessibility (iOS and Android)
                      
-
                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
+        
                      Edit
                      Accessibility
                      Native App Accessibility (Android and iOS)
                      
+
                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
 
                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                      
 
                      Making Apps Accessible
                      
 
                      Accessibility properties
                      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
                      -
                      ← AnimationsImproving User Experience →
                      Edit

                      Alert

                      Launches an alert dialog with the specified title and message.

                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

                      -

                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                      +

                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                      Example

                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.58/alert/index.html b/docs/0.58/alert/index.html
index def30422112..198e5403f05 100644
--- a/docs/0.58/alert/index.html
+++ b/docs/0.58/alert/index.html
@@ -70,7 +70,7 @@
             });
         
                      Edit
                      Alert
                      Launches an alert dialog with the specified title and message.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
 
                      Example
                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.58/clipboard.html b/docs/0.58/clipboard.html
index 40c9c0d2284..fa7aa333055 100644
--- a/docs/0.58/clipboard.html
+++ b/docs/0.58/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.58/clipboard/index.html b/docs/0.58/clipboard/index.html
index 40c9c0d2284..fa7aa333055 100644
--- a/docs/0.58/clipboard/index.html
+++ b/docs/0.58/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.58/components-and-apis.html b/docs/0.58/components-and-apis.html
index 991d7522e2e..44e51629995 100644
--- a/docs/0.58/components-and-apis.html
+++ b/docs/0.58/components-and-apis.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.58/components-and-apis/index.html b/docs/0.58/components-and-apis/index.html
index 991d7522e2e..44e51629995 100644
--- a/docs/0.58/components-and-apis/index.html
+++ b/docs/0.58/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.58/getting-started.html b/docs/0.58/getting-started.html
index acce7f65209..96c67ecf523 100644
--- a/docs/0.58/getting-started.html
+++ b/docs/0.58/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.58/getting-started/index.html b/docs/0.58/getting-started/index.html
index acce7f65209..96c67ecf523 100644
--- a/docs/0.58/getting-started/index.html
+++ b/docs/0.58/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.58/images.html b/docs/0.58/images.html
index 1d6d3ca6171..fb5587b35c2 100644
--- a/docs/0.58/images.html
+++ b/docs/0.58/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.58/images/index.html b/docs/0.58/images/index.html
index 1d6d3ca6171..fb5587b35c2 100644
--- a/docs/0.58/images/index.html
+++ b/docs/0.58/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.58/navigation.html b/docs/0.58/navigation.html
index c4a45f23445..b3233d1b74d 100644
--- a/docs/0.58/navigation.html
+++ b/docs/0.58/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.58/navigation/index.html b/docs/0.58/navigation/index.html
index c4a45f23445..b3233d1b74d 100644
--- a/docs/0.58/navigation/index.html
+++ b/docs/0.58/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.58/picker.html b/docs/0.58/picker.html
index a1ac165c936..2f9e193fce8 100644
--- a/docs/0.58/picker.html
+++ b/docs/0.58/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   style={{height: 50, width: 100}}
diff --git a/docs/0.58/picker/index.html b/docs/0.58/picker/index.html
index a1ac165c936..2f9e193fce8 100644
--- a/docs/0.58/picker/index.html
+++ b/docs/0.58/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   style={{height: 50, width: 100}}
diff --git a/docs/0.58/platform-specific-code.html b/docs/0.58/platform-specific-code.html
index 73bc8e1d665..40abb54a6aa 100644
--- a/docs/0.58/platform-specific-code.html
+++ b/docs/0.58/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.58/platform-specific-code/index.html b/docs/0.58/platform-specific-code/index.html
index 73bc8e1d665..40abb54a6aa 100644
--- a/docs/0.58/platform-specific-code/index.html
+++ b/docs/0.58/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.58/text.html b/docs/0.58/text.html
index 8062de7506b..837557a1738 100644
--- a/docs/0.58/text.html
+++ b/docs/0.58/text.html
@@ -124,7 +124,7 @@ AppRegistry.registerComponent('TextInANest', ()
           width: 100%;
         "
       >
                        Nested text
                        
-
                        Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
+
                        Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
 
                        Nested text
                        
-
                        Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
+
                        Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
 
                        Edit
                        Accessibility
                        Native App Accessibility (iOS and Android)
                        
-
                        Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
+        
                        Edit
                        Accessibility
                        Native App Accessibility (Android and iOS)
                        
+
                        Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
 
                        In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                        
 
                        Making Apps Accessible
                        
 
                        Accessibility properties
                        
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                      
-
                      ← AnimationsImproving User Experience →
                      Edit
                      Accessibility
                      Native App Accessibility (iOS and Android)
                      
-
                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
+        
                      Edit
                      Accessibility
                      Native App Accessibility (Android and iOS)
                      
+
                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
 
                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                      
 
                      Making Apps Accessible
                      
 
                      Accessibility properties
                      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
                      -
                      ← AnimationsImproving User Experience →
                      Edit

                      Alert

                      Launches an alert dialog with the specified title and message.

                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.

                      -

                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                      +

                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.

                      Example

                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.59/alert/index.html b/docs/0.59/alert/index.html
index ff59a69aefd..8886d413c42 100644
--- a/docs/0.59/alert/index.html
+++ b/docs/0.59/alert/index.html
@@ -70,7 +70,7 @@
             });
         
                      Edit
                      Alert
                      Launches an alert dialog with the specified title and message.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
 
                      Example
                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.59/clipboard.html b/docs/0.59/clipboard.html
index eead8e7f8a5..316f55d1ce6 100644
--- a/docs/0.59/clipboard.html
+++ b/docs/0.59/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.59/clipboard/index.html b/docs/0.59/clipboard/index.html
index eead8e7f8a5..316f55d1ce6 100644
--- a/docs/0.59/clipboard/index.html
+++ b/docs/0.59/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.59/components-and-apis.html b/docs/0.59/components-and-apis.html
index 001dfa94a23..34addadd95e 100644
--- a/docs/0.59/components-and-apis.html
+++ b/docs/0.59/components-and-apis.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.59/components-and-apis/index.html b/docs/0.59/components-and-apis/index.html
index 001dfa94a23..34addadd95e 100644
--- a/docs/0.59/components-and-apis/index.html
+++ b/docs/0.59/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                        
     
       
                        Picker
                        
-      
                        Renders the native picker component on iOS and Android.
                        
+      
                        Renders the native picker component on Android and iOS.
                        
                             
   
                        
   
                        
@@ -290,7 +290,7 @@
   
                        
     
       
                        Clipboard
                        
-      
                        Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                        
+      
                        Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                        
                             
   
                        
   
                        
diff --git a/docs/0.59/getting-started.html b/docs/0.59/getting-started.html
index df9bbb89ba5..546aa3bb0db 100644
--- a/docs/0.59/getting-started.html
+++ b/docs/0.59/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.59/getting-started/index.html b/docs/0.59/getting-started/index.html
index df9bbb89ba5..546aa3bb0db 100644
--- a/docs/0.59/getting-started/index.html
+++ b/docs/0.59/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                        If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                        
 
                        
 
                        Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                        
-
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                        
+
                        The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                        
 
                        
   Development OS:
   
diff --git a/docs/0.59/images.html b/docs/0.59/images.html
index be8e6221127..4e7fb11dfcd 100644
--- a/docs/0.59/images.html
+++ b/docs/0.59/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.59/images/index.html b/docs/0.59/images/index.html
index be8e6221127..4e7fb11dfcd 100644
--- a/docs/0.59/images/index.html
+++ b/docs/0.59/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                        Edit
                        Images
                        Static Image Resources
                        
-
                        React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
+
                        React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                        
 
                        <Image source={require('./my-icon.png')} />
 
                        
 
                        The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                        
@@ -88,7 +88,7 @@
 
                        On Windows, you might need to restart the packager if you add new images to your project.
                        
 
                        Here are some benefits that you get:
                        
 
                          
-
                        1. Same system on iOS and Android.
                          2. 
+
                        2. Same system on Android and iOS.
                          3. 
 
                        3. Images live in the same folder as your JavaScript code. Components are self-contained.
                          4. 
 
                        4. No global namespace, i.e. you don't have to worry about name collisions.
                          5. 
 
                        5. Only the images that are actually used will be packaged into your app.
                          6. 
diff --git a/docs/0.59/navigation.html b/docs/0.59/navigation.html
index 0bc01441092..5a9855516e9 100644
--- a/docs/0.59/navigation.html
+++ b/docs/0.59/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.59/navigation/index.html b/docs/0.59/navigation/index.html
index 0bc01441092..5a9855516e9 100644
--- a/docs/0.59/navigation/index.html
+++ b/docs/0.59/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                        Edit
                        Navigating Between Screens
                        Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                        
-
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                        
-
                        If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
+
                        This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                        
+
                        If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                        
 
                        React Navigation
                        
 
                        The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                        
 
                        The first step is to install in your project:
                        
diff --git a/docs/0.59/picker.html b/docs/0.59/picker.html
index 2fe0f7d3b6a..e82f87fc3d6 100644
--- a/docs/0.59/picker.html
+++ b/docs/0.59/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   style={{height: 50, width: 100}}
diff --git a/docs/0.59/picker/index.html b/docs/0.59/picker/index.html
index 2fe0f7d3b6a..e82f87fc3d6 100644
--- a/docs/0.59/picker/index.html
+++ b/docs/0.59/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                        Edit
                        Picker
                        Renders the native picker component on iOS and Android. Example:
                        
+        
                        Edit
                        Picker
                        Renders the native picker component on Android and iOS. Example:
                        
 
                        <Picker
   selectedValue={this.state.language}
   style={{height: 50, width: 100}}
diff --git a/docs/0.59/platform-specific-code.html b/docs/0.59/platform-specific-code.html
index cae289ed249..a1920dcccb3 100644
--- a/docs/0.59/platform-specific-code.html
+++ b/docs/0.59/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.59/platform-specific-code/index.html b/docs/0.59/platform-specific-code/index.html
index cae289ed249..a1920dcccb3 100644
--- a/docs/0.59/platform-specific-code/index.html
+++ b/docs/0.59/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                        
+        
                        Edit
                        Platform Specific Code
                        When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                        
 
                        React Native provides two ways to organize your code and separate it by platform:
                        
 
                          
 
                        • Using the Platform module.
                          • 
diff --git a/docs/0.59/text.html b/docs/0.59/text.html
index dd3f66eb119..6004a954a8c 100644
--- a/docs/0.59/text.html
+++ b/docs/0.59/text.html
@@ -124,7 +124,7 @@ AppRegistry.registerComponent('TextInANest', ()
           width: 100%;
         "
       >
                        Nested text
                        
-
                        Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
+
                        Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
 
                        Nested text
                        
-
                        Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
+
                        Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                        
 
                        Edit
                        Accessibility
                        Native App Accessibility (iOS and Android)
                        
-
                        Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
+        
                        Edit
                        Accessibility
                        Native App Accessibility (Android and iOS)
                        
+
                        Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                        
 
                        In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                        
 
                        Making Apps Accessible
                        
 
                        Accessibility properties
                        
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                      
-
                      ← AnimationsImproving User Experience →
                      Edit
                      Accessibility
                      Native App Accessibility (iOS and Android)
                      
-
                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
+        
                      Edit
                      Accessibility
                      Native App Accessibility (Android and iOS)
                      
+
                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
 
                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                      
 
                      Making Apps Accessible
                      
 
                      Accessibility properties
                      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
                      -
                      ← AnimationsImproving User Experience →

                      0.6

                      Edit

                      Alert

                      Use Alert to display an alert dialog.

                      -

                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

                      +

                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

                      On iOS, you can specify any number of buttons.

                      On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

                      @@ -25,7 +25,7 @@

                      Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.6/alert/index.html b/docs/0.6/alert/index.html
index 99bd77503ff..4baced232e5 100644
--- a/docs/0.6/alert/index.html
+++ b/docs/0.6/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
                      0.6
                      Edit
                      Alert
                      Use Alert to display an alert dialog.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                      
 
                      On iOS, you can specify any number of buttons.
                      
 
                      On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                      
@@ -25,7 +25,7 @@
 
                      Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                      
 
                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                      
 
                      Example usage:
                      
-
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.6/clipboard.html b/docs/0.6/clipboard.html
index 1064da32ba4..d197e7c2398 100644
--- a/docs/0.6/clipboard.html
+++ b/docs/0.6/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      0.6
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      0.6
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.6/clipboard/index.html b/docs/0.6/clipboard/index.html
index 1064da32ba4..d197e7c2398 100644
--- a/docs/0.6/clipboard/index.html
+++ b/docs/0.6/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                        0.6
                        Edit
                        Clipboard
                        Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                        
+        
                        0.6
                        Edit
                        Clipboard
                        Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                        
 
                        Methods
                        
 
                          
 
                        • getString
                          • 
diff --git a/docs/0.6/components-and-apis.html b/docs/0.6/components-and-apis.html
index ff73288b59a..b85f7a4d8b9 100644
--- a/docs/0.6/components-and-apis.html
+++ b/docs/0.6/components-and-apis.html
@@ -130,7 +130,7 @@
   
                          
     
       
                          Picker
                          
-      
                          Renders the native picker component on iOS and Android.
                          
+      
                          Renders the native picker component on Android and iOS.
                          
                               
   
                          
   
                          
@@ -290,7 +290,7 @@
   
                          
     
       
                          Clipboard
                          
-      
                          Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                          
+      
                          Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                          
                               
   
                          
   
                          
diff --git a/docs/0.6/components-and-apis/index.html b/docs/0.6/components-and-apis/index.html
index ff73288b59a..b85f7a4d8b9 100644
--- a/docs/0.6/components-and-apis/index.html
+++ b/docs/0.6/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                          
     
       
                          Picker
                          
-      
                          Renders the native picker component on iOS and Android.
                          
+      
                          Renders the native picker component on Android and iOS.
                          
                               
   
                          
   
                          
@@ -290,7 +290,7 @@
   
                          
     
       
                          Clipboard
                          
-      
                          Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                          
+      
                          Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                          
                               
   
                          
   
                          
diff --git a/docs/0.6/getting-started.html b/docs/0.6/getting-started.html
index e195e0c9881..a6ef7d942a4 100644
--- a/docs/0.6/getting-started.html
+++ b/docs/0.6/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                          If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                          
 
                          
 
                          Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                          
-
                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                          
+
                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                          
 
                          
   Development OS:
   
diff --git a/docs/0.6/getting-started/index.html b/docs/0.6/getting-started/index.html
index e195e0c9881..a6ef7d942a4 100644
--- a/docs/0.6/getting-started/index.html
+++ b/docs/0.6/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                          If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                          
 
                          
 
                          Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                          
-
                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                          
+
                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                          
 
                          
   Development OS:
   
diff --git a/docs/0.6/images.html b/docs/0.6/images.html
index 23704d305ea..6f61260b9e1 100644
--- a/docs/0.6/images.html
+++ b/docs/0.6/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                          Edit
                          Images
                          Static Image Resources
                          
-
                          React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                          
+
                          React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                          
 
                          <Image source={require('./my-icon.png')} />
 
                          
 
                          The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                          
@@ -88,7 +88,7 @@
 
                          On Windows, you might need to restart the packager if you add new images to your project.
                          
 
                          Here are some benefits that you get:
                          
 
                            
-
                          1. Same system on iOS and Android.
                            2. 
+
                          2. Same system on Android and iOS.
                            3. 
 
                          3. Images live in the same folder as your JavaScript code. Components are self-contained.
                            4. 
 
                          4. No global namespace, i.e. you don't have to worry about name collisions.
                            5. 
 
                          5. Only the images that are actually used will be packaged into your app.
                            6. 
diff --git a/docs/0.6/images/index.html b/docs/0.6/images/index.html
index 23704d305ea..6f61260b9e1 100644
--- a/docs/0.6/images/index.html
+++ b/docs/0.6/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                          Edit
                          Images
                          Static Image Resources
                          
-
                          React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                          
+
                          React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                          
 
                          <Image source={require('./my-icon.png')} />
 
                          
 
                          The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                          
@@ -88,7 +88,7 @@
 
                          On Windows, you might need to restart the packager if you add new images to your project.
                          
 
                          Here are some benefits that you get:
                          
 
                            
-
                          1. Same system on iOS and Android.
                            2. 
+
                          2. Same system on Android and iOS.
                            3. 
 
                          3. Images live in the same folder as your JavaScript code. Components are self-contained.
                            4. 
 
                          4. No global namespace, i.e. you don't have to worry about name collisions.
                            5. 
 
                          5. Only the images that are actually used will be packaged into your app.
                            6. 
diff --git a/docs/0.6/navigation.html b/docs/0.6/navigation.html
index 09b78a658fa..a619facf08b 100644
--- a/docs/0.6/navigation.html
+++ b/docs/0.6/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                          Edit
                          Navigating Between Screens
                          Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                          
-
                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                          
-
                          If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                          
+
                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                          
+
                          If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                          
 
                          React Navigation
                          
 
                          The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                          
 
                          The first step is to install in your project:
                          
diff --git a/docs/0.6/navigation/index.html b/docs/0.6/navigation/index.html
index 09b78a658fa..a619facf08b 100644
--- a/docs/0.6/navigation/index.html
+++ b/docs/0.6/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                          Edit
                          Navigating Between Screens
                          Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                          
-
                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                          
-
                          If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                          
+
                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                          
+
                          If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                          
 
                          React Navigation
                          
 
                          The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                          
 
                          The first step is to install in your project:
                          
diff --git a/docs/0.6/navigator.html b/docs/0.6/navigator.html
index 45400387f48..3f21c4f2a7d 100644
--- a/docs/0.6/navigator.html
+++ b/docs/0.6/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                          Edit
                          Navigator
                          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                          
+        
                          Edit
                          Navigator
                          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                          
 
                          To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                          
 
                          import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.6/navigator/index.html b/docs/0.6/navigator/index.html
index 45400387f48..3f21c4f2a7d 100644
--- a/docs/0.6/navigator/index.html
+++ b/docs/0.6/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                          Edit
                          Navigator
                          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                          
+        
                          Edit
                          Navigator
                          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                          
 
                          To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                          
 
                          import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.6/picker.html b/docs/0.6/picker.html
index c040fd0dce0..e9c1495c606 100644
--- a/docs/0.6/picker.html
+++ b/docs/0.6/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                          0.6
                          Edit
                          Picker
                          Renders the native picker component on iOS and Android. Example:
                          
+        
                          0.6
                          Edit
                          Picker
                          Renders the native picker component on Android and iOS. Example:
                          
 
                          <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.6/picker/index.html b/docs/0.6/picker/index.html
index c040fd0dce0..e9c1495c606 100644
--- a/docs/0.6/picker/index.html
+++ b/docs/0.6/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                          0.6
                          Edit
                          Picker
                          Renders the native picker component on iOS and Android. Example:
                          
+        
                          0.6
                          Edit
                          Picker
                          Renders the native picker component on Android and iOS. Example:
                          
 
                          <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.6/platform-specific-code.html b/docs/0.6/platform-specific-code.html
index 9db819e64db..ace2dfe3b96 100644
--- a/docs/0.6/platform-specific-code.html
+++ b/docs/0.6/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                          Edit
                          Platform Specific Code
                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                          
+        
                          Edit
                          Platform Specific Code
                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                          
 
                          React Native provides two ways to organize your code and separate it by platform:
                          
 
                            
 
                          • Using the Platform module.
                            • 
diff --git a/docs/0.6/platform-specific-code/index.html b/docs/0.6/platform-specific-code/index.html
index 9db819e64db..ace2dfe3b96 100644
--- a/docs/0.6/platform-specific-code/index.html
+++ b/docs/0.6/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                          Edit
                          Platform Specific Code
                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                          
+        
                          Edit
                          Platform Specific Code
                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                          
 
                          React Native provides two ways to organize your code and separate it by platform:
                          
 
                            
 
                          • Using the Platform module.
                            • 
diff --git a/docs/0.60/accessibility.html b/docs/0.60/accessibility.html
index e00c721dd8c..79d39015399 100644
--- a/docs/0.60/accessibility.html
+++ b/docs/0.60/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                          Edit
                          Accessibility
                          Native App Accessibility (iOS and Android)
                          
-
                          Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                          
+        
                          Edit
                          Accessibility
                          Native App Accessibility (Android and iOS)
                          
+
                          Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                          
 
                          In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                          
 
                          Making Apps Accessible
                          
 
                          Accessibility properties
                          
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                          
-
                          ← AnimationsImproving User Experience →
                          Edit
                          Accessibility
                          Native App Accessibility (iOS and Android)
                          
-
                          Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                          
+        
                          Edit
                          Accessibility
                          Native App Accessibility (Android and iOS)
                          
+
                          Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                          
 
                          In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                          
 
                          Making Apps Accessible
                          
 
                          Accessibility properties
                          
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                          
-
                          ← AnimationsImproving User Experience →
                          Edit
                          Alert
                          Launches an alert dialog with the specified title and message.
                          
 
                          Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
                          
-
                          This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                          
+
                          This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                          
 
                          Example
                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.60/alert/index.html b/docs/0.60/alert/index.html
index 9076ee90a98..d3e5772f28a 100644
--- a/docs/0.60/alert/index.html
+++ b/docs/0.60/alert/index.html
@@ -70,7 +70,7 @@
             });
         
                      Edit
                      Alert
                      Launches an alert dialog with the specified title and message.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
 
                      Example
                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.60/clipboard.html b/docs/0.60/clipboard.html
index d8cd027ac56..256b5781fff 100644
--- a/docs/0.60/clipboard.html
+++ b/docs/0.60/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      
 
                      Reference
                      
 
                      Methods
                      
diff --git a/docs/0.60/clipboard/index.html b/docs/0.60/clipboard/index.html
index d8cd027ac56..256b5781fff 100644
--- a/docs/0.60/clipboard/index.html
+++ b/docs/0.60/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      
 
                      Reference
                      
 
                      Methods
                      
diff --git a/docs/0.60/components-and-apis.html b/docs/0.60/components-and-apis.html
index 6ec1ba57f33..0a49d020fb8 100644
--- a/docs/0.60/components-and-apis.html
+++ b/docs/0.60/components-and-apis.html
@@ -130,7 +130,7 @@
   
                      
     
       
                      Picker
                      
-      
                      Renders the native picker component on iOS and Android.
                      
+      
                      Renders the native picker component on Android and iOS.
                      
                           
   
                      
   
                      
@@ -290,7 +290,7 @@
   
                      
     
       
                      Clipboard
                      
-      
                      Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                      
+      
                      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                      
                           
   
                      
   
                      
diff --git a/docs/0.60/components-and-apis/index.html b/docs/0.60/components-and-apis/index.html
index 6ec1ba57f33..0a49d020fb8 100644
--- a/docs/0.60/components-and-apis/index.html
+++ b/docs/0.60/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                      
     
       
                      Picker
                      
-      
                      Renders the native picker component on iOS and Android.
                      
+      
                      Renders the native picker component on Android and iOS.
                      
                           
   
                      
   
                      
@@ -290,7 +290,7 @@
   
                      
     
       
                      Clipboard
                      
-      
                      Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                      
+      
                      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                      
                           
   
                      
   
                      
diff --git a/docs/0.60/getting-started.html b/docs/0.60/getting-started.html
index f081196df8b..b104b42b69a 100644
--- a/docs/0.60/getting-started.html
+++ b/docs/0.60/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                      
 
                      
 
                      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                      
-
                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                      
+
                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                      
 
                      
   Development OS:
   
diff --git a/docs/0.60/getting-started/index.html b/docs/0.60/getting-started/index.html
index f081196df8b..b104b42b69a 100644
--- a/docs/0.60/getting-started/index.html
+++ b/docs/0.60/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                      
 
                      
 
                      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                      
-
                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                      
+
                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                      
 
                      
   Development OS:
   
diff --git a/docs/0.60/images.html b/docs/0.60/images.html
index 50ab1e24709..f3c1c8c6a3f 100644
--- a/docs/0.60/images.html
+++ b/docs/0.60/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                      Edit
                      Images
                      Static Image Resources
                      
-
                      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                      
+
                      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                      
 
                      <Image source={require('./my-icon.png')} />
 
                      
 
                      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                      
@@ -88,7 +88,7 @@
 
                      On Windows, you might need to restart the packager if you add new images to your project.
                      
 
                      Here are some benefits that you get:
                      
 
                        
-
                      1. Same system on iOS and Android.
                        2. 
+
                      2. Same system on Android and iOS.
                        3. 
 
                      3. Images live in the same folder as your JavaScript code. Components are self-contained.
                        4. 
 
                      4. No global namespace, i.e. you don't have to worry about name collisions.
                        5. 
 
                      5. Only the images that are actually used will be packaged into your app.
                        6. 
diff --git a/docs/0.60/images/index.html b/docs/0.60/images/index.html
index 50ab1e24709..f3c1c8c6a3f 100644
--- a/docs/0.60/images/index.html
+++ b/docs/0.60/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                      Edit
                      Images
                      Static Image Resources
                      
-
                      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                      
+
                      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                      
 
                      <Image source={require('./my-icon.png')} />
 
                      
 
                      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                      
@@ -88,7 +88,7 @@
 
                      On Windows, you might need to restart the packager if you add new images to your project.
                      
 
                      Here are some benefits that you get:
                      
 
                        
-
                      1. Same system on iOS and Android.
                        2. 
+
                      2. Same system on Android and iOS.
                        3. 
 
                      3. Images live in the same folder as your JavaScript code. Components are self-contained.
                        4. 
 
                      4. No global namespace, i.e. you don't have to worry about name collisions.
                        5. 
 
                      5. Only the images that are actually used will be packaged into your app.
                        6. 
diff --git a/docs/0.60/navigation.html b/docs/0.60/navigation.html
index ab45f8f86d5..03750ec3a43 100644
--- a/docs/0.60/navigation.html
+++ b/docs/0.60/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                      Edit
                      Navigating Between Screens
                      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                      
-
                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                      
-
                      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                      
+
                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                      
+
                      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                      
 
                      React Navigation
                      
 
                      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                      
 
                      The first step is to install in your project:
                      
diff --git a/docs/0.60/navigation/index.html b/docs/0.60/navigation/index.html
index ab45f8f86d5..03750ec3a43 100644
--- a/docs/0.60/navigation/index.html
+++ b/docs/0.60/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                      Edit
                      Navigating Between Screens
                      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                      
-
                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                      
-
                      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                      
+
                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                      
+
                      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                      
 
                      React Navigation
                      
 
                      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                      
 
                      The first step is to install in your project:
                      
diff --git a/docs/0.60/picker.html b/docs/0.60/picker.html
index aa47eb9e5f4..ae4ba9c22b0 100644
--- a/docs/0.60/picker.html
+++ b/docs/0.60/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                      Edit
                      Picker
                      Renders the native picker component on iOS and Android. Example:
                      
+        
                      Edit
                      Picker
                      Renders the native picker component on Android and iOS. Example:
                      
 
                      <Picker
   selectedValue={this.state.language}
   style={{height: 50, width: 100}}
diff --git a/docs/0.60/picker/index.html b/docs/0.60/picker/index.html
index aa47eb9e5f4..ae4ba9c22b0 100644
--- a/docs/0.60/picker/index.html
+++ b/docs/0.60/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                      Edit
                      Picker
                      Renders the native picker component on iOS and Android. Example:
                      
+        
                      Edit
                      Picker
                      Renders the native picker component on Android and iOS. Example:
                      
 
                      <Picker
   selectedValue={this.state.language}
   style={{height: 50, width: 100}}
diff --git a/docs/0.60/platform-specific-code.html b/docs/0.60/platform-specific-code.html
index e2684a6152f..8f8335321c1 100644
--- a/docs/0.60/platform-specific-code.html
+++ b/docs/0.60/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                      Edit
                      Platform Specific Code
                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                      
+        
                      Edit
                      Platform Specific Code
                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                      
 
                      React Native provides two ways to organize your code and separate it by platform:
                      
 
                        
 
                      • Using the Platform module.
                        • 
diff --git a/docs/0.60/platform-specific-code/index.html b/docs/0.60/platform-specific-code/index.html
index e2684a6152f..8f8335321c1 100644
--- a/docs/0.60/platform-specific-code/index.html
+++ b/docs/0.60/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                      Edit
                      Platform Specific Code
                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                      
+        
                      Edit
                      Platform Specific Code
                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                      
 
                      React Native provides two ways to organize your code and separate it by platform:
                      
 
                        
 
                      • Using the Platform module.
                        • 
diff --git a/docs/0.60/text.html b/docs/0.60/text.html
index 5309bb5bbe5..9b2635a98b3 100644
--- a/docs/0.60/text.html
+++ b/docs/0.60/text.html
@@ -121,7 +121,7 @@
           width: 100%;
         "
       >
                      Nested text
                      
-
                      Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                      
+
                      Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                      
 
                      Nested text
                      
-
                      Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                      
+
                      Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                      
 
                      Edit
                      Accessibility
                      Native App Accessibility (iOS and Android)
                      
-
                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
+        
                      Edit
                      Accessibility
                      Native App Accessibility (Android and iOS)
                      
+
                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
 
                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                      
 
                      Making Apps Accessible
                      
 
                      Accessibility properties
                      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                      
-
                      ← AnimationsImproving User Experience →
                      Edit
                      Accessibility
                      Native App Accessibility (iOS and Android)
                      
-
                      Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
+        
                      Edit
                      Accessibility
                      Native App Accessibility (Android and iOS)
                      
+
                      Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
 
                      In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                      
 
                      Making Apps Accessible
                      
 
                      Accessibility properties
                      
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
                      -
                      ← AnimationsImproving User Experience →

                      0.7

                      Edit

                      Alert

                      Use Alert to display an alert dialog.

                      -

                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

                      +

                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.

                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.

                      On iOS, you can specify any number of buttons.

                      On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:

                      @@ -25,7 +25,7 @@

                      Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.7/alert/index.html b/docs/0.7/alert/index.html
index e3a5202c4b1..fa4b44a0f04 100644
--- a/docs/0.7/alert/index.html
+++ b/docs/0.7/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
                      0.7
                      Edit
                      Alert
                      Use Alert to display an alert dialog.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                      
 
                      On iOS, you can specify any number of buttons.
                      
 
                      On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                      
@@ -25,7 +25,7 @@
 
                      Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                      
 
                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                      
 
                      Example usage:
                      
-
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.7/clipboard.html b/docs/0.7/clipboard.html
index 377235b0c62..6760f246c7e 100644
--- a/docs/0.7/clipboard.html
+++ b/docs/0.7/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      0.7
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      0.7
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      Methods
                      
 
                        
 
                      • getString
                        • 
diff --git a/docs/0.7/clipboard/index.html b/docs/0.7/clipboard/index.html
index 377235b0c62..6760f246c7e 100644
--- a/docs/0.7/clipboard/index.html
+++ b/docs/0.7/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                        0.7
                        Edit
                        Clipboard
                        Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                        
+        
                        0.7
                        Edit
                        Clipboard
                        Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                        
 
                        Methods
                        
 
                          
 
                        • getString
                          • 
diff --git a/docs/0.7/components-and-apis.html b/docs/0.7/components-and-apis.html
index 87417ef2c36..2df107dfa54 100644
--- a/docs/0.7/components-and-apis.html
+++ b/docs/0.7/components-and-apis.html
@@ -130,7 +130,7 @@
   
                          
     
       
                          Picker
                          
-      
                          Renders the native picker component on iOS and Android.
                          
+      
                          Renders the native picker component on Android and iOS.
                          
                               
   
                          
   
                          
@@ -290,7 +290,7 @@
   
                          
     
       
                          Clipboard
                          
-      
                          Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                          
+      
                          Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                          
                               
   
                          
   
                          
diff --git a/docs/0.7/components-and-apis/index.html b/docs/0.7/components-and-apis/index.html
index 87417ef2c36..2df107dfa54 100644
--- a/docs/0.7/components-and-apis/index.html
+++ b/docs/0.7/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                          
     
       
                          Picker
                          
-      
                          Renders the native picker component on iOS and Android.
                          
+      
                          Renders the native picker component on Android and iOS.
                          
                               
   
                          
   
                          
@@ -290,7 +290,7 @@
   
                          
     
       
                          Clipboard
                          
-      
                          Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                          
+      
                          Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                          
                               
   
                          
   
                          
diff --git a/docs/0.7/getting-started.html b/docs/0.7/getting-started.html
index b2157917f85..9a5311e0694 100644
--- a/docs/0.7/getting-started.html
+++ b/docs/0.7/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                          If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                          
 
                          
 
                          Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                          
-
                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                          
+
                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                          
 
                          
   Development OS:
   
diff --git a/docs/0.7/getting-started/index.html b/docs/0.7/getting-started/index.html
index b2157917f85..9a5311e0694 100644
--- a/docs/0.7/getting-started/index.html
+++ b/docs/0.7/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                          If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                          
 
                          
 
                          Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                          
-
                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                          
+
                          The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                          
 
                          
   Development OS:
   
diff --git a/docs/0.7/images.html b/docs/0.7/images.html
index f2ac2fd2300..a8b54bb86a7 100644
--- a/docs/0.7/images.html
+++ b/docs/0.7/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                          Edit
                          Images
                          Static Image Resources
                          
-
                          React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                          
+
                          React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                          
 
                          <Image source={require('./my-icon.png')} />
 
                          
 
                          The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                          
@@ -88,7 +88,7 @@
 
                          On Windows, you might need to restart the packager if you add new images to your project.
                          
 
                          Here are some benefits that you get:
                          
 
                            
-
                          1. Same system on iOS and Android.
                            2. 
+
                          2. Same system on Android and iOS.
                            3. 
 
                          3. Images live in the same folder as your JavaScript code. Components are self-contained.
                            4. 
 
                          4. No global namespace, i.e. you don't have to worry about name collisions.
                            5. 
 
                          5. Only the images that are actually used will be packaged into your app.
                            6. 
diff --git a/docs/0.7/images/index.html b/docs/0.7/images/index.html
index f2ac2fd2300..a8b54bb86a7 100644
--- a/docs/0.7/images/index.html
+++ b/docs/0.7/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                          Edit
                          Images
                          Static Image Resources
                          
-
                          React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                          
+
                          React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                          
 
                          <Image source={require('./my-icon.png')} />
 
                          
 
                          The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                          
@@ -88,7 +88,7 @@
 
                          On Windows, you might need to restart the packager if you add new images to your project.
                          
 
                          Here are some benefits that you get:
                          
 
                            
-
                          1. Same system on iOS and Android.
                            2. 
+
                          2. Same system on Android and iOS.
                            3. 
 
                          3. Images live in the same folder as your JavaScript code. Components are self-contained.
                            4. 
 
                          4. No global namespace, i.e. you don't have to worry about name collisions.
                            5. 
 
                          5. Only the images that are actually used will be packaged into your app.
                            6. 
diff --git a/docs/0.7/navigation.html b/docs/0.7/navigation.html
index ece7e894afe..e9d950cf2a7 100644
--- a/docs/0.7/navigation.html
+++ b/docs/0.7/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                          Edit
                          Navigating Between Screens
                          Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                          
-
                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                          
-
                          If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                          
+
                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                          
+
                          If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                          
 
                          React Navigation
                          
 
                          The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                          
 
                          The first step is to install in your project:
                          
diff --git a/docs/0.7/navigation/index.html b/docs/0.7/navigation/index.html
index ece7e894afe..e9d950cf2a7 100644
--- a/docs/0.7/navigation/index.html
+++ b/docs/0.7/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                          Edit
                          Navigating Between Screens
                          Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                          
-
                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                          
-
                          If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                          
+
                          This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                          
+
                          If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                          
 
                          React Navigation
                          
 
                          The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                          
 
                          The first step is to install in your project:
                          
diff --git a/docs/0.7/navigator.html b/docs/0.7/navigator.html
index 58a57071001..d4f52fce66a 100644
--- a/docs/0.7/navigator.html
+++ b/docs/0.7/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                          Edit
                          Navigator
                          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                          
+        
                          Edit
                          Navigator
                          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                          
 
                          To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                          
 
                          import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.7/navigator/index.html b/docs/0.7/navigator/index.html
index 58a57071001..d4f52fce66a 100644
--- a/docs/0.7/navigator/index.html
+++ b/docs/0.7/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                          Edit
                          Navigator
                          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                          
+        
                          Edit
                          Navigator
                          Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                          
 
                          To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                          
 
                          import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.7/picker.html b/docs/0.7/picker.html
index 442e06e15cc..55280c2de82 100644
--- a/docs/0.7/picker.html
+++ b/docs/0.7/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                          0.7
                          Edit
                          Picker
                          Renders the native picker component on iOS and Android. Example:
                          
+        
                          0.7
                          Edit
                          Picker
                          Renders the native picker component on Android and iOS. Example:
                          
 
                          <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.7/picker/index.html b/docs/0.7/picker/index.html
index 442e06e15cc..55280c2de82 100644
--- a/docs/0.7/picker/index.html
+++ b/docs/0.7/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                          0.7
                          Edit
                          Picker
                          Renders the native picker component on iOS and Android. Example:
                          
+        
                          0.7
                          Edit
                          Picker
                          Renders the native picker component on Android and iOS. Example:
                          
 
                          <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.7/platform-specific-code.html b/docs/0.7/platform-specific-code.html
index 7494bb295ba..e4fcf0833a5 100644
--- a/docs/0.7/platform-specific-code.html
+++ b/docs/0.7/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                          Edit
                          Platform Specific Code
                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                          
+        
                          Edit
                          Platform Specific Code
                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                          
 
                          React Native provides two ways to organize your code and separate it by platform:
                          
 
                            
 
                          • Using the Platform module.
                            • 
diff --git a/docs/0.7/platform-specific-code/index.html b/docs/0.7/platform-specific-code/index.html
index 7494bb295ba..e4fcf0833a5 100644
--- a/docs/0.7/platform-specific-code/index.html
+++ b/docs/0.7/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                          Edit
                          Platform Specific Code
                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                          
+        
                          Edit
                          Platform Specific Code
                          When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                          
 
                          React Native provides two ways to organize your code and separate it by platform:
                          
 
                            
 
                          • Using the Platform module.
                            • 
diff --git a/docs/0.8/accessibility.html b/docs/0.8/accessibility.html
index df5f6fc2f8f..1f387aa9ffc 100644
--- a/docs/0.8/accessibility.html
+++ b/docs/0.8/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                          Edit
                          Accessibility
                          Native App Accessibility (iOS and Android)
                          
-
                          Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                          
+        
                          Edit
                          Accessibility
                          Native App Accessibility (Android and iOS)
                          
+
                          Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                          
 
                          In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                          
 
                          Making Apps Accessible
                          
 
                          Accessibility properties
                          
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                          
-
                          ← AnimationsImproving User Experience →
                          Edit
                          Accessibility
                          Native App Accessibility (iOS and Android)
                          
-
                          Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                          
+        
                          Edit
                          Accessibility
                          Native App Accessibility (Android and iOS)
                          
+
                          Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                          
 
                          In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                          
 
                          Making Apps Accessible
                          
 
                          Accessibility properties
                          
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                          
-
                          ← AnimationsImproving User Experience →
                          0.8
                          Edit
                          Alert
                          Use Alert to display an alert dialog.
                          
-
                          This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                          
+
                          This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                          
 
                          Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                          
 
                          On iOS, you can specify any number of buttons.
                          
 
                          On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                          
@@ -25,7 +25,7 @@
 
                          Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                          
 
                          Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                          
 
                          Example usage:
                          
-
                          // Works on both iOS and Android
+
                          // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.8/alert/index.html b/docs/0.8/alert/index.html
index 3036d0506e4..e4aa66dd6fb 100644
--- a/docs/0.8/alert/index.html
+++ b/docs/0.8/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
                          0.8
                          Edit
                          Alert
                          Use Alert to display an alert dialog.
                          
-
                          This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                          
+
                          This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                          
 
                          Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                          
 
                          On iOS, you can specify any number of buttons.
                          
 
                          On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                          
@@ -25,7 +25,7 @@
 
                          Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                          
 
                          Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                          
 
                          Example usage:
                          
-
                          // Works on both iOS and Android
+
                          // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.8/clipboard.html b/docs/0.8/clipboard.html
index abb0a686042..1a7617ddf90 100644
--- a/docs/0.8/clipboard.html
+++ b/docs/0.8/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                          0.8
                          Edit
                          Clipboard
                          Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                          
+        
                          0.8
                          Edit
                          Clipboard
                          Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                          
 
                          Methods
                          
 
                            
 
                          • getString
                            • 
diff --git a/docs/0.8/clipboard/index.html b/docs/0.8/clipboard/index.html
index abb0a686042..1a7617ddf90 100644
--- a/docs/0.8/clipboard/index.html
+++ b/docs/0.8/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                            0.8
                            Edit
                            Clipboard
                            Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                            
+        
                            0.8
                            Edit
                            Clipboard
                            Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                            
 
                            Methods
                            
 
                              
 
                            • getString
                              • 
diff --git a/docs/0.8/components-and-apis.html b/docs/0.8/components-and-apis.html
index bfce54bcb42..28fa396ab42 100644
--- a/docs/0.8/components-and-apis.html
+++ b/docs/0.8/components-and-apis.html
@@ -130,7 +130,7 @@
   
                              
     
       
                              Picker
                              
-      
                              Renders the native picker component on iOS and Android.
                              
+      
                              Renders the native picker component on Android and iOS.
                              
                                   
   
                              
   
                              
@@ -290,7 +290,7 @@
   
                              
     
       
                              Clipboard
                              
-      
                              Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                              
+      
                              Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                              
                                   
   
                              
   
                              
diff --git a/docs/0.8/components-and-apis/index.html b/docs/0.8/components-and-apis/index.html
index bfce54bcb42..28fa396ab42 100644
--- a/docs/0.8/components-and-apis/index.html
+++ b/docs/0.8/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                              
     
       
                              Picker
                              
-      
                              Renders the native picker component on iOS and Android.
                              
+      
                              Renders the native picker component on Android and iOS.
                              
                                   
   
                              
   
                              
@@ -290,7 +290,7 @@
   
                              
     
       
                              Clipboard
                              
-      
                              Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                              
+      
                              Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                              
                                   
   
                              
   
                              
diff --git a/docs/0.8/getting-started.html b/docs/0.8/getting-started.html
index 42ecdad25cb..90d1342d1ce 100644
--- a/docs/0.8/getting-started.html
+++ b/docs/0.8/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                              If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                              
 
                              
 
                              Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                              
-
                              The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                              
+
                              The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                              
 
                              
   Development OS:
   
diff --git a/docs/0.8/getting-started/index.html b/docs/0.8/getting-started/index.html
index 42ecdad25cb..90d1342d1ce 100644
--- a/docs/0.8/getting-started/index.html
+++ b/docs/0.8/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                              If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                              
 
                              
 
                              Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                              
-
                              The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                              
+
                              The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                              
 
                              
   Development OS:
   
diff --git a/docs/0.8/images.html b/docs/0.8/images.html
index 89ade9b4dfd..d789cf2c223 100644
--- a/docs/0.8/images.html
+++ b/docs/0.8/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                              Edit
                              Images
                              Static Image Resources
                              
-
                              React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                              
+
                              React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                              
 
                              <Image source={require('./my-icon.png')} />
 
                              
 
                              The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                              
@@ -88,7 +88,7 @@
 
                              On Windows, you might need to restart the packager if you add new images to your project.
                              
 
                              Here are some benefits that you get:
                              
 
                                
-
                              1. Same system on iOS and Android.
                                2. 
+
                              2. Same system on Android and iOS.
                                3. 
 
                              3. Images live in the same folder as your JavaScript code. Components are self-contained.
                                4. 
 
                              4. No global namespace, i.e. you don't have to worry about name collisions.
                                5. 
 
                              5. Only the images that are actually used will be packaged into your app.
                                6. 
diff --git a/docs/0.8/images/index.html b/docs/0.8/images/index.html
index 89ade9b4dfd..d789cf2c223 100644
--- a/docs/0.8/images/index.html
+++ b/docs/0.8/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                              Edit
                              Images
                              Static Image Resources
                              
-
                              React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                              
+
                              React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                              
 
                              <Image source={require('./my-icon.png')} />
 
                              
 
                              The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                              
@@ -88,7 +88,7 @@
 
                              On Windows, you might need to restart the packager if you add new images to your project.
                              
 
                              Here are some benefits that you get:
                              
 
                                
-
                              1. Same system on iOS and Android.
                                2. 
+
                              2. Same system on Android and iOS.
                                3. 
 
                              3. Images live in the same folder as your JavaScript code. Components are self-contained.
                                4. 
 
                              4. No global namespace, i.e. you don't have to worry about name collisions.
                                5. 
 
                              5. Only the images that are actually used will be packaged into your app.
                                6. 
diff --git a/docs/0.8/navigation.html b/docs/0.8/navigation.html
index 95cf73fd584..b567e467475 100644
--- a/docs/0.8/navigation.html
+++ b/docs/0.8/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                              Edit
                              Navigating Between Screens
                              Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                              
-
                              This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                              
-
                              If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                              
+
                              This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                              
+
                              If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                              
 
                              React Navigation
                              
 
                              The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                              
 
                              The first step is to install in your project:
                              
diff --git a/docs/0.8/navigation/index.html b/docs/0.8/navigation/index.html
index 95cf73fd584..b567e467475 100644
--- a/docs/0.8/navigation/index.html
+++ b/docs/0.8/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                              Edit
                              Navigating Between Screens
                              Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                              
-
                              This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                              
-
                              If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                              
+
                              This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                              
+
                              If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                              
 
                              React Navigation
                              
 
                              The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                              
 
                              The first step is to install in your project:
                              
diff --git a/docs/0.8/navigator.html b/docs/0.8/navigator.html
index c7c479ad606..20dcb7d616f 100644
--- a/docs/0.8/navigator.html
+++ b/docs/0.8/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                              Edit
                              Navigator
                              Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                              
+        
                              Edit
                              Navigator
                              Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                              
 
                              To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                              
 
                              import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.8/navigator/index.html b/docs/0.8/navigator/index.html
index c7c479ad606..20dcb7d616f 100644
--- a/docs/0.8/navigator/index.html
+++ b/docs/0.8/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                              Edit
                              Navigator
                              Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                              
+        
                              Edit
                              Navigator
                              Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                              
 
                              To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                              
 
                              import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.8/picker.html b/docs/0.8/picker.html
index d52fe213310..e0f3b0ebd88 100644
--- a/docs/0.8/picker.html
+++ b/docs/0.8/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                              0.8
                              Edit
                              Picker
                              Renders the native picker component on iOS and Android. Example:
                              
+        
                              0.8
                              Edit
                              Picker
                              Renders the native picker component on Android and iOS. Example:
                              
 
                              <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.8/picker/index.html b/docs/0.8/picker/index.html
index d52fe213310..e0f3b0ebd88 100644
--- a/docs/0.8/picker/index.html
+++ b/docs/0.8/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                              0.8
                              Edit
                              Picker
                              Renders the native picker component on iOS and Android. Example:
                              
+        
                              0.8
                              Edit
                              Picker
                              Renders the native picker component on Android and iOS. Example:
                              
 
                              <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.8/platform-specific-code.html b/docs/0.8/platform-specific-code.html
index 18ac3b7a7c8..53fa13d7008 100644
--- a/docs/0.8/platform-specific-code.html
+++ b/docs/0.8/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                              Edit
                              Platform Specific Code
                              When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                              
+        
                              Edit
                              Platform Specific Code
                              When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                              
 
                              React Native provides two ways to organize your code and separate it by platform:
                              
 
                                
 
                              • Using the Platform module.
                                • 
diff --git a/docs/0.8/platform-specific-code/index.html b/docs/0.8/platform-specific-code/index.html
index 18ac3b7a7c8..53fa13d7008 100644
--- a/docs/0.8/platform-specific-code/index.html
+++ b/docs/0.8/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                              Edit
                              Platform Specific Code
                              When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                              
+        
                              Edit
                              Platform Specific Code
                              When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                              
 
                              React Native provides two ways to organize your code and separate it by platform:
                              
 
                                
 
                              • Using the Platform module.
                                • 
diff --git a/docs/0.9/accessibility.html b/docs/0.9/accessibility.html
index 331b05c7673..c787a85b395 100644
--- a/docs/0.9/accessibility.html
+++ b/docs/0.9/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                              Edit
                              Accessibility
                              Native App Accessibility (iOS and Android)
                              
-
                              Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                              
+        
                              Edit
                              Accessibility
                              Native App Accessibility (Android and iOS)
                              
+
                              Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                              
 
                              In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                              
 
                              Making Apps Accessible
                              
 
                              Accessibility properties
                              
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                              
-
                              ← AnimationsImproving User Experience →
                              Edit
                              Accessibility
                              Native App Accessibility (iOS and Android)
                              
-
                              Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                              
+        
                              Edit
                              Accessibility
                              Native App Accessibility (Android and iOS)
                              
+
                              Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                              
 
                              In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                              
 
                              Making Apps Accessible
                              
 
                              Accessibility properties
                              
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                              
-
                              ← AnimationsImproving User Experience →
                              0.9
                              Edit
                              Alert
                              Use Alert to display an alert dialog.
                              
-
                              This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                              
+
                              This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                              
 
                              Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                              
 
                              On iOS, you can specify any number of buttons.
                              
 
                              On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                              
@@ -25,7 +25,7 @@
 
                              Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                              
 
                              Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                              
 
                              Example usage:
                              
-
                              // Works on both iOS and Android
+
                              // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.9/alert/index.html b/docs/0.9/alert/index.html
index 140c589ece6..b75fca86636 100644
--- a/docs/0.9/alert/index.html
+++ b/docs/0.9/alert/index.html
@@ -13,7 +13,7 @@
           )
         });
         
                              0.9
                              Edit
                              Alert
                              Use Alert to display an alert dialog.
                              
-
                              This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                              
+
                              This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS, as entering text in an alert is common on iOS only.
                              
 
                              Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback, and dismiss the alert. If no buttons are provided, a single 'OK' button will be displayed by default.
                              
 
                              On iOS, you can specify any number of buttons.
                              
 
                              On Android, at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
                              
@@ -25,7 +25,7 @@
 
                              Alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
                              
 
                              Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false, i.e. { cancelable: false }
                              
 
                              Example usage:
                              
-
                              // Works on both iOS and Android
+
                              // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/0.9/clipboard.html b/docs/0.9/clipboard.html
index 4266dfe7c33..0ae1fd84664 100644
--- a/docs/0.9/clipboard.html
+++ b/docs/0.9/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                              0.9
                              Edit
                              Clipboard
                              Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                              
+        
                              0.9
                              Edit
                              Clipboard
                              Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                              
 
                              Methods
                              
 
                                
 
                              • getString
                                • 
diff --git a/docs/0.9/clipboard/index.html b/docs/0.9/clipboard/index.html
index 4266dfe7c33..0ae1fd84664 100644
--- a/docs/0.9/clipboard/index.html
+++ b/docs/0.9/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                                0.9
                                Edit
                                Clipboard
                                Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                                
+        
                                0.9
                                Edit
                                Clipboard
                                Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                                
 
                                Methods
                                
 
                                  
 
                                • getString
                                  • 
diff --git a/docs/0.9/components-and-apis.html b/docs/0.9/components-and-apis.html
index 4bbfbf38081..2d3170bf235 100644
--- a/docs/0.9/components-and-apis.html
+++ b/docs/0.9/components-and-apis.html
@@ -130,7 +130,7 @@
   
                                  
     
       
                                  Picker
                                  
-      
                                  Renders the native picker component on iOS and Android.
                                  
+      
                                  Renders the native picker component on Android and iOS.
                                  
                                       
   
                                  
   
                                  
@@ -290,7 +290,7 @@
   
                                  
     
       
                                  Clipboard
                                  
-      
                                  Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                                  
+      
                                  Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                                  
                                       
   
                                  
   
                                  
diff --git a/docs/0.9/components-and-apis/index.html b/docs/0.9/components-and-apis/index.html
index 4bbfbf38081..2d3170bf235 100644
--- a/docs/0.9/components-and-apis/index.html
+++ b/docs/0.9/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                                  
     
       
                                  Picker
                                  
-      
                                  Renders the native picker component on iOS and Android.
                                  
+      
                                  Renders the native picker component on Android and iOS.
                                  
                                       
   
                                  
   
                                  
@@ -290,7 +290,7 @@
   
                                  
     
       
                                  Clipboard
                                  
-      
                                  Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                                  
+      
                                  Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                                  
                                       
   
                                  
   
                                  
diff --git a/docs/0.9/getting-started.html b/docs/0.9/getting-started.html
index 478e7907e9f..3cc69244509 100644
--- a/docs/0.9/getting-started.html
+++ b/docs/0.9/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                                  If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                                  
 
                                  
 
                                  Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                                  
-
                                  The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                                  
+
                                  The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                                  
 
                                  
   Development OS:
   
diff --git a/docs/0.9/getting-started/index.html b/docs/0.9/getting-started/index.html
index 478e7907e9f..3cc69244509 100644
--- a/docs/0.9/getting-started/index.html
+++ b/docs/0.9/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                                  If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                                  
 
                                  
 
                                  Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                                  
-
                                  The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                                  
+
                                  The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                                  
 
                                  
   Development OS:
   
diff --git a/docs/0.9/images.html b/docs/0.9/images.html
index b75201b6cb6..998055e5663 100644
--- a/docs/0.9/images.html
+++ b/docs/0.9/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                                  Edit
                                  Images
                                  Static Image Resources
                                  
-
                                  React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                  
+
                                  React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                  
 
                                  <Image source={require('./my-icon.png')} />
 
                                  
 
                                  The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                                  
@@ -88,7 +88,7 @@
 
                                  On Windows, you might need to restart the packager if you add new images to your project.
                                  
 
                                  Here are some benefits that you get:
                                  
 
                                    
-
                                  1. Same system on iOS and Android.
                                    2. 
+
                                  2. Same system on Android and iOS.
                                    3. 
 
                                  3. Images live in the same folder as your JavaScript code. Components are self-contained.
                                    4. 
 
                                  4. No global namespace, i.e. you don't have to worry about name collisions.
                                    5. 
 
                                  5. Only the images that are actually used will be packaged into your app.
                                    6. 
diff --git a/docs/0.9/images/index.html b/docs/0.9/images/index.html
index b75201b6cb6..998055e5663 100644
--- a/docs/0.9/images/index.html
+++ b/docs/0.9/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                                  Edit
                                  Images
                                  Static Image Resources
                                  
-
                                  React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                  
+
                                  React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                                  
 
                                  <Image source={require('./my-icon.png')} />
 
                                  
 
                                  The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                                  
@@ -88,7 +88,7 @@
 
                                  On Windows, you might need to restart the packager if you add new images to your project.
                                  
 
                                  Here are some benefits that you get:
                                  
 
                                    
-
                                  1. Same system on iOS and Android.
                                    2. 
+
                                  2. Same system on Android and iOS.
                                    3. 
 
                                  3. Images live in the same folder as your JavaScript code. Components are self-contained.
                                    4. 
 
                                  4. No global namespace, i.e. you don't have to worry about name collisions.
                                    5. 
 
                                  5. Only the images that are actually used will be packaged into your app.
                                    6. 
diff --git a/docs/0.9/navigation.html b/docs/0.9/navigation.html
index dc149a463ca..58dac97dba3 100644
--- a/docs/0.9/navigation.html
+++ b/docs/0.9/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                                  Edit
                                  Navigating Between Screens
                                  Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                                  
-
                                  This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                                  
-
                                  If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                  
+
                                  This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                                  
+
                                  If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                  
 
                                  React Navigation
                                  
 
                                  The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                                  
 
                                  The first step is to install in your project:
                                  
diff --git a/docs/0.9/navigation/index.html b/docs/0.9/navigation/index.html
index dc149a463ca..58dac97dba3 100644
--- a/docs/0.9/navigation/index.html
+++ b/docs/0.9/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                                  Edit
                                  Navigating Between Screens
                                  Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                                  
-
                                  This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                                  
-
                                  If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                  
+
                                  This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                                  
+
                                  If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                                  
 
                                  React Navigation
                                  
 
                                  The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                                  
 
                                  The first step is to install in your project:
                                  
diff --git a/docs/0.9/navigator.html b/docs/0.9/navigator.html
index 92c8a7e9464..d24018e9ef1 100644
--- a/docs/0.9/navigator.html
+++ b/docs/0.9/navigator.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                                  Edit
                                  Navigator
                                  Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                  
+        
                                  Edit
                                  Navigator
                                  Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                  
 
                                  To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                                  
 
                                  import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.9/navigator/index.html b/docs/0.9/navigator/index.html
index 92c8a7e9464..d24018e9ef1 100644
--- a/docs/0.9/navigator/index.html
+++ b/docs/0.9/navigator/index.html
@@ -1,4 +1,4 @@
-Navigator · React Native
                                  Edit
                                  Navigator
                                  Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both iOS and Android. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                  
+        
                                  Edit
                                  Navigator
                                  Navigator handles the transition between different scenes in your app. It is implemented in JavaScript and is available on both Android and iOS. If you are targeting iOS only, you may also want to consider using NavigatorIOS as it leverages native UIKit navigation.
                                  
 
                                  To set up the Navigator you provide one or more objects called routes, to identify each scene. You also provide a renderScene function that renders the scene for each route object.
                                  
 
                                  import React, {Component} from 'react';
 import {Text, Navigator, TouchableHighlight} from 'react-native';
diff --git a/docs/0.9/picker.html b/docs/0.9/picker.html
index e04ab01eba2..a4b26fefe3c 100644
--- a/docs/0.9/picker.html
+++ b/docs/0.9/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                                  0.9
                                  Edit
                                  Picker
                                  Renders the native picker component on iOS and Android. Example:
                                  
+        
                                  0.9
                                  Edit
                                  Picker
                                  Renders the native picker component on Android and iOS. Example:
                                  
 
                                  <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.9/picker/index.html b/docs/0.9/picker/index.html
index e04ab01eba2..a4b26fefe3c 100644
--- a/docs/0.9/picker/index.html
+++ b/docs/0.9/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                                  0.9
                                  Edit
                                  Picker
                                  Renders the native picker component on iOS and Android. Example:
                                  
+        
                                  0.9
                                  Edit
                                  Picker
                                  Renders the native picker component on Android and iOS. Example:
                                  
 
                                  <Picker
   selectedValue={this.state.language}
   onValueChange={(itemValue, itemIndex) => this.setState({language: itemValue})}>
diff --git a/docs/0.9/platform-specific-code.html b/docs/0.9/platform-specific-code.html
index e7c170e2217..d1229e9b395 100644
--- a/docs/0.9/platform-specific-code.html
+++ b/docs/0.9/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                                  Edit
                                  Platform Specific Code
                                  When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                                  
+        
                                  Edit
                                  Platform Specific Code
                                  When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                                  
 
                                  React Native provides two ways to organize your code and separate it by platform:
                                  
 
                                    
 
                                  • Using the Platform module.
                                    • 
diff --git a/docs/0.9/platform-specific-code/index.html b/docs/0.9/platform-specific-code/index.html
index e7c170e2217..d1229e9b395 100644
--- a/docs/0.9/platform-specific-code/index.html
+++ b/docs/0.9/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                                  Edit
                                  Platform Specific Code
                                  When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                                  
+        
                                  Edit
                                  Platform Specific Code
                                  When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                                  
 
                                  React Native provides two ways to organize your code and separate it by platform:
                                  
 
                                    
 
                                  • Using the Platform module.
                                    • 
diff --git a/docs/accessibility.html b/docs/accessibility.html
index ac5a2b091e3..61941d97fd2 100644
--- a/docs/accessibility.html
+++ b/docs/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                                  Edit
                                  Accessibility
                                  Native App Accessibility (iOS and Android)
                                  
-
                                  Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                  
+        
                                  Edit
                                  Accessibility
                                  Native App Accessibility (Android and iOS)
                                  
+
                                  Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                  
 
                                  In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                                  
 
                                  Making Apps Accessible
                                  
 
                                  Accessibility properties
                                  
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                                  
-
                                  ← AnimationsImproving User Experience →
                                  Edit
                                  Accessibility
                                  Native App Accessibility (iOS and Android)
                                  
-
                                  Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                  
+        
                                  Edit
                                  Accessibility
                                  Native App Accessibility (Android and iOS)
                                  
+
                                  Both Android and iOS provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                                  
 
                                  In addition to this documentation, you might find this blog post about React Native accessibility to be useful.
                                  
 
                                  Making Apps Accessible
                                  
 
                                  Accessibility properties
                                  
@@ -307,7 +307,7 @@ adb shell settings put secure enabled_accessi
 # enable
 adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
 
                                  
-
                                  ← AnimationsImproving User Experience →
                                  Edit
                                  Alert
                                  Launches an alert dialog with the specified title and message.
                                  
 
                                  Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
                                  
-
                                  This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                                  
+
                                  This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                                  
 
                                  Example
                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/alert/index.html b/docs/alert/index.html
index 0e893ada0b5..62fc721b6a5 100644
--- a/docs/alert/index.html
+++ b/docs/alert/index.html
@@ -70,7 +70,7 @@
             });
         
                      Edit
                      Alert
                      Launches an alert dialog with the specified title and message.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
 
                      Example
                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/clipboard.html b/docs/clipboard.html
index ada7df44a03..86dadea2932 100644
--- a/docs/clipboard.html
+++ b/docs/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      
 
                      Reference
                      
 
                      Methods
                      
diff --git a/docs/clipboard/index.html b/docs/clipboard/index.html
index ada7df44a03..86dadea2932 100644
--- a/docs/clipboard/index.html
+++ b/docs/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      
 
                      Reference
                      
 
                      Methods
                      
diff --git a/docs/components-and-apis.html b/docs/components-and-apis.html
index d55c2f6a86c..4540c1edf1a 100644
--- a/docs/components-and-apis.html
+++ b/docs/components-and-apis.html
@@ -130,7 +130,7 @@
   
                      
     
       
                      Picker
                      
-      
                      Renders the native picker component on iOS and Android.
                      
+      
                      Renders the native picker component on Android and iOS.
                      
                           
   
                      
   
                      
@@ -290,7 +290,7 @@
   
                      
     
       
                      Clipboard
                      
-      
                      Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                      
+      
                      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                      
                           
   
                      
   
                      
diff --git a/docs/components-and-apis/index.html b/docs/components-and-apis/index.html
index d55c2f6a86c..4540c1edf1a 100644
--- a/docs/components-and-apis/index.html
+++ b/docs/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                      
     
       
                      Picker
                      
-      
                      Renders the native picker component on iOS and Android.
                      
+      
                      Renders the native picker component on Android and iOS.
                      
                           
   
                      
   
                      
@@ -290,7 +290,7 @@
   
                      
     
       
                      Clipboard
                      
-      
                      Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                      
+      
                      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                      
                           
   
                      
   
                      
diff --git a/docs/getting-started.html b/docs/getting-started.html
index 2014b161df1..d335aa9db5a 100644
--- a/docs/getting-started.html
+++ b/docs/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                      
 
                      
 
                      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                      
-
                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                      
+
                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                      
 
                      
   Development OS:
   
diff --git a/docs/getting-started/index.html b/docs/getting-started/index.html
index 2014b161df1..d335aa9db5a 100644
--- a/docs/getting-started/index.html
+++ b/docs/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                      
 
                      
 
                      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                      
-
                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                      
+
                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                      
 
                      
   Development OS:
   
diff --git a/docs/images.html b/docs/images.html
index ade142370cc..3ce865824bc 100644
--- a/docs/images.html
+++ b/docs/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                      Edit
                      Images
                      Static Image Resources
                      
-
                      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                      
+
                      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                      
 
                      <Image source={require('./my-icon.png')} />
 
                      
 
                      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                      
@@ -88,7 +88,7 @@
 
                      On Windows, you might need to restart the packager if you add new images to your project.
                      
 
                      Here are some benefits that you get:
                      
 
                        
-
                      1. Same system on iOS and Android.
                        2. 
+
                      2. Same system on Android and iOS.
                        3. 
 
                      3. Images live in the same folder as your JavaScript code. Components are self-contained.
                        4. 
 
                      4. No global namespace, i.e. you don't have to worry about name collisions.
                        5. 
 
                      5. Only the images that are actually used will be packaged into your app.
                        6. 
diff --git a/docs/images/index.html b/docs/images/index.html
index ade142370cc..3ce865824bc 100644
--- a/docs/images/index.html
+++ b/docs/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                      Edit
                      Images
                      Static Image Resources
                      
-
                      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                      
+
                      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                      
 
                      <Image source={require('./my-icon.png')} />
 
                      
 
                      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                      
@@ -88,7 +88,7 @@
 
                      On Windows, you might need to restart the packager if you add new images to your project.
                      
 
                      Here are some benefits that you get:
                      
 
                        
-
                      1. Same system on iOS and Android.
                        2. 
+
                      2. Same system on Android and iOS.
                        3. 
 
                      3. Images live in the same folder as your JavaScript code. Components are self-contained.
                        4. 
 
                      4. No global namespace, i.e. you don't have to worry about name collisions.
                        5. 
 
                      5. Only the images that are actually used will be packaged into your app.
                        6. 
diff --git a/docs/navigation.html b/docs/navigation.html
index 5b021c58932..ae013ec5f73 100644
--- a/docs/navigation.html
+++ b/docs/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                      Edit
                      Navigating Between Screens
                      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                      
-
                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                      
-
                      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                      
+
                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                      
+
                      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                      
 
                      React Navigation
                      
 
                      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                      
 
                      The first step is to install in your project:
                      
diff --git a/docs/navigation/index.html b/docs/navigation/index.html
index 5b021c58932..ae013ec5f73 100644
--- a/docs/navigation/index.html
+++ b/docs/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                      Edit
                      Navigating Between Screens
                      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                      
-
                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                      
-
                      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                      
+
                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                      
+
                      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                      
 
                      React Navigation
                      
 
                      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                      
 
                      The first step is to install in your project:
                      
diff --git a/docs/next/accessibility.html b/docs/next/accessibility.html
index 5f480a2550b..7e543fd3772 100644
--- a/docs/next/accessibility.html
+++ b/docs/next/accessibility.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                      Edit
                      Accessibility
                      Both iOS and Android provide APIs for integrating apps with assitive technologies like the bundled screen readers VoiceOver (iOS) and Talkback (Android). React Native has complimentary APIs that let your app accommodate all users.
                      
+        
                      Edit
                      Accessibility
                      Both Android and iOS provide APIs for integrating apps with assitive technologies like the bundled screen readers VoiceOver (iOS) and Talkback (Android). React Native has complimentary APIs that let your app accommodate all users.
                      
 
                      
-
                      iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
+
                      Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
 
                      
 
                      Accessibility properties
                      
 
                      accessible (iOS, Android)
                      
diff --git a/docs/next/accessibility/index.html b/docs/next/accessibility/index.html
index 5f480a2550b..7e543fd3772 100644
--- a/docs/next/accessibility/index.html
+++ b/docs/next/accessibility/index.html
@@ -1,4 +1,4 @@
-Accessibility · React Native
                      Edit
                      Accessibility
                      Both iOS and Android provide APIs for integrating apps with assitive technologies like the bundled screen readers VoiceOver (iOS) and Talkback (Android). React Native has complimentary APIs that let your app accommodate all users.
                      
+        
                      Edit
                      Accessibility
                      Both Android and iOS provide APIs for integrating apps with assitive technologies like the bundled screen readers VoiceOver (iOS) and Talkback (Android). React Native has complimentary APIs that let your app accommodate all users.
                      
 
                      
-
                      iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
+
                      Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
                      
 
                      
 
                      Accessibility properties
                      
 
                      accessible (iOS, Android)
                      
diff --git a/docs/next/alert.html b/docs/next/alert.html
index 2af2de0a568..4b44beaec57 100644
--- a/docs/next/alert.html
+++ b/docs/next/alert.html
@@ -70,7 +70,7 @@
             });
         
                      Edit
                      Alert
                      Launches an alert dialog with the specified title and message.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
 
                      Example
                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/next/alert/index.html b/docs/next/alert/index.html
index 2af2de0a568..4b44beaec57 100644
--- a/docs/next/alert/index.html
+++ b/docs/next/alert/index.html
@@ -70,7 +70,7 @@
             });
         
                      Edit
                      Alert
                      Launches an alert dialog with the specified title and message.
                      
 
                      Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
                      
-
                      This is an API that works both on iOS and Android and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
+
                      This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see AlertIOS; entering text in an alert is common on iOS only.
                      
 
                      Example
                      @@ -98,7 +98,7 @@

                      By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.

                      Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }

                      Example usage:

                      -
                      // Works on both iOS and Android
+
                      // Works on both Android and iOS
 Alert.alert(
   'Alert Title',
   'My Alert Msg',
diff --git a/docs/next/clipboard.html b/docs/next/clipboard.html
index da78717f167..5d16ae7b034 100644
--- a/docs/next/clipboard.html
+++ b/docs/next/clipboard.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      
 
                      Reference
                      
 
                      Methods
                      
diff --git a/docs/next/clipboard/index.html b/docs/next/clipboard/index.html
index da78717f167..5d16ae7b034 100644
--- a/docs/next/clipboard/index.html
+++ b/docs/next/clipboard/index.html
@@ -1,4 +1,4 @@
-Clipboard · React Native
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both iOS and Android
                      
+        
                      Edit
                      Clipboard
                      Clipboard gives you an interface for setting and getting content from Clipboard on both Android and iOS
                      
 
                      
 
                      Reference
                      
 
                      Methods
                      
diff --git a/docs/next/components-and-apis.html b/docs/next/components-and-apis.html
index f728e44f975..d22a7834593 100644
--- a/docs/next/components-and-apis.html
+++ b/docs/next/components-and-apis.html
@@ -130,7 +130,7 @@
   
                      
     
       
                      Picker
                      
-      
                      Renders the native picker component on iOS and Android.
                      
+      
                      Renders the native picker component on Android and iOS.
                      
                           
   
                      
   
                      
@@ -290,7 +290,7 @@
   
                      
     
       
                      Clipboard
                      
-      
                      Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                      
+      
                      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                      
                           
   
                      
   
                      
diff --git a/docs/next/components-and-apis/index.html b/docs/next/components-and-apis/index.html
index f728e44f975..d22a7834593 100644
--- a/docs/next/components-and-apis/index.html
+++ b/docs/next/components-and-apis/index.html
@@ -130,7 +130,7 @@
   
                      
     
       
                      Picker
                      
-      
                      Renders the native picker component on iOS and Android.
                      
+      
                      Renders the native picker component on Android and iOS.
                      
                           
   
                      
   
                      
@@ -290,7 +290,7 @@
   
                      
     
       
                      Clipboard
                      
-      
                      Provides an interface for setting and getting content from the clipboard on both iOS and Android.
                      
+      
                      Provides an interface for setting and getting content from the clipboard on both Android and iOS.
                      
                           
   
                      
   
                      
diff --git a/docs/next/getting-started.html b/docs/next/getting-started.html
index f09f7873e3f..63b21719be4 100644
--- a/docs/next/getting-started.html
+++ b/docs/next/getting-started.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                      
 
                      
 
                      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                      
-
                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                      
+
                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                      
 
                      
   Development OS:
   
diff --git a/docs/next/getting-started/index.html b/docs/next/getting-started/index.html
index f09f7873e3f..63b21719be4 100644
--- a/docs/next/getting-started/index.html
+++ b/docs/next/getting-started/index.html
@@ -118,7 +118,7 @@ npm start # you can also use: expo start
 
                      If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
                      
 
                      
 
                      Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
                      
-
                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you can pick one to start with, since the setup is a bit different.
                      
+
                      The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
                      
 
                      
   Development OS:
   
diff --git a/docs/next/images.html b/docs/next/images.html
index 3bbe4edc0a3..4dbaf7aa2c5 100644
--- a/docs/next/images.html
+++ b/docs/next/images.html
@@ -69,7 +69,7 @@
               }
             });
         
                      Edit
                      Images
                      Static Image Resources
                      
-
                      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                      
+
                      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                      
 
                      <Image source={require('./my-icon.png')} />
 
                      
 
                      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                      
@@ -88,7 +88,7 @@
 
                      On Windows, you might need to restart the packager if you add new images to your project.
                      
 
                      Here are some benefits that you get:
                      
 
                        
-
                      1. Same system on iOS and Android.
                        2. 
+
                      2. Same system on Android and iOS.
                        3. 
 
                      3. Images live in the same folder as your JavaScript code. Components are self-contained.
                        4. 
 
                      4. No global namespace, i.e. you don't have to worry about name collisions.
                        5. 
 
                      5. Only the images that are actually used will be packaged into your app.
                        6. 
diff --git a/docs/next/images/index.html b/docs/next/images/index.html
index 3bbe4edc0a3..4dbaf7aa2c5 100644
--- a/docs/next/images/index.html
+++ b/docs/next/images/index.html
@@ -69,7 +69,7 @@
               }
             });
         
                      Edit
                      Images
                      Static Image Resources
                      
-
                      React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                      
+
                      React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
                      
 
                      <Image source={require('./my-icon.png')} />
 
                      
 
                      The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for my-icon.png in the same folder as the component that requires it. Also, if you have my-icon.ios.png and my-icon.android.png, the packager will pick the correct file for the platform.
                      
@@ -88,7 +88,7 @@
 
                      On Windows, you might need to restart the packager if you add new images to your project.
                      
 
                      Here are some benefits that you get:
                      
 
                        
-
                      1. Same system on iOS and Android.
                        2. 
+
                      2. Same system on Android and iOS.
                        3. 
 
                      3. Images live in the same folder as your JavaScript code. Components are self-contained.
                        4. 
 
                      4. No global namespace, i.e. you don't have to worry about name collisions.
                        5. 
 
                      5. Only the images that are actually used will be packaged into your app.
                        6. 
diff --git a/docs/next/navigation.html b/docs/next/navigation.html
index 08805a7e2ea..8505246b107 100644
--- a/docs/next/navigation.html
+++ b/docs/next/navigation.html
@@ -69,8 +69,8 @@
               }
             });
         
                      Edit
                      Navigating Between Screens
                      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                      
-
                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                      
-
                      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                      
+
                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                      
+
                      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                      
 
                      React Navigation
                      
 
                      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                      
 
                      The first step is to install in your project:
                      
diff --git a/docs/next/navigation/index.html b/docs/next/navigation/index.html
index 08805a7e2ea..8505246b107 100644
--- a/docs/next/navigation/index.html
+++ b/docs/next/navigation/index.html
@@ -69,8 +69,8 @@
               }
             });
         
                      Edit
                      Navigating Between Screens
                      Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
                      
-
                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
                      
-
                      If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                      
+
                      This guide covers the various navigation components available in React Native. If you are getting started with navigation, you will probably want to use React Navigation. React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
                      
+
                      If you'd like to achieve a native look and feel on both Android and iOS, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: react-native-navigation.
                      
 
                      React Navigation
                      
 
                      The community solution to navigation is a standalone library that allows developers to set up the screens of an app with a few lines of code.
                      
 
                      The first step is to install in your project:
                      
diff --git a/docs/next/picker.html b/docs/next/picker.html
index 8a43df166ee..99c5417db3a 100644
--- a/docs/next/picker.html
+++ b/docs/next/picker.html
@@ -1,4 +1,4 @@
-Picker · React Native
                      Edit
                      Picker
                      Renders the native picker component on iOS and Android. Example:
                      
+        
                      Edit
                      Picker
                      Renders the native picker component on Android and iOS. Example:
                      
 
                      <Picker
   selectedValue={this.state.language}
   style={{height: 50, width: 100}}
diff --git a/docs/next/picker/index.html b/docs/next/picker/index.html
index 8a43df166ee..99c5417db3a 100644
--- a/docs/next/picker/index.html
+++ b/docs/next/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                      Edit
                      Picker
                      Renders the native picker component on iOS and Android. Example:
                      
+        
                      Edit
                      Picker
                      Renders the native picker component on Android and iOS. Example:
                      
 
                      <Picker
   selectedValue={this.state.language}
   style={{height: 50, width: 100}}
diff --git a/docs/next/platform-specific-code.html b/docs/next/platform-specific-code.html
index f4b8af65c34..2187a528dea 100644
--- a/docs/next/platform-specific-code.html
+++ b/docs/next/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                      Edit
                      Platform Specific Code
                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                      
+        
                      Edit
                      Platform Specific Code
                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                      
 
                      React Native provides two ways to organize your code and separate it by platform:
                      
 
                        
 
                      • Using the Platform module.
                        • 
diff --git a/docs/next/platform-specific-code/index.html b/docs/next/platform-specific-code/index.html
index f4b8af65c34..2187a528dea 100644
--- a/docs/next/platform-specific-code/index.html
+++ b/docs/next/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                      Edit
                      Platform Specific Code
                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                      
+        
                      Edit
                      Platform Specific Code
                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                      
 
                      React Native provides two ways to organize your code and separate it by platform:
                      
 
                        
 
                      • Using the Platform module.
                        • 
diff --git a/docs/next/text.html b/docs/next/text.html
index aad15433e76..8c91a73c877 100644
--- a/docs/next/text.html
+++ b/docs/next/text.html
@@ -121,7 +121,7 @@
           width: 100%;
         "
       >
                      Nested text
                      
-
                      Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                      
+
                      Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                      
 
                      Nested text
                      
-
                      Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                      
+
                      Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                      
 
                      Edit
                      Picker
                      Renders the native picker component on iOS and Android. Example:
                      
+        
                      Edit
                      Picker
                      Renders the native picker component on Android and iOS. Example:
                      
 
                      <Picker
   selectedValue={this.state.language}
   style={{height: 50, width: 100}}
diff --git a/docs/picker/index.html b/docs/picker/index.html
index 73b9df9da82..7bcb2d478cb 100644
--- a/docs/picker/index.html
+++ b/docs/picker/index.html
@@ -1,4 +1,4 @@
-Picker · React Native
                      Edit
                      Picker
                      Renders the native picker component on iOS and Android. Example:
                      
+        
                      Edit
                      Picker
                      Renders the native picker component on Android and iOS. Example:
                      
 
                      <Picker
   selectedValue={this.state.language}
   style={{height: 50, width: 100}}
diff --git a/docs/platform-specific-code.html b/docs/platform-specific-code.html
index 678d6507450..3feda0ef334 100644
--- a/docs/platform-specific-code.html
+++ b/docs/platform-specific-code.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                      Edit
                      Platform Specific Code
                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                      
+        
                      Edit
                      Platform Specific Code
                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                      
 
                      React Native provides two ways to organize your code and separate it by platform:
                      
 
                        
 
                      • Using the Platform module.
                        • 
diff --git a/docs/platform-specific-code/index.html b/docs/platform-specific-code/index.html
index 678d6507450..3feda0ef334 100644
--- a/docs/platform-specific-code/index.html
+++ b/docs/platform-specific-code/index.html
@@ -1,4 +1,4 @@
-Platform Specific Code · React Native
                      Edit
                      Platform Specific Code
                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for iOS and Android.
                      
+        
                      Edit
                      Platform Specific Code
                      When building a cross-platform app, you'll want to re-use as much code as possible. Scenarios may arise where it makes sense for the code to be different, for example you may want to implement separate visual components for Android and iOS.
                      
 
                      React Native provides two ways to organize your code and separate it by platform:
                      
 
                        
 
                      • Using the Platform module.
                        • 
diff --git a/docs/text.html b/docs/text.html
index c73cdf09091..c8ce224a788 100644
--- a/docs/text.html
+++ b/docs/text.html
@@ -121,7 +121,7 @@
           width: 100%;
         "
       >
                      Nested text
                      
-
                      Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                      
+
                      Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                      
 
                      Nested text
                      
-
                      Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
                      
+
                      Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.