RFC: Expose transition progress as a Reanimated SharedValue for external consumers (react-native-teleport integration)

[asadhmv]

Hey! Love the library, the gesture engine and reveal transition are exactly what I need.

I'm trying to combine it with react-native-teleport to build Instagram-style feed → reels transitions. The idea: your gestures handle the dismiss/open animation, teleport handles moving the actual video component between screens without unmounting it (so playback never interrupts).

The missing piece: teleport's Portal component needs to know when to switch hostName (e.g. from "feed" to "overlay" to "reels"). That decision has to happen based on the transition progress, but right now progress is only accessible inside screenStyleInterpolator as a worklet, not from outside the navigator.

Would it make sense to expose the active transition's progress as a SharedValue that can be consumed outside, something like a useScreenTransitionProgress() hook? That way I could do:

const progress = useScreenTransitionProgress();

useAnimatedReaction(
  () => progress.value,
  (p) => {
    if (p > 0.6) runOnJS(setPortalHost)("reels");
    if (p < 0.4) runOnJS(setPortalHost)("feed");
  }
);

Happy to open a PR if this direction makes sense to you. What do you think?

[eds2002]

Would 'useScreenAnimation' work for you? These aren't in the docs sorry about that (they need better work lol).

Also, react-native-teleport is being worked on in the next release! So most of the manual stuff will just be handled by the lib. Should have more updates on my x account

[asadhmv]

Thanks for the pointer. Excited to see where this goes!