Hacker News Reader

Comment by akamaka | Hacker News Reader

Starting a React Native app project has been quite easy, but what resources do you use when you need to go deeper to solve difficult problems? I find that a lot of the documentation makes everything look easy, but I don't understand what's going on underneath the hood.

Do you just read the React Native source code to learn how it actually works?

View on HN

You will just have to start trying. There is still a lot objective c that you will need to write for various kits that haven't been ported over.

So learning how to write bridges and view managers are pretty much essential.

Very active issues tab and community though, so you can work through most thing, but definitely room for improvement though. But the biggest struggle was keeping with it and buying into React way of doing things.

hit me up on twitter if you have more specific questions @myusuf3.

Thank you! I've asked this same question before, but your answer is the most actionable one I've received so far. I'm going to dive in and get a better understanding of bridges and view managers.

In the React Native case specifically, I've found that searching github issues is often super helpful. The project is very popular, changing really really fast, and still has a bunch of rough edges. So if something really seems wonky (and isn't a bizarre use case), it's pretty common that someone has already brought it up there.

Reading the code is pretty much always a good idea, too.

Not the parent but I thought I'd chip in.

When I get stuck using one of the Native APIs, I usually look in the source code. It usually becomes very clear which issues that might have occured. What I'm saying is; there's no need to read the full source code, just reading the relevant component/API adapter goes a long way.

(At least for the problems I have solved. Your mileage may vary)

Reply on news.ycombinator.com