@brentvatne
Nothing here yet.
Nothing here yet.
No blogs yet.
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!
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 Andrés! We're considering this. I am personally (not speaking for the team) not convinced that we need it, and I do not like having to integrate native APIs that are specific to a particular vendor (when we can avoid it). That said, there is clearly a lot of demand for Firebase (as per https://expo.canny.io/feature-requests). You can use the JS SDK for the database, authentication, and very shortly for storage (this will be available in March).