@VolksJK @burhanyilmazz_ @expo @phantom @BurgerKing @coinbase @Airbnb ejecting hasn't really been a thing anymore since 2021 🤐
English
phil 🫠
8.6K posts
phil 🫠
@_philpl
https://t.co/QmJOXJ4mSf on 🦋 • dev tools at @expo 𝝠 • 🗻 n+1 GraphQL/TS/React projects • 🔨 gql.tada, urql • 🐙 https://t.co/Ds9MkaBefU & https://t.co/aZl2NeIJGb
London Katılım Temmuz 2012
740 Takip Edilen9.5K Takipçiler
@burhanyilmazz_ @expo @phantom @BurgerKing @coinbase @Airbnb Convenience is great but doesnt erase limitations even in 2026 using @expo still means giving up some control and flexibility eventually serious projects eject.
English
If you’re building Expo apps in Türkiye let us know. Would love to hear about your experiences and share your development stories.
Hendrik Haandrikman 🐈@HHaandr
🇹🇷 The Turkish government is now offering app developers up to $430,000 in support. Per app. Per year A new government decree in Türkiye is a massive accelerator for (Turkish) developers Here’s what’s happening 🧵
English
we'll look at ootb react-native-macos OOT linking & resolution for 56. i think most tricky parts are done, there's been more testing against macOS, and the next gap is CLI & create-expo/prebuild changes
for the CLI it'll basically now come down to getModulesRunBeforeMainModule (which should probably just go away at this point), getPolyfills, and autolinking changes. autolinking module resolution should cover the rest
so there's a plan but will have to see if it pans out
English
@GroundControl @expo A basic create-expo-app template for Expo macOS would go a long way. It's an absolute pain every time I have to scaffold a new app.
I'm sick of patching:
- react-native-macos-init
- the Metro config
- the Podfile
- the pbxproj
- the AppDelegate
But we really need Prebuild, too.
English
I've been trying to make a MacOS build on an Expo app but I've been running into some issues. I'm having Claude Code search Twitter via Chrome MCP for anyone else who's hitting the issue and look it's @birch_js
English
phil 🫠 retweetledi
Introducing Expo Agent
Build truly native iOS and Android apps from a prompt. Anything from React to SwiftUI to Jetpack Compose.
Compile and deploy for Apple, Android, and the web right from the browser!
English
and to pull the curtain behind this just a little, @claudeai code one-shots expo-widgets apps rapidly.
it took longer to edit these videos than to create 3+ demos and pick the best one
Expo@expo
The 𝚎𝚡𝚙𝚘-𝚠𝚒𝚍𝚐𝚎𝚝𝚜 alpha is here! Now you can build iOS home screen widgets and Live Activities as React components. No separate Xcode target. No manual App Groups. No SwiftUI layout code. Write your widget in @expo/ui, and Continuous Native Generation handles the rest. ◆ Interactive buttons and toggles on the home screen ◆ Live Activities for the Lock Screen and Dynamic Island ◆ One React component, native rendering under the hood Details and code to get started in the blog below ↓
English
it'll be hard to reliably get real-time updates through background-tasks, I reckon, yea. more testing needed, which is why widgets are in alpha, but with the expo-background-task refresh from SDK 54, we can probably make non-lockscreen updates reliable, within the OS limits
English
How reliable is the sync with bg tasks ?
I tried doing it before this and it was a mess, background tasks work but they were no guarantee it would actually update the app state from lock screen - i assume iOS limitation. Push notifications might work but they too expensive.
I read a blog from Uber about their LiveActivities. They do use push notifications though, and they don’t have actions on it, I assume its hard to implement reliably
uber.com/en-DE/blog/liv…
English
phil 🫠 retweetledi
The 𝚎𝚡𝚙𝚘-𝚠𝚒𝚍𝚐𝚎𝚝𝚜 alpha is here!
Now you can build iOS home screen widgets and Live Activities as React components.
No separate Xcode target. No manual App Groups. No SwiftUI layout code.
Write your widget in @expo/ui, and Continuous Native Generation handles the rest.
◆ Interactive buttons and toggles on the home screen
◆ Live Activities for the Lock Screen and Dynamic Island ◆ One React component, native rendering under the
hood
Details and code to get started in the blog below ↓
English
@DnuLkjkjh @expo this uses a light JSC runtime that renders pure Swift UI. That's why the API constrains this to a small function that returns Swift UI views via Expo UI. That keeps this lean enough to work for widgets & live activities
English
writing iOS widgets in React instead of SwiftUI and having CNG handle the Xcode target setup is a huge DX win. the manual App Groups + widget extension + shared container dance is one of the worst parts of iOS widget development. curious how Live Activities handle the tight timing constraints though — WidgetKit has strict memory and CPU budgets for updates
English
@tusharghige @expo expo-ui/jetpack-compose wasn't as far along as swift-ui when this project was started and the implementation plan for iOS was more solid. Android will follow. the iOS widgets aren't rendered with React Native but instead with pure Swift UI driven by a mini JSC runtime
English
@erickreutz @expo you have the option to update the entire widget's swift ui views or props inputs from the app, from a background-task, or update the props from a push notification
English
@stackoversnow @expo yep, widgets/live activities are functions that describe Swift UI views and can be updated via props from the app, a background-task, or push notifications. button presses can also feed back into the app
English
@hirbod @betomoedano the wait was worth it if you check how much the prices of QD-OLED monitors have dropped 😄
English
@YayaSoumah @expo @AlanJamesHughes @tsapeta you can get Expo Go for 55 from our testflight (link in the changelog post), but keep in mind this isn't for Expo Go but for custom dev builds
English
English
@mikitahimpel @expo since OTA updates can be run at app startup or on a user action, it'll affect the app itself, or UI, depending on how you present it. But since this reduces bandwidth, it'll reduce traffic cost, which isn't getting cheaper fast enough these days unfortunately
English
@expo Does this affect how users feel about your app? In my opinion, if users see that the app is updating for too long, they will blame Apple or their internet provider.
English
🤏 You can ship much smaller OTA updates with SDK 55.
EAS Update now supports bundle diffing. Devices download a patch instead of the full bundle.
In testing, that's ~75% smaller downloads. A 3MB update drops to ~0.75MB.
◆ Opt-in, beta, works on Android and iOS
◆ Falls back to full bundle if a patch isn't a clear win
Enable it in your app config today. Details in the blog below ↓
English
@Miguel750343611 @expo if i had to guess, there's probably a a callback that's passed to skia that'll need a '"worklet"' directive? hard to tell w/o a repro, but maybe it's worth opening an issue or discussion thread on react-native-skia
English
Expo SDK 55 is here😅
React Native 0.83. React 19.2. Legacy Architecture dropped. New Architecture is the default.
◆ 75% smaller update downloads with Hermes bytecode diffing
◆ Expo Router v7 🤯
◆ Brownfield isolation via expo-brownfield
◆ AI tooling: MCP + agent skills for Claude Code
◆ Expo UI much improved for both Swift and Jetpack Compose
There is so much more...it feels futile to try and isolate a few bullets...check out the full release notes and let us know what you think ↓
English
@freiserg @TomaszLorencDev @expo fair, but this applies in that case: x.com/_philpl/status…
it's jarring to switch defaults here and is non-trivial with the prebuilds, and that's the main blocker of us probably not doing a mid-cycle switch to 0.84 most likely. that's why canary is potentially better for 0.84
phil 🫠@_philpl
@Bodok0 @expo a mid-cycle bump isn't out of the question but Hermes v1 switching from opt-in (0.83) to the default (0.84) might be too jarring to have in a single SDK line (with 56 eventually being RN 0.85) It'll become clearer in the coming weeks and we'll adjust if needed
English
@_philpl @TomaszLorencDev @expo Mainly Hermes v1 built-in. Otherwise compile times increase significantly as mentioned in the blog post. I haven’t tried it myself yet
English
‼️Expo SDK 55 beta is out now🧪 (RN 0.83.1 + React 19.2)
Highlights:
♢ Legacy Architecture support is gone
♢ New default template (native tabs, /src/app)
♢ Hermes v1 opt-in
♢ Smaller OTA updates with Hermes bytecode diffing
♢ More native Router APIs + better brownfield support
♢...and more and more...
We'll link to the release notes with details about breaking changes below ↓ Please give the beta a try and report your issues 🙏
English
@zeeshdev28 @expo we've accidentally pinned a few react-navigation dependencies that weren't supposed to be pinned. There's a patch for this coming today
English
@freiserg @TomaszLorencDev @expo what change in RN 0.84 are you after that makes it appealing to be available to you now in 55 rather than 56 or using the Expo canary line?
English
@_philpl @TomaszLorencDev @expo These options feel pretty inconvenient. Hopefully RN 0.84 will also land in SDK 55 🤞
English
re react: react is just a top-level API package and contains little logic. The renderer in RN is a specific version of React itself but not based on a separate package version. The react base package can't be upgraded because the renderer contains a hardcoded exact version check
That's not ideal for react-dom specifically, and we're pushing for change there on React's side
English