We need this feature for both of the platforms. This is an essential feature. Expo must add this to its' built-in modules: https://github.com/alinz/react-native-share-extension [1] https://developer.android.com/training/sharing/send [2] https://developer.apple.com/library/archive/documentation/General/Conceptual/ExtensibilityPG/Share.html#//apple_ref/doc/uid/TP40014214-CH12-SW1

It would be great if we could run tasks on other threads in Expo using this package for example: https://github.com/mrousavy/react-native-multithreading

Expo generally lags well behind on React Native, but I'm hoping that won't mean a multi-year wait for React 18 support.

I'd love the ability to have images in push notifications! We're an image-centric messaging app, so rich pushes would go a long way for us.

Moved from: https://github.com/expo/expo/issues/11 Add support for in app purchases to standalone apps on iOS and Android in the managed workflow Status as of May 3, 2021: We are working on supporting native plugins in Expo managed apps, you can read about it here: https://blog.expo.io/expo-managed-workflow-in-2021-d1c9b68aa10 - but it's not ready yet. ------------------------------ Status as of July 21, 2020: The same as the previous status update applies here. We are still building the infrastructure that we need to be able to support IAPs in the managed workflow. If you need them, I recommend ejecting to the bare workflow. You can continue to use all of the Expo SDK packages after ejecting, including OTA updates and Notifications. https://docs.expo.io/workflow/customizing/ ------------------------------ Status as of April 14, 2020: IAP APIs in the managed workflow will not be available until we have completed support for native plugins in the managed workflow, which is part of our rewrite of the build service. You may want to consider using bare workflow for now! You can continue to use Updates and Notifications in bare React Native apps now as of SDK 37: https://blog.expo.io/expo-sdk-37-is-now-available-dd5770f066a6 . ------------------------------ Status as of November 7, 2019: This feature is definitely important for us in the medium to long-term but we need to build some more infrastructure before it's possible. We're currently rewriting our build service to make it capable of handling adding In-App Purchase support to apps but it's not there yet.

Right now using detox with Expo isn't a great experience (IMHO), plus I get the feeling the detox team doesn't enjoy supporting expo. Fair enough for the wix team, it reduces their support requests but makes recommending detox unlikely. Having experienced the dizzying joys of cypress testing with expo-web, the greatest wish at our company would be for an expo e2e testing tool that lets us test native iOS/Android using expo! We'd happily pay for features like test recording, or test runner servers etc. Also, see React Native Radio podcast discussion from 26:30 ( https://www.reactnativeradio.com/episodes/180-testing-strategies-tools-and-frameworks ). I know others would love an expo blessed e2e testing solution!

When I'm viewing my experience's project page (as the owner), it'd be useful to see all release channels that exist, get the QR for that specific experience and maybe even delete any that should no longer exist. Same goes for the expo app - I should be able to load up any "version" of my app if multiple channels exist.

William Candillon presented a very cool react native Skia integration. https://www.youtube.com/watch?v=EHxEX78alZE This is amazing drawing library, and it would be nice if it will be in expo managed workflow.

Please add support for https://github.com/Nozbe/WatermelonDB WatermelonDB is a new way of dealing with user data in React Native and React web apps. It's optimized for building complex applications in React Native, and the number one goal is real-world performance. In simple words, your app must launch fast.

Prior to SDK 45 and the "new" dev client, development builds would automtaically build and download the app at the Metro URL configured in the RN debug settings. Now with expo-dev-launcher, the app loads the menu every time the app is loaded, forcing me to select the app, even if I only ever use the same one. This also creates some frustration with Hermes debugging not loading the "active" app, but rather the launcher app, e.g. the issue explored at https://github.com/expo/expo/issues/17355 and other general weirdness when trying to successfully use the Hermes Debugger.