{"id":14771,"date":"2019-02-18T09:13:24","date_gmt":"2019-02-18T08:13:24","guid":{"rendered":"https:\/\/www.inovex.de\/blog\/?p=14771"},"modified":"2026-03-17T07:59:33","modified_gmt":"2026-03-17T06:59:33","slug":"lessons-learned-react-native","status":"publish","type":"post","link":"https:\/\/www.inovex.de\/de\/blog\/lessons-learned-react-native\/","title":{"rendered":"Lessons Learned after Using React Native for a Year"},"content":{"rendered":"

Last year I received the assignment to create a sophisticated Android and iOS application for a European retail chain, so their employees could be more productive in their daily routines. The goal was to create a React Native app to enable their employees to scan and maintain the retail chain\u2019s inventory in an easy and convenient way. I began working on the project in October 2017 and finished my work in December 2018. While creating the inventory app I had the opportunity to learn and gained a lot of insights about the pros and cons of using React Native.<\/p>\n

In this article you will find a brief summary of the lessons I learned while working with React Native on a daily basis for over a year. Please keep in mind that some of the lessons I learned refer to our technology stack which I attached below. For clarity reasons I divided this blog entry in four sections: \u2018The Good\u2019, \u2018The Bad\u2019, \u2018The Ugly\u2019, and \u2018Additional Learnings\u2019. <\/p>\n

\"\"
Our React Native technology stack.<\/figcaption><\/figure>\n
<\/div>\n
\n

<\/p>\n<\/div>