Krzysztof Magiera
@kzzzf.bsky.social
Software Mansion • React Native • Radon IDE
Would add LG form sheets too that will hopefully land in the next version of react native screens
September 19, 2025 at 4:50 PM
Would add LG form sheets too that will hopefully land in the next version of react native screens
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
September 19, 2025 at 4:49 PM
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
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
September 15, 2025 at 10:28 AM
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
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
September 15, 2025 at 10:27 AM
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
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
September 14, 2025 at 10:29 AM
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
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
September 3, 2025 at 7:34 AM
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
Can’t you make the reference stable with useMemo though and just reconfigure it when needed?
September 3, 2025 at 7:28 AM
Can’t you make the reference stable with useMemo though and just reconfigure it when needed?
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
September 3, 2025 at 6:26 AM
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
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
September 3, 2025 at 6:25 AM
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
If you have any feedback from using the tool I'd be super valuable to hear your thoughts. Thanks!
May 5, 2025 at 9:11 PM
If you have any feedback from using the tool I'd be super valuable to hear your thoughts. Thanks!
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.
May 5, 2025 at 9:11 PM
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.
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.
May 5, 2025 at 9:11 PM
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.
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.
There are still some rough edges but works very well for many people already.
May 5, 2025 at 9:11 PM
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.
There are still some rough edges but works very well for many people already.
🙋♂️ will be there
April 18, 2025 at 9:04 AM
🙋♂️ will be there
Read more about Radon AI: ide.swmansion.com/docs/feature...
And check out the full changelog for the 1.5 release: github.com/software-man...
And check out the full changelog for the 1.5 release: github.com/software-man...
Radon AI | Radon IDE – An IDE for React Native
Radon AI is a GitHub Copilot Chat participant enhanced with up-to-date information about the React Native ecosystem.
ide.swmansion.com
April 14, 2025 at 1:21 PM
Read more about Radon AI: ide.swmansion.com/docs/feature...
And check out the full changelog for the 1.5 release: github.com/software-man...
And check out the full changelog for the 1.5 release: github.com/software-man...
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
📚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
April 14, 2025 at 1:21 PM
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
📚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
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)
January 22, 2025 at 10:33 AM
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)
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.
January 22, 2025 at 10:33 AM
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.
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.
January 22, 2025 at 10:33 AM
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.
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
January 19, 2025 at 12:21 PM
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
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
January 19, 2025 at 12:21 PM
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
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
January 19, 2025 at 12:21 PM
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