Feature Requests

We run a production Expo app (SDK 54) that wraps a heavy web app in react-native-webview. Our main ask is framework support for background memory, plus two things from the SDK 54 upgrade that caused a production regression: Background memory reclaim (the main ask). For WebView-heavy apps, the OS reclaims the backgrounded app/WebView under memory pressure, forcing a full cold relaunch on return. This is OS behavior, but it's a supported Expo use case. We'd like framework-level support: reducing background memory footprint, and/or a supported way to retain and restore WebView state across an OS-initiated process kill. Bundled react-native-webview version. SDK 54 shipped 13.15.0, which carried a WebView recovery crash (fixed upstream in 13.16.1/13.16.2). Bundling a webview version with a known crash caused a regression for us. New Architecture default. Our config set newArchEnabled: false scoped to Android in expo-build-properties, but after the SDK 54 upgrade the iOS build was on the New Architecture anyway. An SDK upgrade silently switching a build's architecture, without an obvious cross-platform signal, is easy to miss and hard to diagnose. Please make newArchEnabled behavior explicit and consistent across platforms. Environment: Expo SDK 54, react-native-webview (moving to 13.16.x), iOS + Android, production.

Use case I build Vibe Costs, a dashboard that lets developers aggregate live software and infrastructure costs. EAS Billing already shows an estimated current-period amount across Build, Update, Hosting, and Workflows, but there is no public endpoint or billing-read OAuth scope for reading that summary. Expo billing support confirmed that the EAS REST API only covers triggering workflows and reading run details. Personal access tokens and robot users are the documented programmatic options, but robot users still cannot read cost data. Requested solution Please add customer-authorized third-party OAuth with a narrow billing-read scope and an endpoint returning: current billing-period total and currency plan allowance and signed credits or adjustments documented freshness EAS product and project attribution stable account, project, and resource IDs The important constraint is least privilege. Customers should not need to provide a personal access token or robot token to an external cost dashboard. Technical proposal and machine-readable schema: https://vibecosts.app/cost-api/docs If this becomes available, I will build and maintain the connector and test it against my own Expo account.

Use case I build Vibe Costs, a dashboard that lets developers aggregate live software and infrastructure costs. EAS Billing already shows an estimated current-period amount across Build, Update, Hosting, and Workflows, but there is no public endpoint or billing-read OAuth scope for reading that summary. Expo billing support confirmed that the EAS REST API only covers triggering workflows and reading run details. Personal access tokens and robot users are the documented programmatic options, but robot users still cannot read cost data. Requested solution Please add customer-authorized third-party OAuth with a narrow billing-read scope and an endpoint returning: current billing-period total and currency plan allowance and signed credits or adjustments documented freshness EAS product and project attribution stable account, project, and resource IDs The important constraint is least privilege. Customers should not need to provide a personal access token or robot token to an external cost dashboard. Technical proposal and machine-readable schema: https://vibecosts.app/cost-api/docs If this becomes available, I will build and maintain the connector and test it against my own Expo account.

More and more supply chain attacks are causing many organizations to require a min-release-age setting in their NPM configuration (and I presume pnpm, yarn, etc). Expo doctor should not recommend updating dependencies that are too new according to those rules because this fails to fetch via NPM and forces us to have to manually find all dependencies that satisfy the version ranges but are older than X days.

@expo/ui exposes SwiftUI's refreshable modifier for List , but there is currently no way to customize the color/tint of the native refresh indicator. The refresh gesture works correctly and the native SwiftUI refresh indicator is displayed, but its color remains the system/default color. Expected behavior There should be a way to configure the tint/color of the refresh indicator, for example: refreshable({ onRefresh: async () => { await refresh() }, tint: '#FF5A5F', }) or preferably through a dedicated modifier/API that maps to the appropriate SwiftUI behavior. For example: <List modifiers={[ listStyle('plain'), refreshable(refresh), refreshableTint('#FF5A5F'), ]} /> The exact API is up to the maintainers; the important part is exposing the ability to customize the refresh indicator's color. Current behavior Applying the existing tint() modifier to the List does not change the color of the refresh indicator: <List modifiers={[ listStyle('plain'), tint('#FF5A5F'), refreshable(refresh), ]} /> The refresh indicator remains black/system-colored. This is particularly noticeable in applications with custom light/dark themes where the default indicator color does not match the application's accent color.

AudioPlayer already ships PCM sampling — isAudioSamplingSupported , setAudioSamplingEnabled(enabled) , and the audioSampleUpdate event. AudioPlaylist has none of it: its entire event map is playlistStatusUpdate and trackChanged . The ask: mirror those onto AudioPlaylist , emitting for whichever track is current ( currentIndex is already tracked and surfaced). Use case — a hands-free voice assistant. TTS clips play through AudioPlaylist because one queue gives synthesis/playback overlap, ordering, and a single stop/kill switch in one place. The UI has a presence indicator that should pulse with the assistant's actual voice, but with no sampling on the playlist it has to run off a synthetic timer instead. The alternatives are adding a native audio dependency, or moving playback to individual AudioPlayer s and rebuilding the queue/skip machinery — neither is proportionate to needing an amplitude number. It looks small on both platforms (read against 57.0.4): Android: AudioPlayer sources its samples from Visualizer(ref.audioSessionId) in createVisualizer() . AudioPlaylist extends the same BaseAudioPlayer and so has the same ref.audioSessionId , and Visualizer binds to the audio session rather than the media item — so track changes need no special handling. Lifting samplingEnabled + createVisualizer() + sendAudioSampleUpdate() into BaseAudioPlayer would give both classes the feature at once. iOS: AudioTapProcessor is initialised with an AVPlayer , and AudioPlaylist is a SharedRef<AVQueuePlayer> — already an AVPlayer . The tap attaches to player.currentItem 's audio mix, so the only additional piece is re-installing it on track change, which the playlist already observes. Happy to put up a PR if that would be welcome.

iOS silences all haptics and system sounds for as long as an app holds a recording-capable audio session (any category set with allowsRecording). For a chat app this is painful: recording a voice note is exactly when you want haptic feedback for things like recording lock and slide-to-cancel, and right now every haptic in the app goes dead the moment the recorder configures the session. Apple has an opt-in for this: AVAudioSession.setAllowHapticsAndSystemSoundsDuringRecording(true). expo-audio doesn't expose it, so the only way to get it today is a patch-package patch on the native module (which is what we ship). Proposal: a boolean on AudioMode, e.g. allowsHapticsAndSystemSoundsDuringRecording, default false so nothing changes for existing apps. Two details worth knowing from running this in production: The property belongs to the session configuration, so it needs re-asserting after every setCategory call, not once at startup. A category change drops it. There are three setCategory sites in expo-audio as of SDK 57: the setAudioModeAsync path in AudioModule, AudioRecorder.prepare, and the new AudioStream (measurement mode). The first two should respect the flag. The AudioStream one is a judgment call, measurement mode exists to keep the input clean and the mic picks up the Taptic Engine, which is also why Apple made muting the default. Happy to send a PR if the shape gets a thumbs up, we already run the equivalent change in production.

please criteria how to implement this permission so that expo-av has set up in the background or audio stream REQUEST_IGNORE_BATTERY_OPTIMIZATIONS Expo Permission

Lock screen controls for AudioPlaylist. This would result in Parity between the AudioPlayer and AudioPlaylist.

Alt prop support for web