Web development at Memo Bank

Decisions were ultimately based on the following criteria (in order of importance):

As you can see below, React clearly stands out in the community.

Productivity is a pillar argument for all of them, so we settled the matter on the basis of maintainability and chose to use React.

JavaScript is a dynamically-typed language; it doesn’t require us to define the data types of our constructs before we can use them. Instead, type-checking is performed at runtime. This can be convenient, but it has the drawback of not protecting us against type errors.

JSX offers many advantages. The view and logic, typically separated in different files due to different technologies, are now reunited. Everything about the component is housed in the same file and is compiled with compilation checks. Also, there are no new attributes to learn — like ng-something in Angular or v-something in Vue — just plain old HTML and {} to insert JavaScript.

The strength of component-based architectures lies in composition. A component can use other components to render itself, ending up in a hierarchy of components, just like a DOM hierarchy, but with less noise and more semantics.

React is a library rather than a framework. Compared to Angular for example, which admittedly is very complete, but is also rather opinionated about how to structure your app, React is very flexible and doesn’t impose anything.

As we’ve seen, React offers a good way to separate the app into small components, but it doesn’t give a lot of guidance on how to make these components communicate.

A component can easily pass down properties to its own children in the hierarchy tree, and these properties can be callbacks to communicate information up to the ancestors. However, communicating with neighbors tends to be complicated, involving a common ancestor, making it hard to follow and debug.

This case is quite trivial, but already adds a lot of noise. This will accumulate with each new feature and eventually make the app a big mess.

With React and Redux in place, we now have small and reusable components with clear responsibilities and a very decoupled way to communicate between them.

The name of this library is quite self-explanatory. It allows the creation of components that possess their own encapsulated style. This removes the need to map styles and components together. In other words, we don’t need to define class names anymore!

We can extend existing styled-components using extend() or convert any regular component using styled(MyComponent). Our JSX code can now consist solely of components like <MyComponent>, instead of using <div> with class names everywhere, which makes it easier to read.

Now that the whole component, including its style, is bundled in a single JS file, it’s easier to grasp, and also easier to share.

We wanted to have the same notion of a ‘components library’ in our code. They needed to be easily browsable and documented in a single place. Also, we have two codebases (back-office and front-office), and we need a way to reuse the components in both places.

First, we extracted some of our components in a library and deployed it to NPM. Then, we looked for ways to make those components browsable directly in the browser.

Note that when we edit the code displayed in the browser, the live view updates itself automatically.

By carefully documenting all our shared components, we lay the groundwork for all future developments.

React with JavaScript/Flow seems like a safe bet in 2018. It allows us to build our apps with small reusable components in a language guaranteed to be supported for a very long time. These components are entirely self-contained using styled-components and only communicate with each other using props and redux. We’re building for the future by encapsulating all common components in a self-documented, carefully-tested shared library, in sync with the initial designs on Sketch, using styleguidist.

All of this combined allows us to keep a maintainable code base, be productive, and remain invested in a strong development community.

Related posts:

bibit pisang mas kirana cepat berbuah berbunga dan terlaris termurah maseeeeee bibit pisang mas kirana ukuran : 30–55 cm hasil : bonggol 1.Cepat tumbuh ,Cepat berbuah dan dipastikan Bakal Berbuah…

You will never understand until it happens to you. This sentence is used a lot in the context of trying to explain different traumas to people who have never went through it. It’s hard to explain…

Page speed is often confused with “site speed,” which is actually the page speed for a sample of page views on a site. Larby Amirouche, a digital marketing expert defines it as either “page load…