Feature Requests

For multiple apps sharing the same codebase (ie: white-labelling, etc...), allow the user to change the output folder for android and ios during the prebuild step. IE : npx expo prebuild --ios-folder ./ios-app1 --android-output ./android-app1 We have this use case where an app shares the same codebase with minor changes across both of them. As of now we have to have a core repository, forked into two other repositories. This is a nightmare to maintain with SDK upgrades and other stuff. I would love to see this small feature added some day !

Re.Pack is easier to use, metro is a disaster.

Introduce a way to define a default Suspense fallback for: All routes globally, Or, at minimum, for all routes rendered by a specific layout. Expected benefits: Remove redundant Suspense wrappers in every route file. Guarantee a unified UX by enforcing one loading indicator without manual repetition. Make architecture cleaner and maintenance substantially easier for large codebases with many async routes. Example: Allow specifying a fallback prop on layouts, e.g.: export function Layout({ children }) { return ( <Suspense fallback={<LoadingIndicator />}> <Stack> ... </Stack> </Suspense> ); } or <Stack suspenseFallback={<LoadingIndicator />} > <Stack.Screen/> <Stack.Screen/> <Stack.Screen/> /Stack>

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

I would like to develop native WPF and UWP apps for Windows, which is my main operating system. React Native for Windows has been out for almost two years now and should be stable enough for Expo. https://github.com/Microsoft/react-native-windows

In expo-image, the build process uses kotlin-kapt . It should be change to ksp since kotlin version in expo is currently 1.9 and will be 2.x soon. Based on Kotlin documentation, it is recommended that kapt should be migrated to ksp for better performance and support.

From https://github.com/expo/expo/issues/313 : "Is there any way to customize the android AppTheme without detaching and editing _styles.xml_ directly? If it's not currently possible, it would be cool if we could set colorPrimary , colorPrimaryDark , colorControlActivated , colorAccent , etc. through _app.json_."

iOS supports Audio.RECORDING_OPTION_IOS_OUTPUT_FORMAT_LINEARPCM ; it'd be great if this could also be supported by Android. One use case for this is for speech-to-text, which lossy formats do not work well with. Additionally, Android currently does not appear to support any lossless format. https://docs.expo.io/versions/v34.0.0/sdk/audio/

I would like to avoid having to convert .3gp's and .aac's server side to .wav for playback on a website. Would be great to have a consistent file format available for export for Expo.Recording

iOS background tasks have a limited execution time. When this time expires, iOS calls an expiration handler before forcefully terminating the task. Currently in expo-background-task: The expiration handler only logs a warning and marks the task as failed ( BackgroundTaskAppDelegate.swift:13-18 ) JavaScript task code has no way to know when expiration is imminent Tasks cannot perform cleanup operations before being terminated This can lead to data loss or inconsistent state if tasks are killed mid-operation I'm not familiar with the Android implementation. If there is no analogous feature on Android, any registered expiration handler can be ignored.