React Day
New York

I've been coding with Hooks since they were announced at React Conf last October. I write about Hooks as the managing editor of the American Express Technology Blog.

React has quickly become one of the most popular front-end libraries for creating web applications. But how much do we know about how well these interfaces work for *all* of our users, including those with disabilities or impairments?

When people think about cloud computing, they typically think about servers & back end development. This is starting to change. With the emergence of more & more powerful & sophisticated managed services like AWS AppSync, Cloudinary, Algolia, Auth0 & Firebase, it's completely possible for front-end engineers to build full-stack web & mobile applications while with almost no back-end code, relying on these services to do the heavy lifting for features like data layers, search, authentication, authorization, & more. In this talk, I'll talk about this philosophy in depth & then show how (live-code) to build a full-stack web application in just a few minutes by using React & AWS Amplify React to quickly build a real-world application complete with a GraphQL API, authentication & authorization, & hosting.

It has been one year since Discovery Communications acquired Scripps Networks Interactive to become Discovery, Inc., a leading global media organization in the real-life entertainment space. With 18 unique brands across nine platforms, Discovery is now the largest IP owner in media with an audience of consumers who are unique to each of our brands. The problem to solve became: how do we scale 162 different binaries to send to app stores, and leverage reuse of our products across brands without delivering the same experience? What resulted was one React Native codebase to cover eight of the nine platforms. Additionally, we created a layout renderer so that the application itself is not pre-built with the user experience. Instead, a personalized user experience is delivered to the application at run-time for rendering. In our React talk, we can go into more detail about what our solution to this problem offers consumers.We can also demo a number of features including: How we develop and maintain a universal component library to support multiple applications, how we handle custom product needs not shared by other applications, how we create screen layouts and customer experiences using composable atomic elements, how we handle theming and styling of generic components to be product or device specific.

It has been one year since Discovery Communications acquired Scripps Networks Interactive to become Discovery, Inc., a leading global media organization in the real-life entertainment space. With 18 unique brands across nine platforms, Discovery is now the largest IP owner in media with an audience of consumers who are unique to each of our brands. The problem to solve became: how do we scale 162 different binaries to send to app stores, and leverage reuse of our products across brands without delivering the same experience? What resulted was one React Native codebase to cover eight of the nine platforms. Additionally, we created a layout renderer so that the application itself is not pre-built with the user experience. Instead, a personalized user experience is delivered to the application at run-time for rendering. In our React talk, we can go into more detail about what our solution to this problem offers consumers.We can also demo a number of features including: How we develop and maintain a universal component library to support multiple applications, how we handle custom product needs not shared by other applications, how we create screen layouts and customer experiences using composable atomic elements, how we handle theming and styling of generic components to be product or device specific.

Codesplitting is hard. Codesplitting with type checking is even harder. Building a strongly typed system around a library built on top of generics and indirection? Now that sounds impossible. But we did it at Dropbox, and I’m here to show you how you can do it too. This talk will cover how we built a sane, code split, and strongly typed Redux store that is easy for consumers to use. I wrote a short article about this last year. This will be more in depth and better visualized Check it!

Ever wondered how to use microservices approach in a FEDmobile application? hesitating to choose React Native for your big project? I’m here to eliminate the school of thought that React Native is mostly for small mobile applications. Around 3 years ago, with 4 developers and a few hundred lines of code, Wix started the journey with React Native. We’ve grown a lot since and in order to enable ~70 Wix mobile developers, from 15 different teams, to easily integrate their code into the app, we had to rewrite the app’s architecture, implement new framework and think more like an OS to allow each team integrate their mini app ('Module') into the main Wix’s React Native mobile platform (aka 'Engine'). A simple analogy to better understand the relation between 'Engine' & 'Module', would be the same as Chrome & Extensions or iOS & Apps. This 'Engine' includes principles like: Memory management & modules lazy loading, communication channels between modules, dependency management and code sharing. And the biggest part of the puzzle, a single native project (iOS & Android) for all modules, enabling them to test their JS modules independently without using Xcode or Android Studio. Keeping that in mind, we are still able to increase our app codebase with no limitations.

Design systems are a popular way for teams to flavor their design and development workflow. However, an often-missing ingredient in many design systems is a focus on accessibility best practices — especially when component libraries are involved. In this talk, we’ll take a look at how you can mix some commonly-used components with the ingredients of accessibility. Pair this with best practices guidance in your documentation, and you’ll have the recipe for a delectably inclusive design system.

Despite all the warnings, our team has been fetching data with React Suspense since it was introduced last year. In this talk, I'll talk about some of the challenges we faced and some of our solutions as well as what to expect from the React core team later this year.

Storybook is an open source tool for developing UI components in isolation for React, Vue, and Angular. It makes building stunning UIs organized and efficient. John has spent the past few months working with Storybook. He has been successful creating a Storybook for a React component library called Kendo UI, which you can see here: kendoreact - storybook.netlify.com. This talk would provide attendees with an overview of what Storybook is, how it works, how it can be used in a development environment for component development, and highlight many examples of Storybook in the real world. It should inspire React developers to incorporate it into their development workflow/ process.

We are all talented designers and engineers that strive to create the best user experience. Unfortunately, we don’t always know what the best user experience is until a new feature is in production and used by our customers. That’s where the power of A/B testing comes into play! At Netflix, we are constantly running A/B tests to improve our user experience. Find out how to handle A/B testing at scale, what it takes to build the optimal test, and how to start implementing A/B tests within your company.

You will enjoy a delicious dinner at Brooklyn Bowl, and then you will have the change to play bowling or dance to the rhythm of great music from a Dj while enjoying a drink or a cocktail.