Currently getThumbNailAsync blocks UI on iOS. This is because the AsyncFunction("getThumbnail", getVideoThumbnail).runOnQueue is set to main queue. This is a problem especially when network is bad and video does not get fetched. It would be great either to set dispatch queue to DispatchQueue.global (qos: .utility) or to create a new non-blocking version of getThumbnail dispatched on this queue

I've been using expo-camera since SDK 32. My experience with iOS is nice, but when it comes to Android... Such an essential component, with such poor performance on Android devices (even with API 2 and not-so-heavy processing), honestly, is something that puts you off. I know that there are other solutions such as migrating to react-native-camera-vision or other alternatives, but I feel that Expo, as it did with expo-image, should have a proper camera, in terms of performance. A 2 to 5 second delay when capturing a photo, or a drop in performance during processing is something that really puts me off. Do you plan to reimplement/drastically improve performance for Android in the near future? Thank you for your dedication to this amazing project.

There are a few react native packages for dynamic island support on iPhone 14 Pro and higher, but I don't believe there's any options for Expo specifically.

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.

Support iPad's multitasking features (Slide Over, Split View) in Expo standalone apps. According to the Apple documentation ( https://developer.apple.com/library/content/documentation/WindowsViews/Conceptual/AdoptingMultitaskingOniPad/QuickStartForSlideOverAndSplitView.html#//apple_ref/doc/uid/TP40015145-CH13-SW1 ) it seems there are three criteria to have it enabled: * Set the Base SDK to “Latest iOS,” as described in Setting the Base SDK in App Distribution Guide. * Provide a LaunchScreen.storyboard file (instead of a .png image file as you did in iOS 7 and earlier), as described in Creating a Launch Screen File in App Distribution Guide. * In your project’s Info.plist file, in the “Supported interface orientations (iPad)” array, declare support for all four device orientations Request: * Update app.json schema to allow declarative support for all four device directions * Allow specifying a storyboard file as the splash screen or convert the existing splash png into a LaunchScreen.storyboard

I really miss the oppurtunity to share a message with my shared file, for example: a user shares a photo to whatsapp from inside the app, and the whatsapp caption is automatically filled by the provided message and send to the receiver of the shared file.

Allow share, to work with multiples files

Allow users to add subtitles to video (.srt file/fetched from URI?). It would be really nice to add an ability to resync them (+ 5 seconds etc.)

Expo sdk 42 brought a very popular feature but no good examples are available, https://docs.expo.dev/versions/latest/sdk/notifications/#handling-incoming-notifications-when-the-app-is-1 the “content-available” flag ... This flag must be added, but can we pass it to the expo notification service api? Or do we have to use apns and fcm directly? I don't think it's really that hard to let set this key value along with others :) Please add this little feature to expo notification service api.

It would be great if current Expo push notification service supported tags so that we can update existing push notification in the user's mobile device. This is especially important when developing applications such as chats - when we need to notify users when new message has been sent, but we don't want to create N push notifications, only update the number of unread messages.