TIL that you can use πππππ-ππππππ-πππππ-πππππ with ππ‘πππ for faster network requests - literally plug-n-play! β¨
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 β
In the next version of screen-transitions, native stack integration is deprecated!
Well kinda, I'm just moving it behind an adapter approach.
This way you can use the latest version of native stack from react-navigation/expo router and simply just opt into custom transitions.
Our warp[dot]dev site gets 10M visitors/year. We migrated the whole thing from a no-code editor back to code in just 3 weeks.
Very few hiccups, and SEO actually improved. Plus, the marketing team is free to use Warp to ship future changes
The bounds api is great for images, but not so much for videos that require continuity (yet). Today I had some time to play around with react-native-teleport and this is how I managed to integrate it into screen-transitions.
Super excited to see how further this can be pushed
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.