Nowadays there are a lot of UI frameworks for React like Bootstrap, UIKit, Semantic UI and so on. Depending on the project complexity and requirements, you decide which front-end framework would be used because the main reason is to ease your development process.

The last days I am spending time on learning GraphQL and how its clients communicate between frontend and backend application parts.

After React Hooks introduction at React Conf October 2018 I decided to learn this approach how to use state and side-effects in React functional components.

There are many tools available for designers to create beautiful user interfaces and user experiences. And today I want to share another approach on how to build interactive design prototypes with ReactJS and why.

In this post, I explain how you can find any user on GitHub through GitHub API using ReactJS, Redux, Saga, Axios, and Formik.

Why do we need to use this technology stack? Here is the short description:

These days, we are bridging the communication gap between human and computer. The next big thing is a conversational interface — the era of natural language processing. To highlight the point, nowadays there are two kinds of a conversational interface — virtual assistants (Siri, Alexa) and chatbots (like Slackbot, Telegram), which through “human” experience help end user to complete the specific task.

When I was learning React there were a couple things that I couldn’t clearly understand and one of them was children prop. That is until I faced the problem similar to the following one.

Here we are! Due to my master thesis at the university, one of the requirements is the implementation of an interactive mockup for the university WebTV platform. So, I decided to make it with React.

The last days I am working on the project, which should include the state machine. Implementing this project with React, I decided to use the Redux framework to manage state in my React application. Moreover, thanks to redux store we can debug data (in one place) easily.

The way, how I try to understand the purpose of any framework is to use it and compare with the already implemented no-framework solution.

Sure, most of us, at first hear about a new library from tech media portals or from tech-dev influencers or from conferences/meetups or from coworkers, etc. then we are going to check out the source of it whether it is a software or open-source product. In the end, we are playing with it and trying to apply it to the existing product.