Shachar

I tried `react-native-easy-dnd` and couldn't get it working. Even so it has the down side of using `PanResponder`. So I built something my own. I think it's pretty good. Still...

I've published it here: [rn-drag-drop](https://github.com/ShaMan123/rn-drag-drop). However I'm about to abandon it in favor of this: [PR for react-native-gesture-handler](https://github.com/software-mansion/react-native-gesture-handler/pull/963). Android is coming into alpha very soon.

What about pring instead of struggling against the natural elements?

#5 iOS needs work, not yet compatible on `@next` version

Hi there, `react-native-reanimated` is about to release a major version, once they do iOS can be implemented easily

Unfortunately not. It isn't too much work but I don't have a mac.... If you'd PR I'll assist where possible

Yeah, it's much more peeformant. It was the main reason I forked. Android will run out of memory in the original repo because it uses bitmaps badly. בתאריך יום ה׳,...

The frame rate drop is a different issue caused because of crossing the bridge for every movement. That was solved ysing reanimated. And could be better solved natively. Regatding iOS...

By the way, I think this kind of ui should be implemented completely in native and pass a single data object at the very end of the interaction.

solved?