A demo app created in times of Expo SDK 42-45, when features shown here were new/experimental. Recently it was updated to Expo SDK 54, and they're mature and stable now. See commit for details.
Experimenting with new awesome React Native + Expo features.
Work in progress. More info soon.
A preview video (click the image):

⚠️ Caution! Some features used in this demo are in early, experimental stage and they're not ready for production. Use at your own risk.
🎉 It is now available as a separate library: expo-music-picker!
Now it is included in expo-audio so a custom native module is no longer needed!
SharedValues and animated with Reanimated 4.There is plan to use react-native-multithreading and calculate it in a separate thread. But even without that, the JS keeps around 57-59 fps.
First time:
git submodule update.yarn installyarn prebuildyarn run:iosJust to start the bundler (without rebuilding client): run yarn start.
Most of them are caused by limited time of mine, and also by some libraries, which depend on Expo, but have not yet been updated to support latest Expo features.
Error: FunctionCallException: Calling the 'setAudioSamplingEnabled' function has failed (at ExpoModulesCore/SyncFunctionDefinition.swift:137)
→ Caused by: NativeSharedObjectNotFoundException: Unable to find the native shared object associated with given JavaScript object (at ExpoModulesCore/DynamicSharedObjectType.swift:58)]See the the plugins section of app.json to see how the patches are applied:
xw
expo-cli built-in plugins sets the Push Notifications capability even when expo-notifications are not installed and I see no way to disable it. Another plugin was written to delete that entitlement.Info.plist value about Media Library usage permission - a config plugin takes care of thatI started this project when Expo SDK 42 came out. So much changed since then and with each release less and less patches and workarounds were needed:
Linking custom native modules:
~~The custom_native_modules directory needs to be added to autolinking paths in Podfile. A config plugin takes care of that.~~
> It appears that it can be configured in package.json as expo.autolinking.searchPaths. It's not needed anyway, look at the next point:
expo-modules-autolinking requires modules to be specified in package.json dependencies. I don't want to copy my custom native modules to node_modules they are deleted after being copied there by yarn.~~~~Patched expo-modules-autolinking@0.5.1 to apply changes from this PR until it's published. Now custom native modules dir can be specified in package.json.~~ Finally, this PR is published in upstream expo-modules-autolinking.
~~Replaced expo-av with my custom expo-av-jsi native module to support JSI Audio~~
~~The JSI Audio streaming is now included in upstream
expo-av@10.2.0but yet for iOS only. It'a super-secret hidden feature of SDK 44.~~
In SDK 45 both platforms are now supported by Expo AV. 🎉
expo-gl and related libraries - needed, because of migration from @unimodules/core to expo-modules-core~~xcframework if available, but that does not work for patched expo-gl, so its xcframework is deleted force build from source.~~expo-gl installs wrong expo-modules-core dependency in its own node_modules - it is deleted, the global node_modules one is correct.~~AppDelegate.m is being broken by expo-dev-client config plugin, wrote another config plugin to copy the patched file.~~react-native-ble-plx and Podfile config plugin, because of this issue.~~There was a postinstall.js script to perform some of the patches above (like file copy/delete). Fortunately it is no longer needed. Yay! 🎉
~~patch-package for webgltexture-loader-expo@1.0.0, a dependency of gl-react-expo - it has not yet been updated to use expo-modules-core in favor of @unimodules/core.~~
Upstream version 1.2.0 has it patched 🎉
$ claude mcp add expo-mega-demo \
-- python -m otcore.mcp_server <graph>