When specifying the behavior of a data structure component, there are often two concerns that need to be dealt with: basic functionality and support for data integrity. A data structure component is often easier to use if these two concerns are divided as much as possible into separate sets of client functions.²
Which should we choose? The rise of Flutter brought doubt to the decisions for a new mobile project. This doubt did not exist back in 2016/17 when someone needed a cross-platform mobile solution. Back in 2016/17
React Native recently added support to React hooks. Here is an overview of how to use FlatList with it.
Interesting how in ReasonML we don't need to worry much about types thanks to it's inference
The second year of the biggest conference of React in Latin America gathered big names of the Brazilian React scene. This is a summary of everything that happened.
In this Medium Post, I explain how you can automate your StoryBook set up for React Native
React introduces a component model to compose your UI. There are a couple of ways of rendering a component/JSX. You can use these simples rules to determine which way to write your component.
With the advent of ES6 and Class fields we can now write shorter components and without the need of worrying with the this keyword bind.
Should one stop using class setState for lack of understanding it.
Advantages of using class fields and Arrow functions