Forgot to mention. It would be cool to define multiple shared bounds w/ different animations. you can return a bounds object with your shared bound id to apply animated styles individually

Right now it's VERYYY experimental. This mostly will be inspired by shared transitions like in instagram, TikTok, the shop app. Anyways, thank you guys for inspiring me

3) The name could change, but I really like the way Android differentiates their shared animations, element and bound. I think bound is more fitting in this case. Shared ELEMENTS is out of my scope but thankfully reanimated 4 will eventually perfect this.

^^ The reason for this, some apps get fancy. The underlying background for the shared element scale down, while the shared element scales into the new screen ofc, I think this is the best way of going about it.

2) My thinking process is to keep the api the same. You SHOULD be able to animate your shared bounds, ideally this would be set to a preset, but the option is there if you ever need it.

Eventually I'll show more complex examples, but .1) A new key that we'll expose is called previous. We can use current and next to animate screen transitions. Now we can use previous to animate our shared bounds

Thought I'd start documenting some stuff, this is just a veryyyy basic example and something that I hope in the end could work out great for shared elements

shared elements are SO exhausting.

RT @sheehanmunim: Just implemented react native screen transitions by @trpfsu in my new app, Lackin. Can't wait to implement new features a….

the old syntax was driving me crazy, this is much more enjoyable to write. out in the next version

still very experimental but I really doubt I could ever get it to work alongside screen-transitions, the only thing I hate is that noticeable lag, you can literally see when my push event runs in the index screen.

b is a transparent modal that has pointer events set to none, causing the underlying gesture to still be able to run correctly.

was a little inspired of handling forward navigation via gestures, this is a very ugly example, but I think this can lead to very customizable screens.

I think in the next version it'd be cool for . -more presets.-handle gesture driven push events as well ? 🤨.-handle that ugly new syntax. and I can't think of anymore, im beat - if you have any cool ideas drop a comment pls.

there's also a slight syntax change, but the old version still works, this just saves you a few keystrokes. personally think the new way looks a little ugly ngl, I'll have to figure this one out

I also assume u guys also ditched wonky flatlist in favor of legend list 😼

react-native-screen-transitions v1.1.0 improves on nested scrollables inside gesture driven screens, on android and iOS

RT @o_kwasniewski: Recently, I've worked on improving the built-in React Native modal! ✨. I've introduced a new prop: `allowSwipeDismissal`….