To be honest, I am working as a mobile developer because I got this opportunity for the first time. Then, after going through it, it turned out that mobile development itself has a broad scope, so I became more interested. I also thought that if I moved to other fields, I couldn't stay focused, so I decided to stick with mobile development until now.
I started working in mobile development in 2016 until now, which means it's been more than 6 years. What I love most about mobile development is that there are many things to explore. Due to its broad scope, mobile development has become an interesting area to dive into.
I like working at VirtualSpirit because this company carries a remote work type so I can work from home. I can still have time for my family. Since I have always had a goal of being able to work remotely.
Meanwhile, the mobile team is the last team to run the development according to the standard development process (design → backend → mobile). So if there is a miss in the timeline, the mobile team will fall through the cracks. Moreover, if there is a bug, the mobile team will always be the first team to blame for. Even though it is not necessarily the fault of the mobile team.
But that doesn't mean the performance in React Native isn't good, it's more a matter of preference. React native is optimal for fast development processes because it’s hybrid, easy to learn, and has a large community.
One common performance issue that often arises is the re-render issue. There are many ways to avoid this. The easiest way is immutability, using refs, atomic components, selecting stores, using states, etc. Many developers who are just learning React Native often miss these methods.
At VirtualSpirit we rarely use automated testing. But even with React Native, we can implement testing, from unit testing to UI testing, etc.
As in question number 6 earlier, many developers who are just learning React Native often experience this. I was like that before. The way to avoid this is to read more sources, look for more references, and have more discussions with other developers.
My advice is don't hesitate to ask questions, look for people who can help us in learning, don't forget to learn fundamentals, don't use Google or StackOverflow too much, and read more documents or other sources.