React.js is the JavaScript library developed by Facebook and Instagram to create fast and reusable user interfaces.
Introducing new development paradigms and best practices to the frontend, it has gathered a large and active community of developers.

The conference is organized by GrUSP, the organizers of jsDay, in partnership with FEVR.

ReactJS Day

Theming with React is not always as straight-forward as we would like it to be. Often we rather style our CSS leading to masses of unneeded and convoluted classes. With universal JavaScript, React Native and Javascript for styles we may want a mechanism that's coupled more deeply into React. In this talk, we will explore current common approaches to this problem and how we can take a step further to create React-coupled theming.

Individual paint for your React components

Following the "React: CSS in JS" talk of @vjeux in late 2014, a plethora of discussion, prototypes and implementations followed that realized his ideas or expanded on them. One of the concepts that emerged is the notion of CSS Modules in mid 2015. 

In this talk I want to share my lessons learned after getting hands-on experience with CSS Modules in a shipped customer project and working on an open-source project that utilizes them. In particular I want to talk about their advantages over the other solutions but also about their shortcomings.

CSS is dead, long live CSS but in modules, please!

“Everything fails all the time”. True for every software project, especially for a large and complex JS project. In this session we are gonna explore testing and monitoring techniques to deliver and maintain a ReactJS + Redux application, and at the same time being able to go back to sleep without the fear that everything is gonna explode during the night.

How to push a ReactJS application in production...

We all like building User Interfaces with React. But what happens when our application is showing a 3D world, virtual-reality-like, using WebGL Should we leave the UI in the DOM, flat and out of the 3D environment? Or could React.js be used to build a UI *inside* the 3D world? And what if we wanted to share the business logic code between 3D and 2D versions of the UI?

Reactive Reality

"Anything that can be derived from the application state, should be derived. Automatically". This is the philosophy behind MobX, a new state management library for JavaScript applications. During this talk we will know the pros and cons of this API, comparing it to other state management libraries, and use it in a React application.

Stay Reactive with MobX

I will explore a modular approach that allows for better code reusability and isolation of concerns when building React+Redux Applications. Based on github.com/gianmarcotoso/redux-seed

Building Modular Redux Applications

At SpareBank1, Norway's second largest bank, we've used React in production for about two years. This past year we've introduced both React and Redux to the largest branch of the organization - the online banking app for desktop. This means writing all new features in React, and gradually re-writing our old pages as their near their end-of-life. 

The interesting part is how we've lifted our frontend collaboration to the organizational level. We've created a shared component library - meaning hundreds of npm modules containing all you need to create a large and modern SPA. This includes having an automatically updated design guide utilizing these components, also serving as a platform for discussion between frontend devs, graphical and interaction designers. 

Having close to 150 developers and designers working together across 20+ teams and application - really is frontend at scale. This talk can be seen as a natural continuation of my 2015 ReactJS Day talk "How We Used React To Tame The SPA Beast", although having seen it is definitely not a requirement.

Frontend At Scale - Experiences Using React In A Large Organization

Have you asked yourself this question? I have. In this talk I share with you what I found out and why should you care.

What the hell is graphQL and why should I care

No matter how good you are as a developer and how many tests you write: your application will throw errors. At YPlan we tried to catch all the exceptions and handle them in the right way to give our users the best possible experience. In this talk, I will go through the problems we tried to solve and the solutions we implemented #forreal

ReactJS Day 2016

Oct 7 | Verona, Italy