1 / 8

4 Powerful Reasons to Migrate to React Native or Add React Native to the Existing Native Project

Check out this presentation to make the right decision whether to switch your mobile app to React Native or not.

Apiko
Télécharger la présentation

4 Powerful Reasons to Migrate to React Native or Add React Native to the Existing Native Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 4 Powerful Reasons to Migrate Your App to React Native by www.apiko.com

  2. Contents: I.Mobile app development trends. How can the mobile app development change in the nearest future? II.When and why you might need to migrate to React Native III.Problems during the rewriting process and the ways to deal with them IV.Mini count-up list How you can save money and time with React Native. www.apiko.com

  3. I. Mobile app development current trends and the nearest future According to The State of JavaScript, back in 2017 a lot of developers preferred 'clean' Native development. Now, in 2018, this tendency is still a domainant one on the arena of JavaScript development. That’s not the verdict, though. Take a closer look at React Native and the percentage of people who ‘have USED it before, and WOULD use it again’ and the percentage of people who ‘have HEARD of it, and WOULD like to learn it’. We theorize that by the end of 2018, this piece of stats can have a completely different look with React Native leading the way or competing with Native development. I've HEARD of it, and WOULD like to learn it I've USED it before, and WOULD use it again Native Apps 7.9k 9.1k React Native 4.8k 14k www.apiko.com

  4. II. When and why might you need to migrate or merge the app with React Native? Typically there are two reasons to include React Native to your app’s stack. Let’s consider 2 bright examples: #1. You have a native Android app. You want to build an iOS version of this product too, but you don’t have enough assets and/or time, or you want to save both. React Native can be the exact option you might need. The framework provides code reuse and code sharing opportunity. It means that you can build one business logic for both iOS and Android apps. The feature that saves your development team and you more time and resources. #2. You have native Android project and React Native iOS project. You need to make some iOS app functionality available for Android app ver- sion. React Native integrates with the native Swift or Java code and you can see it in action. If the code is stable and well-written for one platform (i.e. iOS), it will work well for another one (i.e. Android). There are 3 key criteria to pay attention to, when migrating to React Native: App’s App’s business model App’s UI/UX architecture www.apiko.com

  5. III. Problems during the rewriting process and the ways to deal with them #1. If you’re using native code + React Native, you need to somehow connect both technologies by the means of ‘bridging’. This is where most of the issues take place. To help you get a better understanding of how this works, look at the scheme below: Bridge #2. Consider that you're creating a React Native app and want to imple- ment native modules there, written on your own/or by your devs team to perform complex operations. You should create a ‘wrapper’ for a certain native module to work with React Native first. For this task, your develop- ers’ team should possess the required skills, or you have to look for the experienced native + React Native developer(s). It might cause issues which rather refer to the project’s organization and team’s proficiency. Other React Native ‘borderlines’ include: ● Many consider React Native as UI layer to be the drawback. ● Native updates and APIs. When Android/iOS SDKs update, it can take some time for React Native to adjust the updated APIs to its core library. ● React Native is still young. Not v.1, not v.2 but v. 0. When any update takes place inside the React Native mechanism, prepare yourself to face popping, sometimes pointless error messages. www.apiko.com

  6. III. Problems during the rewriting process and the ways to deal with them Several recommendations on how to organize more productive coding -in-React Native process ● Use additional tools like Recompose, Redux. The current technologies, allow you to get an opportunity to test and boilerplate a lot. Apart from these, check out Expo, an open source toolchain for JavaScript+React developers ● You can merge Native technologies, like Swift (iOS) or Java (Android) with React Native if you’re building a complex app or a marketplace platform. + ● Optimize React Native animations, by keeping to the 60 FPS standard. How can you do this? - utilize ‘Animated library’, - update components with ‘shouldComponentUpdate’ - use ‘InteractionManager’. www.apiko.com

  7. IV. Mini count-up list. How can you save money and time with React Native? React Native development will help you save investments, starting from 35%. This percentage also depends on the project itself and its function- ality, especially how frequently source code can be reused for both plat- forms. In general, if the application doesn't have specific features related to one platform you can save ~40% of initial budget. For instance, you’re planning the project which would cost you $ 50k for Native iOS and Android development. React Native offers us code reuse/sharing option, which means that you or your developers’ team can write one code that suits both mobile OSs, iOS and Android. This can help you lower the cost of mobile app development to ~ $ 30k, means you can save ~ $ 20k. ~ $20k saved Lower the cost to ~ $30k www.apiko.com

  8. Get in touch with us www.apiko.com Ukraine Ternopil office Krushel’nyts’koi St., 18, 46400 mykola@apiko.com Ivano-Frankivsk office Teodora Tsoklera St., 9, 76008 mykola@apiko.com USA 4433 Merlin Way, Soquel, CA 95073 +1 650-996-2875 Jim Norris Estonia Tallinn, Harju maakond Pae tn 25-47, Lasnamäe linnaosa 11414

More Related