Feature Requests

Add a Snackbar component to expo-ui Hey team — I know you're steering the expo-ui effort and the direction so far has been great. But one critical piece is still missing: a proper Snackbar component, comparable to what Jetpack Compose offers. In almost every production mobile app, transient in-app notifications are essential — for undo actions, connection status, form feedback, or lightweight alerts. A toast is too ephemeral, a modal is too disruptive. Snackbars hit that perfect middle ground, and they're a first-class citizen in Material Design for a reason. Right now, teams building with Expo have to either pull in a third-party library, hack a custom one with Animated and absolute positioning, or just skip the pattern entirely — all of which undermines the “fully native, fully Expo” experience that expo-ui promises. I’d love to see a Snackbar component that: · Anchors to the bottom of the screen and slides up · Supports an optional action (e.g., “UNDO”) with proper touch handling · Respects safe areas and keyboard insets out of the box · Follows the duration/sweep-to-dismiss behaviors we’re used to from Material you/AOSP This is not a “nice to have” — it's a baseline primitive for modern mobile UX. Can we get this on the roadmap?

It is currently impossible to achieve some blur effects due to limitations of the blur view. The key things are: No way to adjust blur distance and saturation independently Maximum "intensity" of 100 only blurs by 20px (inspecting in web) I'm currently working on an app that requires a 100px blur. I can achieve this by stacking BlurViews on top of each other, but regardless of which "tint" I use the end result is always too dark, too light, too saturated, or too unsaturated. I'm not sure what the limitations are, but it may resolve all of my issues if instead of having a single "intensity" prop this was split into "distance" and "saturation".

I want to trigger press, long press actions in my liquid glass native tabs. For example show tooltip when long pressed, or trigger press when pressed again while being on the same route

Support for React Native MacOS apps in the SDK, including prebuild. I know some progress has been made, but other parts of it have stalled or been deprioritized, so gauging community support seems key to understanding its relative importance. Related to but distinct from https://expo.canny.io/feature-requests/p/support-for-react-native-windows-apps and https://expo.canny.io/feature-requests/p/support-for-ios-marzipanproject-catalyst-apps-that-can-run-on-macos The same as https://github.com/expo/expo/discussions/22273 (the top voted discussion topic) but recreated here in Canny, where feature requests are supposed to live.

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

Expo hosting sets a default Content Security Policy of "frame-ancestors 'self'". This means you cannot load any expo web app in an iframe, which can sometimes be a valid/valuable use case. Being able to control the level of strictness of the CSP is a standard feature of other hosting services (netlify, vercel, etc). Would it be possible to add this to the hosting config in eas.json or something like that? Thanks!

Currently it's possible to disable onboard screen in dev mode via deep link like: com.my.app ://expo-development-client/?url=http%3A%2F%2F10.0.2.2%3A8081%3FdisableOnboarding%3D1 but it adds an extra friction with tools like Maestro. It'd be nice to be able to disable onboarding screen via .env variables like EXPO_DISABLE_ONBOARDING=1

We'd like to record in a streamable format such that the recording is valid if it is interrupted in the middle (like if the app is killed). The variety of AAC formats require stopAndUnloadAsync() to be called in order to produce a valid recording file as far as I can tell. LinearPCM/WAV works but makes very large recordings. Opus offers a smaller file format that supports streaming.

This feature exists for ios as attachments when scheduling a local notification, but the option does not exist for Android even though it's been supported for many years natively on Android.

expo-doctor currently outputs human-readable text only. There's no Node API and no --json flag, which makes it difficult to consume programmatically in CI scripts without parsing the raw output with fragile string matching. Scripts that want to act on expo-doctor results have to parse ✔/✖ characters from the verbose CLI output and hard-code check names that must match exactly — both of which break silently when the output format or check names change. We currently are running expo-doctor in our CI environment, and we want to fail on anything except dependencies being out of date, so we have to have custom logic in place to parse the output, etc.