Update 2018-08-0.27.md

website/src/_posts/2018-08-0.27.md

@@ -1,5 +1,5 @@
 ---
-title: "Uppy 0.27: Dashboard without tabs, autoProceed: false by default, work on React Native"
+title: "Uppy 0.27: First Swing at React Native Support"
 date: 2018-08-23
 author: ife
 image: "https://uppy.io/images/blog/0.27/uppy-add-initial.jpg"
@@ -13,7 +13,7 @@ In `0.27` we are iterating on the Dashboard UI again (getting rid of the permane
 
 ## Dashboard UI without tabs
 
-Uppy used to always display the tab bar (the one you use to select between importing files from Instagram, Webcam, local disk, etc). This was not working well when many providers with the growing list of sources we support, especially on mobile.
+Uppy used to always display the tab bar (the one you use to select between importing files from Instagram, Webcam, local disk, etc). This was not working well with the growing list of sources we support, especially on mobile.
 
 <img src="/images/blog/0.27/uppy-with-tabs.jpg">
 
@@ -21,7 +21,7 @@ So in `0.27` we are iterating on the UI again:
 
 <img src="/images/blog/0.27/uppy-add-initial.jpg">
 
-The list of icons is visible on the initial screen (plus, we’ve added colors!), but when you complete the inital selection, it’s hidden behind the “plus” button:
+The providers are now visible as a list of icons on the initial screen (plus, we’ve added colors!), but when you complete the inital selection, it’s hidden behind the “plus” button:
 
 <img src="/images/blog/0.27/uppy-files-selected.jpg">
 
@@ -37,9 +37,9 @@ The StatusBar that shows progress has been “lightened”:
 
 Informer messages now always appear in a gray round bubble, we’ve dropped the multiple color support. Plus tons of small fixes like better animations, colors, font sizes and more, [check out the PR #942](https://github.com/transloadit/uppy/pull/942) for details.
 
-We are aiming to make the UI less heavy, so that Uppy can easier fit within your excisting site or app design.
+We are aiming to make the UI less heavy, so that Uppy can easier fit within your existing site or app design.
 
-Mobile version is now much nicer as well:
+The mobile version is now much more refined as well:
 
 <img src="/images/blog/0.27/uppy-mobile.jpg">
 
@@ -56,35 +56,39 @@ By default, Uppy used to begin uploading right after you selected a file. If you
 const uppy = Uppy({ autoProceed: false })
 ```
 
-Since in most cases we actually wanted `autoProceed: false`, this is now the new default. Make sure you changes this in your project if needed. If you weren't setting an `autoProceed` option at all, you'll now have to add `autoProceed: true`.
+Since in most cases we actually wanted `autoProceed: false`, this is now the new default. That makes Uppy's UI less magical and harder to make irreversible mistakes with, by default. Make sure you change this in your project if needed. If you weren't setting an `autoProceed` option at all, you'll now have to add `autoProceed: true`.
 
 ## Progress on React Native
 
-We’ve begun working on supporting React Native in Uppy. Since `0.27` it should run in React Native environment — meaning you can use Uppy API (`uppy.addFile()`, `uppy.upload()`) for adding files and uploading, without the UI. `@uppy/xhr-upload` uploader is already supported, and we are working on making `@uppy/tus`(and `tus-js-client` itself) run in React Native too.
+We’ve begun working on supporting React Native in Uppy. Since `0.27` it should run in a React Native environment — meaning you can use Uppy API (`uppy.addFile()`, `uppy.upload()`) for adding files and uploading, without the UI. `@uppy/xhr-upload` uploader is already supported, and we are working on making `@uppy/tus`(and `tus-js-client` itself) run in React Native too.
 
-Next we plan to make sure all non-UI Uppy plugins work in RN, and then provide useful components for adding Uppy to your RN apps.
+We plan to make sure all non-UI Uppy plugins work in RN, and then provide a few useful components for adding Uppy to your RN apps.
 
 Please head the [React Native PR #988](https://github.com/transloadit/uppy/pull/988), for details and let us know what you think, and how we could improve the Uppy React Native experience.
 
+Built-in React Native support has been a 1.0 goal from the start. We've had many requests about Angular.js and Vue support. There are already community built solutions for these platforms that seem to work well, but unfortunately we won't be officially supporting them before our 1.0 milestone. Depending on community input we might add that later.
+
 ## Package sizes
 
 We now have a cool table showing mingzipped bundle sizes for each individual Uppy package, [check it out](https://uppy.io/docs/stats/#bundle-sizes):
 
 <img width="400" src="/images/blog/0.27/uppy-sizes.png">
 
-## Uppy Server is now Companion
+## "Uppy Server" is now "Companion"
 
 ```bash
 npm install @uppy/companion
 ```
 
-Uppy Server is an optional service that Uppy can use to import files from sources like Instagram or Dropbox. However simply naming it "Server" was quite unclear and has caused confusion. Many people thought you could upload files to Uppy Server, as well, but that's not the case. So, we're renaming it to Companion: an optional tool you can use to add more functionality to your Uppy uploader.
+Uppy Server is an optional service that Uppy can use to import files from sources like Instagram or Dropbox. However simply naming it "Server" was quite unclear and has caused confusion. Many people thought you could upload files to Uppy Server as well, but that's not the case. We recommend uploading to a [tus.io](https://tus.io) server, and if that's too much for your simple usecase, use your existing webserver to handle the upload. 
+
+So, we're renaming it to Companion: an optional tool in the datacenter you can use to add more functionality to your Uppy js client.
 
-Simultaneously we moved Uppy Companion into the main [transloadit/uppy](https://github.com/transloadit/uppy) monorepo. This centralizes Uppy issue reporting, and makes it easier to do updates and simultaneous releases of the client and Companion parts.
+Simultaneously we moved Uppy Companion into the main [transloadit/uppy](https://github.com/transloadit/uppy) [monorepo](https://github.com/babel/babel/blob/master/doc/design/monorepo.md). This centralizes Uppy issue reporting, and makes it easier to do updates and simultaneous releases of the client and Companion parts.
 
 The first release of `@uppy/companion` is 0.14, and the last `uppy-server` release is 0.13.4. `uppy-server` will be deprecated on npm soon.
 
-Note that despite the rename, configuration for standalone Companion still uses `UPPYSERVER_` environment variables. This should ease the transition, since you'll only have to update the package name for now. `COMPANION_` variables will be used instead in the future, of course we'll notify you when the time comes!
+Note that despite the rename, configuration for standalone Companion still uses `UPPYSERVER_` environment variables. This should ease the transition, since you'll only have to update the package name for now. Once we add `COMPANION_` variable support, we'll continue to support `UPPYSERVER_` environment variables to smoothen the transition. And of course we'll notify you here when that time comes!
 
 ## Other Cool Changes