In a web app, the enemy of performance isn't bad algorithms — it's bloat. From loading the least data and JavaScript to re-rendering the fewest components in response to changes in state, the most performant apps are the one that do the least. But it's often hard to maintain a small bundle while iterating on features.

Enter Isograph, the framework for building data-driven React apps. It leverages a compiler to provide great DevEx and performance, right out of the box.

In this talk, find out how Isograph lets you:

• load component JavaScript and data only when needed, for example when the user is about to scroll to them

• load components (such as a VideoViewer) only if an item of that type (a Video) is returned from the server, and

• defer loading parts of your component tree, without server support.

And the cherry on top? We're doing it all in userland. 😎

But wait, there's more! We'll also show how Isograph re-renders the absolute minimum of components and garbage collects data that's no longer needed, allowing your app to stay consistently performant. So let's prove the old adage: less is more performant.

When writing a fullstack application a common problem facing developers today is keeping data consistency between the frontend and backend. What the backend expects and what the frontend sends is not always the same.

In this talk we’ll look at this problem and different approaches to solve it. We’ll take a look at how AWS Amplify approaches this problem and show a demo. We’ll also compare and contrast other TypeScript approaches with React and Next.