I work from Vancouver, Canada but most of the team is in Palo Alto, California. My work day is a little different from theirs so I'll have to let someone else speak to this ;)

Yes, if you are based in USA then take a look at http://expo.io/jobs

Hi Saket! Are there any plans to support bluetooth and BLE via some Expo apis? We do plan on supporting this! It's a very popular feature request: https://expo.canny.io/feature-requests/p/bluetooth-api No timeline for it yet but we're making our way towards it. Any plans for Expo or some of your apis eventually becoming separate libraries so we can only use the parts we need Some users have started to do this , eg: react-native-camera is the Camera component extracted from the Expo codebase. As for only using the parts you need, we plan on making it possible to opt-in to only the APIs that you need in the build step, to help reduce the size of the binary. (even if at a extra cost per library)? No plans for charging for that.

react-native-gesture-handler - great gestures have never been so easy. react-native-vector-icons - of course react-native-animatable - super simple to drop in animations react-native-paper - still early for this but I'm excited for it! react-native-camera - we re-built this for Expo and people liked it so they pulled the native code out of Expo and into this library react-native-tab-view - excellent gl-react - it's good plenty more that I haven't listed here!

There's a lot of discussion around this here: https://expo.canny.io/feature-requests/p/native-plugins It's not clear to me what this would look like in practice. We have been considering making it possible to inject plugins in the build step ( exp build:ios/android ), but not the Expo client.

Yes this is possible with Expo! The native builds run on our servers, so when you run exp build:ios it builds your JS bundle and asset manifest, uploads them both to CloudFront, then kicks off a build job on MacStadium. When it's done, you can download the binary and upload it to iTunes (it may be possible to upload without a Mac, I am not entirely sure). This is only needed when you're ready to ship to the App Store, and before that the workflow is no different between a Mac and Windows when using Expo. Read more about this in our docs: https://docs.expo.io/versions/latest/distribution/index.html Using React Native without Expo, you can't really build for iOS without some likely painstaking workarounds involving provisioning your own mac cloud instance.

Hi Jake! How are features picked? We pay close attention to the feature requests: https://expo.canny.io/feature-requests . In addition to that, we conduct user interviews frequently, speak to businesses who may be interested in using it or who are using it, participate in hackathons, and we build apps with Expo ourselves to get a feel for what we think it needs. How do you discuss problems as a team? This is a tough question to answer! Not sure I can give a concise answer to this, sorry :( What other services do you use? Amplitude Segment Google Cloud Slack Dropbox Paper Canny Circle CI Buildkite GitHub (of course) waffle.io Twilio DoorDash :P Lyft Plenty of others..

Hi José! Yes we are planning on that. See my reply to Chris in https://hashnode.com/ama/with-expo-team-cjdqxyifm04hwt3wt80z47mf7#cjdum1yct02ism3wt65416ysk We've been working on infrastructure and refactoring necessary to support "optional modules" -- this would allow you to selectively opt in and out of APIs to include in your standalone app. We'd also let you select which versions of the Expo SDK to include -- usually this would just be the one version that you're using.

Hi Chris! Yes, this can absolutely be solved. We've been working on infrastructure and refactoring necessary to support "optional modules" -- this would allow you to selectively opt in and out of APIs to include in your standalone app. We'd also let you select which versions of the Expo SDK to include -- usually this would just be the one version that you're using. More info on versions in this reply: https://hashnode.com/ama/with-expo-team-cjdqxyifm04hwt3wt80z47mf7#cjdulxcq00579z0wufh2exvby

Hi Anant! This is going to be a boring answer but the truth is there is no one particular part that is / has been the most difficult. One difficult problem that comes to mind is handling versioning our native code elegantly. It's something that most people using Expo just take for granted, but there was a long period of time where the Expo client wasn't capable of doing this. The Expo client needs to support multiple versions of React Native in a single binary. If you built an app 6 months ago and want to use the Expo client to open it today, 6 releases later (we do monthly releases), it will still work. We include I believe 7 versions currently. Each of the APIs that Expo includes also needs to be versioned, and their dependencies.