Evan Bacon 🥓

Expo SDK 56 is out 🙌 ◆ Expo UI is stable on iOS and Android ◆ iOS builds 16% faster, plus another 20% on EAS from precompiled community libs ◆ Android cold starts 40% faster ◆ Expo Router decoupled from React Navigation ◆ Inline native modules: write Swift and Kotlin right next to your TypeScript ◆ Hermes v1 by default ◆ Bytecode diffing on by default (~58% smaller OTA updates) ◆ iOS Widgets stable ◆ React Native 0.85 + React 19.2 It's been two months since SDK 55, and we packed in everything we could fit. Your iOS build times are going to thank you. Full changelog ↓

Meta Ray-Ban DisplayでReachy Miniを操作できた！

Expo SDK 56 is out 🙌 ◆ Expo UI is stable on iOS and Android ◆ iOS builds 16% faster, plus another 20% on EAS from precompiled community libs ◆ Android cold starts 40% faster ◆ Expo Router decoupled from React Navigation ◆ Inline native modules: write Swift and Kotlin right next to your TypeScript ◆ Hermes v1 by default ◆ Bytecode diffing on by default (~58% smaller OTA updates) ◆ iOS Widgets stable ◆ React Native 0.85 + React 19.2 It's been two months since SDK 55, and we packed in everything we could fit. Your iOS build times are going to thank you. Full changelog ↓

You can now build iOS camera apps directly in Codex! ~ / npx serve-sim Agents can even use video files to develop headlessly in the cloud, run e2e tests, and work in parallel. No more bottleneck on physical sensors!

If Austin wants to be a tier 1, tech city it needs to get serious and stop using this water for frivolous recreation and start using it for data centers. If you don’t understand this, you’re going to get left behind

making my first mobile app and it’s so weird, you’re telling me you can’t just push and see your changes live in 2 min? if there’s a bug it’s stuck there for 2 days? maybe mobile app devs are the best at testing their work since it literally takes days for a fix to deploy 🤣

You might believe you should spend less time thinking about code because of AI. I strongly disagree! We’re watching this play out live where tons of AI generated code becomes a liability. At the end of the day, an engineer needs to be responsible / on call for code that gets shipped to production. If you don’t understand the system you’re trying to debug, you’re probably going to have a bad time. Yes, AI can help with all of this, if you set up the proper systems. You can have agents triage prod logs, look at errors, etc. You can speed up parts of the investigation, but an engineer needs to make the call. There might be serious customer or financial implications from that change. I expect the trend continue for trimming dependencies, vendoring code so you can modify it directly, preferring simpler systems with fewer abstractions, and spending waaaay more time thinking about system design and code maintenance. I’ve said this before, but it’s a great time to get familiar with CS fundamentals and some of the history behind what great software looks like. Many parts will be different in the coming years as AI progresses, but also a lot more than people realize will stay the same.