React Native - Separate View and Logic
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
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
add a comment |
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
add a comment |
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
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
react-native
asked Nov 14 '18 at 4:03
Husni KamalHusni Kamal
317
317
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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.
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
add a comment |
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
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.
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
add a comment |
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.
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
add a comment |
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.
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.
answered Nov 14 '18 at 4:47
Nemi ShahNemi Shah
40138
40138
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
add a comment |
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
add a comment |
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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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