![]() So we just decided to go with RN-web to get something running on web ASAP. So keeping in mind our short time notice and business criticality, we just decided to keep our learning curve low and not worrying too much about future and to use react-native-web, which currently officially supports Rn 0.55, and we are on 0.59, as we had saw some people mention they are successfully running RN-web on RN 0.59, some mentioned some hacks like making react-native-web think its RN 0.55 when compiling for web. It almost felt like we needed this conversion a couple of years too early. But we don’t live in a perfect world, do we? Turns out, react community is making great progress towards hybrid apps and PWAs but it is not yet quiet there, ionic has its react beta out, there is a project called ReactXP from microsoft and expo is also working on web compatibility of its apps. In a perfect world, we will just be putting our code through some code convertor which coverts our react-native app to reactjs web app. ![]() So as per pressure from the business side, we had to choose something where we have minimum to none learning curve. So I was tasked to do some R&D and provide a feasible plan for this conversion with minimum friction and time requirements. Yup! Just like that.Īnd incidentally, both of us had not any experience of converting apps to web. And we need to port our react-native app to web version within a week or so, knowing we are team of only two devs. And the issue is, they both need a web app instead of the mobile app, that too ASAP. Suddenly one morning, we have an emergency meeting, and the project manager tells us that we have these X and Y clients whom we are going to partner with, and these are business critical deals. On a product i am working on, they have a fully functional react-native app released in iOS app store( It did not had android builds and releases, we are planning on that as well but thats not the topic here). We had its RN version recently upgraded from 56.x to 59.9, the app IS on app store, but with not a lot of users just yet, as it is a startup still trying to get kick-started with their initial contracts and everything. And other one is Thomas Gladdines, he was so kind to help me through email with all queries i had in the process. Credits/Shoutouts:īefore we begin our journey, i wanted to give credits to a couple of people who helped a lot on this journey, first one is the Bruno Lemos, i got the react-native monorepo setup with initial react-native-web setup from his excellent blog post. You can skip Credits and background section if you like and can jump to “Let’s Just begin the actual stuff! ” section. But you should be able to have them run in the similar way as i will explain for ios below. But i will share my journey anyway.Īlso note, we did not had any active android builds, so this series won’t be explaining steps involved with building android successfully. Also my work of conversion of this app is still WIP, so who knows what and where that work ends up. I am not yet sure how many parts this series will take. So proceed with caution, and point out any improvements in the process in comments. ![]() I am mostly experienced in Ruby on Rails full stack development with mostly focus on backend and DevOps, i have worked on and off on different JS frameworks, but I am not an expert(yet) in babel and webpack configurations etc. ![]() This article assumes you already have some experience with reactjs and react-native, you know how to build mobile builds of a RN codebase, and have them run in a simulator. This series is about my journey of converting and existing react native app to render on web with same(90%+) code, using the brilliant react-native-web project which came out of twitter. ![]()
0 Comments
Leave a Reply. |