FG x React

While our teams are solution-agnostic, there are a few instances where we group together to learn and specialize in various techniques, strategies, and frameworks. Forest Giant’s development team is in the process of expanding the team’s expertise by focusing on React, a prominent JavaScript library for building user interfaces.

The front-end framework and library space is volatile. With new frameworks and libraries popping out into cyberspace every year, it’s difficult to keep switching to the next shiny object in our path. By adopting a single tech stack that all of our team is knowledgeable in, we’re able to build more expertise and come on to a project with that shared knowledge and experience.

So why React? We spoke to the team to find out.

For Matt Adams, FG software engineer, React is great for several reasons. “Speed of development, code reuse, limited boilerplate, freedom of extensibility, and excellent performance come to mind, just to name a few,” Adams mentioned. “It’s clear to read, fun to write, and doesn’t try to do too much–it lets you implement things like state management and routing the way you want to, rather than forcing you into implementing these things its own way.”

Jesse Lucas, CTO, piggybacked on React’s openness to implementation. “React isn’t as opinionated as something like Angular, for example. You can make decisions and have the freedom to solve based on your team and the project at hand.”

In addition to React’s freedom, there’s a strong benefit for clients that elect to use React in their projects.

“By adopting a standard framework and creating tools and systems around it, we’re able to make front-end iterations faster than before,” Lucas commented. “While designers are iterating within Invision, we’re also able to follow along with low-fidelity mockups to get the concept into reality as quickly as possible.”

While React is certainly being looked at as one of Forest Giant’s specialities, not all projects will automatically use the library. “In the end, we use the best tools for the project at hand. It could be React, it could be Angular, etc. While our team is beginning to specialize in React, if a project is best served with another solution, that’s the direction we’re going to go,” said Dave Durand, CEO. “We do what’s best for the client, may it be React or otherwise.”

At the time of writing, two projects are React-based with many more in the pipeline. Our development teams are working together to create internal databases of React components for even quicker development cycles for new and existing projects. We look forward to crafting the future with React!

Jessica Elle
Digital Marketing