You don’t really need it since you can create custom components and do whatever you want

we have a custom component and it really kinda sucks: github.com/bluesky-soci... every time you rerender the component it has to send it via useEffect to the provider and then back down to the outlet which is really slow. is there a better way to do this?

we had issues in the past where you can’t have a controlled input in a portalled component controlled from outside of the parent, because passing state from a parent down to the portalled text input is crazy slow

What I mean is you can create a custom native component, mount it natively wherever you want it, and just pass props to it

ohhhh sounds difficult, add to core pls 😓

(fr though thank you will look into it!)

I think the problem is there isn’t really a generic way to do it that will work in all RN apps, maybe it could work for an app that uses all full screen RN views with JS driven routing, but as soon as you’re embedding inside an app with native navigation it gets tricky

There are also existing solutions to common problems you use portals for in DOM, for example dialogs and bottom sheets. For those use cases you can assist use the built in platform components for those, which libraries already do for you

The Modal core component is basically a portal, but it doesn’t work for every use case, which is kinda my point above

yeah we use our shitty portal component for our custom native bottom sheets but it’s subpar. we should definitely investigate doing the portal part natively

the portal from gorhom is not working out for your usecase for example?