@rolandobarbella@_philpl@betomoedano@expo day 2 at expo but this is the goal π€
been making expo content for a while already and there's plenty more on the way
https://t.co/RYv7YSdO7F
Built offline persistence into my app insanely fast using /native-data-fetching skill from @expo.
This + codex helped me wire up offline persistence with Tanstack Query + MMKV. Huge win for users with flaky connections
Iβm super excited to announce Iβve joined @expo as a Developer Success Engineer! π₯³
Kind of surreal, honestly. Iβve been building with Expo on a ton of projects for a while now, and itβs shaped how I think about building apps more than anything. And thereβs a lot happening in the React Native world right now, so getting to work on it from the inside, plus making content that helps other devs build better and faster, feels like exactly where I want to be.
Looking forward to spending a lot more time with this community π
Y'all are in for a treat π
Nathan is going to make some slick demos that will help you add unique and beautiful interactions to your apps.
So glad you're here Nathan!
Swift now talks to JSI directly. The Objective-C++ middle layer is gone.
In Expo SDK 56 we rewrote the native module infrastructure on Apple platforms. Calls are faster and the stack is simpler. The seam that used to make debugging miserable is gone too.
Here's how π§΅
Your next native module can live right next to your π°ππ.πππ‘.
In Expo SDK 56 we added inline native modules. Create a π½ππππππ πππ .ππ πππ beside your app files and write Swift there. Nothing to scaffold first.
Setup takes two steps β
So we kinda reinvented the wheel and built a fully custom AV engine and composition library for MyGroove because ExoPlayer, AVFoundation and ffmpeg weren't fast- or powerful enough π
Introducing React Native Doctor
Find performance and security bugs in your mobile app
Run via CLI and fix with agents. Fully open source
npx react-doctor@latest