the React Native vs Native App development comparison<\/a>), we believe React Native apps are a great addition to a web project. Such development significantly cuts Time to Market and lets you outpace the competitors at no additional expense. You\u2019ll still need to write a bit of platform-specific code but you\u2019ll also get to reuse many components, saving you even more time.<\/p>\n\nWhen to use ReactJS?<\/h2>\n\n
The above mentioned reasons make for a compelling case to use React in many different scenarios. The obvious choice will be sites relying heavily on user interaction with the elements. This will be especially true if the state of components frequently changes – navigation pops up and disappears, users log in, content or e.g. buttons change after users\u2019 interaction. Thanks to Virtual DOM, React will be able to manage each of these changing states easily and dynamically present the content to end users.<\/p>\n\n
React will be also a great choice if a website comes with a very complex structure that might be hard to keep track of with a traditional, imperative approach. As the application scales, React will allow you to easily keep track of all the interactions.<\/p>\n\n
When not to use ReactJS?<\/h2>\n\n
Over the years, the React library became so robust and flexible that it can be used for nearly any frontend project. There might be, however, cases when using React is possible but there are likely just better suited approaches. This will mostly apply to very simplistic pages with few elements, such as landing pages or simple websites with little customization or without lots of dynamic content and rich stateful interactions. For such projects, a simple HTML generated by a backend and a bit of JavaScript might be enough. With the abundance of simple and inexpensive web generators, such sites can be brought to life in no time. Deploying ReactJS could be simply overkill. But, if you plan to add much more interaction to the website in the near future, go for ReactJS from the beginning.<\/p>\n\n
Don\u2019t use React with heavy, complex admin panels. A much better approach are typical backend frameworks that are more tightly coupled to database structure. React works best with a lot of workflows and interactions, you likely won\u2019t need much of that. To code typical admin panel functionalities such as tables or user permissions, backend frameworks will require much less code than framework-focused ReactJS. As such, it might be easier to stick with backend frameworks from the get-go and keep React for more frontend-focused developments.<\/p>\n\n
Finally, as mentioned in the beginning React is fairly easy to learn for any JavaScript developer. There is, however, a higher learning curve if your developers never worked with JS before and it\u2019s something to consider. ReactJS follows the flux architecture and this concept might be harder to grasp for developers used to different approaches (like MVC for example).<\/p>\n\n
Summary<\/h2>\n\n
ReactJS is in many ways a revolutionary approach to building both frontend and mobile apps. It\u2019s quickly grown to be the favourite tool for many JavaScript developers and it looks like it\u2019s here to stay. We absolutely love using it with our products and will definitely continue doing so for years to come. If you\u2019re still hesitating between React and other frameworks\/libraries, give us a shout and we\u2019ll be happy to suggest the best approach.<\/p>\n","protected":false},"excerpt":{"rendered":"
There are many reasons why ReactJS is our favourite JavaScript library. If you’re still not sure whether it will work for your project, check out our article!<\/p>\n","protected":false},"author":77,"featured_media":12018,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3],"tags":[],"coauthors":["Piotr Ma\u0142ek"],"class_list":["post-12009","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-development"],"acf":[],"aioseo_notices":[],"categories_data":[{"name":"Engineering","link":"https:\/\/railsware.com\/blog?category=development"}],"post_thumbnails":"https:\/\/railsware.com\/blog\/wp-content\/uploads\/2019\/07\/Why-we-use-ReactJS-for-our-projects-Illustration.jpg","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/posts\/12009","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/users\/77"}],"replies":[{"embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/comments?post=12009"}],"version-history":[{"count":15,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/posts\/12009\/revisions"}],"predecessor-version":[{"id":13711,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/posts\/12009\/revisions\/13711"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/media\/12018"}],"wp:attachment":[{"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/media?parent=12009"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/categories?post=12009"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/tags?post=12009"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/coauthors?post=12009"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"Why](\"https:\/\/railsware.com\/blog\/wp-content\/uploads\/2019\/07\/Why-we-use-ReactJS-for-our-projects-Illustration.jpg\")
<\/p>\n\n