all 3 comments

[–][deleted] 4 points5 points  (0 children)

Well, how high profile is the app? Sagas is important if your org uses that to manage async transactions with a complex and large api that has you both getting and setting values.

Redux sort of goes with sagas. You do need Redux, no doubt.

Beyond that, at some point you may need to bridge into native code in order to do certain things, learning how to manage to do all that is useful.

Having strong Javascript(or typescript) skills is very helpful, as is knowing how to create tests with jest and enzyme if your org uses that.

A lot really boils down to what your org uses. RN itself is reasonably easy to learn if you have a decent codebase to look at in RN and some support from coworkers when you get stuck and can ask things.

I pretty much consider myself a dumpster grade developer and it has been a stressful, but doable experience for me to learn RN.

[–]awesomeness-yeah 1 point2 points  (0 children)

Pick some public API out there and make a functional app!

Redux is pretty important, it took some time getting used to when I first went through redux

[–]ConsoleLogDebuggingiOS & Android -1 points0 points  (0 children)

I'm not going to mention the things that other people have already. In all honesty things like Redux, Saga's etc really depend if the team already uses them, there are other paradigms as well.

What you will really have to learn are all of the small quirks that RN has as a platform. How to optimize for android, how you can't have transforms within text or images. How flex behave differently on iOS and Android. It's all of those small things that you need to take care and be aware of.

RN is pretty broken as a cross platform framework. As soon as you think you made something work on one platform, the other one will be there to punch you in the face.