React Native - Separate View and Logic










0















Is separate view and logic (like java class and xml in Android) in React Native is best way to increase app performance? Any reference for this guys?










share|improve this question


























    0















    Is separate view and logic (like java class and xml in Android) in React Native is best way to increase app performance? Any reference for this guys?










    share|improve this question
























      0












      0








      0








      Is separate view and logic (like java class and xml in Android) in React Native is best way to increase app performance? Any reference for this guys?










      share|improve this question














      Is separate view and logic (like java class and xml in Android) in React Native is best way to increase app performance? Any reference for this guys?







      react-native






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 14 '18 at 4:03









      Husni KamalHusni Kamal

      297




      297






















          1 Answer
          1






          active

          oldest

          votes


















          0














          In terms of app performance it wont really matter because in the end it all gets combined into a single JS bundle file. But separating render and business logic is always useful. It lets you rewrite business logic without having to navigate render logic when you want to make a change and also helps reuse business logic elsewhere in your app if you need to.



          A simple example is something we evaluated at work, we have a react native application and a react website. A lot of our business logic of API handling data parsing and storage and redux handling was similar if not exactly the same on both platforms. What we realised is that if we write all the business logic separately we could simply write it once and use it on both platforms and only our render logic could change. Now it is more complicated than my explanation of course but it is possible.



          Hope this helps.






          share|improve this answer























          • thanks bro, it's very useful. umm, is there a library for separating logic from view bro? 😂 @Nemi Shah

            – Husni Kamal
            Nov 14 '18 at 6:33











          • Well no there is not, and unfortunately there is not any easy way of separating logic if your app is close to being done We ended up having to refactor our code base sadly which took longer than we like to admit. But glad I helped.

            – Nemi Shah
            Nov 14 '18 at 7:47










          Your Answer






          StackExchange.ifUsing("editor", function ()
          StackExchange.using("externalEditor", function ()
          StackExchange.using("snippets", function ()
          StackExchange.snippets.init();
          );
          );
          , "code-snippets");

          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "1"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53293033%2freact-native-separate-view-and-logic%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          In terms of app performance it wont really matter because in the end it all gets combined into a single JS bundle file. But separating render and business logic is always useful. It lets you rewrite business logic without having to navigate render logic when you want to make a change and also helps reuse business logic elsewhere in your app if you need to.



          A simple example is something we evaluated at work, we have a react native application and a react website. A lot of our business logic of API handling data parsing and storage and redux handling was similar if not exactly the same on both platforms. What we realised is that if we write all the business logic separately we could simply write it once and use it on both platforms and only our render logic could change. Now it is more complicated than my explanation of course but it is possible.



          Hope this helps.






          share|improve this answer























          • thanks bro, it's very useful. umm, is there a library for separating logic from view bro? 😂 @Nemi Shah

            – Husni Kamal
            Nov 14 '18 at 6:33











          • Well no there is not, and unfortunately there is not any easy way of separating logic if your app is close to being done We ended up having to refactor our code base sadly which took longer than we like to admit. But glad I helped.

            – Nemi Shah
            Nov 14 '18 at 7:47















          0














          In terms of app performance it wont really matter because in the end it all gets combined into a single JS bundle file. But separating render and business logic is always useful. It lets you rewrite business logic without having to navigate render logic when you want to make a change and also helps reuse business logic elsewhere in your app if you need to.



          A simple example is something we evaluated at work, we have a react native application and a react website. A lot of our business logic of API handling data parsing and storage and redux handling was similar if not exactly the same on both platforms. What we realised is that if we write all the business logic separately we could simply write it once and use it on both platforms and only our render logic could change. Now it is more complicated than my explanation of course but it is possible.



          Hope this helps.






          share|improve this answer























          • thanks bro, it's very useful. umm, is there a library for separating logic from view bro? 😂 @Nemi Shah

            – Husni Kamal
            Nov 14 '18 at 6:33











          • Well no there is not, and unfortunately there is not any easy way of separating logic if your app is close to being done We ended up having to refactor our code base sadly which took longer than we like to admit. But glad I helped.

            – Nemi Shah
            Nov 14 '18 at 7:47













          0












          0








          0







          In terms of app performance it wont really matter because in the end it all gets combined into a single JS bundle file. But separating render and business logic is always useful. It lets you rewrite business logic without having to navigate render logic when you want to make a change and also helps reuse business logic elsewhere in your app if you need to.



          A simple example is something we evaluated at work, we have a react native application and a react website. A lot of our business logic of API handling data parsing and storage and redux handling was similar if not exactly the same on both platforms. What we realised is that if we write all the business logic separately we could simply write it once and use it on both platforms and only our render logic could change. Now it is more complicated than my explanation of course but it is possible.



          Hope this helps.






          share|improve this answer













          In terms of app performance it wont really matter because in the end it all gets combined into a single JS bundle file. But separating render and business logic is always useful. It lets you rewrite business logic without having to navigate render logic when you want to make a change and also helps reuse business logic elsewhere in your app if you need to.



          A simple example is something we evaluated at work, we have a react native application and a react website. A lot of our business logic of API handling data parsing and storage and redux handling was similar if not exactly the same on both platforms. What we realised is that if we write all the business logic separately we could simply write it once and use it on both platforms and only our render logic could change. Now it is more complicated than my explanation of course but it is possible.



          Hope this helps.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 14 '18 at 4:47









          Nemi ShahNemi Shah

          37138




          37138












          • thanks bro, it's very useful. umm, is there a library for separating logic from view bro? 😂 @Nemi Shah

            – Husni Kamal
            Nov 14 '18 at 6:33











          • Well no there is not, and unfortunately there is not any easy way of separating logic if your app is close to being done We ended up having to refactor our code base sadly which took longer than we like to admit. But glad I helped.

            – Nemi Shah
            Nov 14 '18 at 7:47

















          • thanks bro, it's very useful. umm, is there a library for separating logic from view bro? 😂 @Nemi Shah

            – Husni Kamal
            Nov 14 '18 at 6:33











          • Well no there is not, and unfortunately there is not any easy way of separating logic if your app is close to being done We ended up having to refactor our code base sadly which took longer than we like to admit. But glad I helped.

            – Nemi Shah
            Nov 14 '18 at 7:47
















          thanks bro, it's very useful. umm, is there a library for separating logic from view bro? 😂 @Nemi Shah

          – Husni Kamal
          Nov 14 '18 at 6:33





          thanks bro, it's very useful. umm, is there a library for separating logic from view bro? 😂 @Nemi Shah

          – Husni Kamal
          Nov 14 '18 at 6:33













          Well no there is not, and unfortunately there is not any easy way of separating logic if your app is close to being done We ended up having to refactor our code base sadly which took longer than we like to admit. But glad I helped.

          – Nemi Shah
          Nov 14 '18 at 7:47





          Well no there is not, and unfortunately there is not any easy way of separating logic if your app is close to being done We ended up having to refactor our code base sadly which took longer than we like to admit. But glad I helped.

          – Nemi Shah
          Nov 14 '18 at 7:47

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53293033%2freact-native-separate-view-and-logic%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          這個網誌中的熱門文章

          How to read a connectionString WITH PROVIDER in .NET Core?

          In R, how to develop a multiplot heatmap.2 figure showing key labels successfully

          Museum of Modern and Contemporary Art of Trento and Rovereto