1. It's great but it's moving too fast sometimes. RN ecosystem is pretty bad so no way I would recommend any less mature alternatives (flutter for example). 2.

1. It's great but it's moving too fast sometimes. RN ecosystem is pretty bad so no way I would recommend any less mature alternatives (flutter for example). 2. Heard of Elm and unidirectional data flow (flux, redux...). Didn't use Elm, but did use redux and flux. It makes it easier to discover what is going on in the code which means faster bug fixes, faster features... 3. No, I did not 4. I don't care as I never plan to be Swift developer 5. We do, for primary web and mobile app (~15 frontend/mobile engineers) 6. If the main requirement is to be cross-platform and share the code I would go exactly for this stack React 7. Not so much about react, but Redux part of the codebase can be entirely shared if written correctly, all you have to do is write views for different platforms (mobile/web) 8. I heard of hooks, spend some time to understand, and I am OK with it but won't be pushing it in our company as I am not entirely convinced. I liked class based components having things explicit and not too much magic. Hooks felt like they were hyped by todo list warriors on the first day it was announced. Let's see how it turns out in bigger projects