Support React 16.8.0 aka Hooks
Now that React merged the Hooks feature it will soon be released. The API is such a nice enhancement for structuring code that I can't wait to start using it. Besides being a nice tool Hooks will also replace [recompose](https://github.com/acdlite/recompose) and a lot of messy HoC patterns. The latter is particularly relevant when using Typescript, since proper typing is sometimes hard or impossible to achieve. For example [typesafe inject for MobX](https://github.com/mobxjs/mobx-react/issues/256)
In App Purchases
Moved from: https://github.com/expo/expo/issues/11 Add support for in app purchases to standalone apps on iOS and Android
Add react-native-ffmpeg to Expo for video manupulations. Link to npm: https://www.npmjs.com/package/react-native-ffmpeg
Similar to the API provided by https://github.com/Polidea/react-native-ble-plx I work on a bluetooth connected medical device and have been using that library to do most of the bluetooth stuff. However, you must detach the expo app to get it working and the setup is non-trivial. It would be nice to have a bluetooth API built into the expo SDK.
Expo init - typescript
Expo init command in CLI has only two options to create project. Blank project and something with React Navigation. It would be nice, it there will be third option -> Typescript. It will create same project as blank one, but it will have tsconfig.json and some necessary things, which are required (and/or) useful. (For example, I don't know, if I need package tslib). Some Babel configuration, when TS is natively supported Some inspiration: https://github.com/rauldeheer/expo-typescript or https://github.com/janaagaard75/expo-and-typescript
Add Mapbox GL support
Mapbox recently released it's React Native SDK(react-native-mapbox-gl), would be great to get this in Expo.
Auto increment buildNumber(iOS) and versionCode(Android)
Currently, if we ever forget to increment the buildNumber or versionCode, the only point of time when we realize is when we are almost done uploading our APK or IPA file. That's when we are shown the error. This wastes a lot of time. Requesting expo team to add an optional argument to expo build command which automatically increments the buildNumber and versionCode. Or else, we should be shown a warning message when trying to build with same version code, and asked whether we want to continue or increment. Thanks. Hope it is implemented soon.