Doing the Bare Minimum with Isograph

Presentation byRobert Balicki

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.

Similar Presentations
Cover Photo for Vike: Modular React Framework

Vike: Modular React Framework

React frameworks like Next.js and Remix restrict and dictate your stack in ways they shouldn't.

Vike is a (React) framework designed from the ground up to be modular:

  • Choose your architecture: SPA/SSR/SSG, RPC/GraphQL/REST, server/static/edge deployment, ...
  • Use tools with zero-config integration (Vike extensions) or fully control integration code.

Vike embraces the do-one-thing-do-it-well philosophy for unprecedented flexibility and stability. For example, if you have an existing backend with a GraphQL API, then you don't need Server Actions. With Vike, you can use React your way — such as first-class support for GraphQL instead of Server Actions.

Your stack, your choice.

Rom Brillout

Doing the Bare Minimum with Isograph

Presentation byRobert Balicki

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.

Similar Presentations
Cover Photo for Vike: Modular React Framework

Vike: Modular React Framework

React frameworks like Next.js and Remix restrict and dictate your stack in ways they shouldn't.

Vike is a (React) framework designed from the ground up to be modular:

  • Choose your architecture: SPA/SSR/SSG, RPC/GraphQL/REST, server/static/edge deployment, ...
  • Use tools with zero-config integration (Vike extensions) or fully control integration code.

Vike embraces the do-one-thing-do-it-well philosophy for unprecedented flexibility and stability. For example, if you have an existing backend with a GraphQL API, then you don't need Server Actions. With Vike, you can use React your way — such as first-class support for GraphQL instead of Server Actions.

Your stack, your choice.

Rom Brillout

Get in touch!

hi@guild.host