Krzysztof Magiera
@kzzzf.bsky.social
1.4K followers 110 following 92 posts
Software Mansion • React Native • Radon IDE
Posts Media Videos Starter Packs
kzzzf.bsky.social
Would add LG form sheets too that will hopefully land in the next version of react native screens
kzzzf.bsky.social
Yes. Screens have a custom implementation for full screen swipe that can enabled with a prop. With the next version it will however default to the native full screen swipe behavior
kzzzf.bsky.social
Note that simple_push still doesn't modify the default behavior but provides an alternative animation that tries to match the default behavior. This will be different in iOS 26 where push/pop have a rubber-band effect now
kzzzf.bsky.social
yeah, simple_push really seems like the only way to go here. We've spent some time trying to match the default behavior (you can read more about it here: github.com/software-man... ) Open to changing that if you can suggest a better easing curve
kzzzf.bsky.social
Default transitions are hardly customizable on iOS. Especially now with iOS 26 where they made a ton of changes and the default transitions behave differently, I wonder how the x app would feel (given it is indeed custom transition for push). I can see if there’s anything we could do next week
kzzzf.bsky.social
As for that one I’m not so sure, it may just add another handler when you call it for the second time. Would need to check
kzzzf.bsky.social
Can’t you make the reference stable with useMemo though and just reconfigure it when needed?
kzzzf.bsky.social
Another way to do it is to keep the drawer gesture references which may stable too with useMemo and only co figure it once. You can reassign the gesture instance to new components and I think you should be able to event have it used in two different components at the same time
kzzzf.bsky.social
If the drawer changes frequently this could be a problem. The native gesture will be accumulating all the previous drawer gesture references which may become too big. It actually only keeps the id so each one wont contribute a lot but if it grows indefinitely it could be a problem
kzzzf.bsky.social
If you have any feedback from using the tool I'd be super valuable to hear your thoughts. Thanks!
kzzzf.bsky.social
We also contribute changes or work with other tools that we integrate such that we can eventually get rid of these with some future versions of RN.
kzzzf.bsky.social
There are a couple of "hacks" that may be considered fragile but they typically stem from current limitations in RN tooling. A lot of them are mitigated or completely obsolete on newer versions of RN while we keep them around in order to support older versions.
kzzzf.bsky.social
It might seem to be too good to be true, but we’ve worked hard over many months to get it to the point we're at now.

There are still some rough edges but works very well for many people already.
kzzzf.bsky.social
🙋‍♂️ will be there
kzzzf.bsky.social
Introducing Radon AI for GitHub Copilot!
📚It taps into our daily-updated database of docs & code samples from top libraries in RN directory, giving Copilot the best context for your queries
🧐It understands versions of packages you're using for improved quality of suggestions
kzzzf.bsky.social
🚀 Radon IDE 1.5 is out!

🚨🚨 NEW 💬 Radon AI – Chat participant for GitHub Copilot with up-to-date React Native knowledge

And more:
⚡ Improved EAS workflows
📱 Home / App Switch buttons support
🪲 Improved error & exception handling with clickable links
🔧 Support for RN 0.79
kzzzf.bsky.social
Just published Radon IDE 1.3 with:
🛜 built-in Network Inspector
0️⃣ zero config integrated Redux DevTools
💅🏻 the panel now matches editor theme by default (contributed by @kszlezingier.bsky.social )
👾 number of important fixes to debugger and project workflows

Install it here: ide.swmansion.com
kzzzf.bsky.social
It required small changes to Fabric but thanks to the help from Meta we got that sorted a long time ago. Other than that Fabric is really well designed and we would have to make a ton of compromises if it wasn't in place and we had to work with the old architecture (that's why Rea4 is Fabric only)
kzzzf.bsky.social
As for the compromises, there isn't anything significant that comes to mind. The biggest challenge was to figure out how to handle prop updates that aren't triggered by react re-renders, but we actually come up with the right technique in Reanimated 3 already when integrating with Fabric.
kzzzf.bsky.social
Those are all great questions. We have a good contact with people at meta and been discussing this as well. There are definitely different tradeoffs so difficult to say at this point if this will land upstream in the near future.
kzzzf.bsky.social
This is the most important update to Reanimated since worklets. Really proud of the team 🐎
swmansion.com
Announcing React Native Reanimated 4 🐴

Long-awaited CSS Animations and Transitions support is here! ✨

Available now in Beta.

Read more 👇
kzzzf.bsky.social
There’s a chance this will work without being wrapped. I don’t know to be honest. Of course as long as you don’t nest buttons under components that use gestures too
kzzzf.bsky.social
So you can’t make the Animated wrapper for a component that is already wrapped. BTW: reanimated doesn’t have this restriction but the example is for Animated API not Reanimated
kzzzf.bsky.social
I don’t know if it is needed. Would have to try it. All button components are by default wrapped this way such that they can be referenced in other gesture detectors for orchestration. The “pure” button is not wrapped because Animated requires direct native component for createAnimatedComponent