Charlie Cheever

I recreated Revolut's tab bar in @expo with all the tiny details > npx expo install expo-glass-tabs

I recreated Revolut's tab bar in @expo with all the tiny details > npx expo install expo-glass-tabs

Here is the Expo + WebGPU volcano game demo from my real iPhone And honestly, I’m impressed by how smooth it feels. This is still the initial prototype. No improvements yet, and there are plenty of bugs to fix. But seeing Three.js running through React Native WebGPU inside an Expo app feels unreal. The interesting part is performance: UI thread → always 60 FPS JS thread → drops significantly over longer sessions So the rendering stays smooth, but once the JS thread gets overloaded with game logic, object updates, collisions, and events, the gameplay gradually starts to feel laggy. The next challenge is optimization: → Reduce work inside the main JS loop → Reuse objects instead of constantly allocating them → Use a fixed-timestep game loop → Move suitable calculations into a Worklet runtime or native layer → Keep React state completely outside the per-frame path → Profile memory usage and remove unnecessary scene updates Worklets alone aren’t a magic fix, but moving heavy calculations away from the main JS runtime could make a big difference. Still early. Still buggy. But this real-device demo shows how much potential @expo DOM (creator: @Baconbrix ) + @threejs + @reactnative @webgl_webgpu already has. Open to contract or full-time mobile roles. DMs are open.

Flighty is one of the best-designed native app's on iOS, so I rebuilt it with @expo. Everything on the Expo side is real native UI. This is the best time there's ever been to build app's with Expo.

Flighty is one of the best-designed native app's on iOS, so I rebuilt it with @expo. Everything on the Expo side is real native UI. This is the best time there's ever been to build app's with Expo.