Popular posts

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: 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.

Bluetooth is near the top of our list but its complicated for a few reasons so that's why it's not done yet. (a) The Bluetooth stacks on iOS and Android are pretty different so its not easy or obvious how to unify those, and (a2) the native APIs are pretty imperative and stateful and we'll probably need to map that onto something declarative so it can work over an async bridge to work with RN (b) The use cases for Bluetooth vary widely--from BLE stuff to paired, etc., etc., (c) Bluetooth usage will typically involve stuff happening in the background, and we're still putting together background task support (though it should be available soon!)

re: Making APIs available outside of Expo. We might do this! It would definitely be nice in some ways but doing that might hamper our ability to do other things well. It's something we talk about a lot, but in the context of many other considerations and plans for the future architecture of Expo.