4 ms·
This looks very interesting, but I'd like to know that if I ever did need to fall back to native APIs, I could keep the code I've written using Exponent's APIs
by jameslk 10y ago
This looks very interesting, but I'd like to know that if I ever did need to fall back to native APIs, I could keep the code I've written using Exponent's APIs still (even if that means I couldn't use the convenient build tools anymore). Is this possible?
- nikki93 10y agoYup! Since our client code is open source, you could run a custom fork of our client that includes the native module(s) you want and still use the JavaScript app code you've written with it. If you end up making such a change let us know and through a pull request or such we could try getting it into standard Exponent!
- brentvatne 10y agoThere are a few of ways to do this right now: - Fork the Exponent client and add your native API. - Try to get a patch into upstream. - If it's not urgent, ask us if we plan to implement it and if it seems like a common enough use case we would add it to our roadmap. - Go into the Exponent source and copy whatever native code you need into a new React Native project. We're also working on a way to "eject" from Exponent similar to the create-react-app eject command but easier to reverse and to keep receiving updates to Exponent, because it's not an "all-in" kind of eject, you can read more about that here: https://blog.getexponent.com/answered-on-slack-ejecting-from-exponent-154bdca57dc1#.yr55mmqtc https://blog.getexponent.com/answered-on-slack-ejecting-from... (caveat: this feature is still in early development)
- skanga 10y agoDoes it support Bluetooth LE communications?