This talk is a deep dive on how React concurrently renders to provide time slicing and touches on concurrent hooks like useTransition and useSyncExternalStore.

Writing complex UI and maintaining it can be hard. Writing tests help, but writing tests is also hard. Storybook can help with both, and provide auto documentation for your components.

Migrating a production app is not an easy feat, especially if it's actively being used by over a million people. In this talk, we'll explore how we rebuilt our homepage and product page on the app directory using next.js 13. We'll highlight some of the challenges we faced and the solutions we came up with

Work or life? Find a balance without a painful choice. Learn tips on how to manage and succeed in both fields. Olga will go deep into the significance of self-care, time management, and the importance of individual needs and values.

In this talk, Taz will dive into the skepticism of building React Native Apps for the Web, including everything from design systems and navigation to ExpoGL and Reanimated, from how they’ve successfully built Guild on top of this architecture.

An open discussion with GraphQL experts and the audience live in New York City to chat about what they're seeing in the GraphQL space 🙌🗽

In this talk, I will dive into the skepticism of building React Native Apps for the Web, including everything from design systems and navigation to ExpoGL and Reanimated, from how they’ve successfully built Guild on top of this architecture.

Runes are all the rage these days. They're the new way we handle reactivity in Svelte.

Learn:

• What they are

• How they work

• How to use them

Since OpenAI released ChatGPT in late 2022 we've seen a lot of very interesting things pop up in the AI space. Among them are things like Vercel's v0 and openv0. In this talk we'll take a look at how to leverage these tools to build Svelte components.

Writing one component is easy. Conditionally rendering two different ones is still not hard. But what if you face an "n" number of permutations. "n" number of different UI elements and scattered business logic? Switch statements all over the place. Might not sound scary when we write the code. What about your future self? Cognitive load fires off the roof. Maintaining your code? Onboarding new devs? Good luck. Sounds all too familiar? Let's see a possible solution how to tame complexity. How to tackle a large number (possibly infinite) of branches in a frontend codebase without losing our sanity.