React on the Blockchain - the Missing Getting Started Guide

React Summit Remote Edition

React Summit Remote Edition 2021

Vladimir Novick

Create Collaborative VR Environment in the Browser with React and GraphQL

React Summit

React Summit 2020

Controlling Apps with Your Mind and AI

React Summit Remote Edition 2020

Run Games Within Your React Native Apps

React Day Berlin

React Day Berlin 2022

From Prompting to Orchestrating: Coding Is Now a System

AI Coding Summit

AI Coding Summit London

AI Coding Summit Berlin

You don't need a framework to orchestrate coding agents well — you need the disciplines. In this hands-on workshop you'll take a real repo and orchestrate a small fleet by hand, reaching honest L1 Orchestrated Coding (spec: https://github.com/vnovick/orchestrated-coding) — one owner of context, worktree-per-task isolation, brief/report handoffs, an independent reviewer behind a deterministic gate. Then you'll flip on orchestra - an open-source plugin - and watch the exact same disciplines become enforced: a hook that refuses to let an agent commit, fail-closed verification that says "unverified" instead of lying. Finally I'll run the fully autonomous L3 version live. Vendor-neutral, spec-driven, nothing to buy.

Orchestrate a Fleet of Agentic Loops: From By-Hand L1 to Enforced Doctrine

Last time at AI Coding Summit London I gave you From Prompting to Orchestrating — the argument that coding with fleets of agents is a systems problem, and the spec (grounded in dozens of research papers from the major labs) that names the fix. Then I went and built that spec.  Twice. Once as an autonomous daemon that runs the whole loop for you, once as a plugin that lives inside your own coding session. The disciplines came out identical both times. The only thing that changed was who conducts the orchestra - and that turned out to be the whole lesson.  This is the sequel: what two real implementations taught me that the spec couldn't, including the two MUST-level checks my own reference implementation failed when I audited it against my own rules.

The Orchestra Plays Itself. Who Runs the Loop? Lessons from Two Spec Implementations.

AI Coding Summit NYC

Every CI vendor now ships auto-fix: a job goes red, an agent patches it, reruns, pushes to your PR. That was the easy part. The hard part is what else the agent can change while it's in there. To the agent, a test file and the workflow file are the same push. Nothing in most setups knows the difference. There's a line between fixing the build and owning the pipeline. Most teams haven't drawn it. Some don't know they need to. This talk is about where it goes, how to make CI enforce it, and why the agent that writes a fix should never be the one that says it's good.

Agents in CI Can Fix the Build. Don't Let Them Touch the Pipeline

We thought AI would help us write code faster. Instead, it's changing what coding actually is. We started with prompts, then copilots, then agents. Each step felt like a leap forward — until you try to build something real at scale.Because prompts don’t remember. Agents don’t coordinate. And models still hallucinate and miss context. What’s emerging instead is a different approach: not writing code line by line, but designing systems that produce, validate, and evolve code. Instead of a single assistant, we orchestrate multi-agent workflows — planning, implementing, reviewing, and testing — with shared context and feedback loops.In this talk, we’ll cover: - why prompt-based and single-agent approaches break down - how multi-agent systems reshape development workflows - practical patterns for planning, execution, validation, and control loops - where things fail — and how to make systems reliable We’ll show how structured orchestration makes agent-based systems actually work in practice — especially when moving beyond isolated, task-level automation. The shift isn’t from coding to prompting — it’s from coding to designing systems that write code.

In this talk we will see how we can bridge React Native app with commonly used game engine Unity3d for two way interaction between the game and React Native app

What is the future of user interactions? Will we continue using web and mobile or will we switch into VR and AR completely? What is our UX today on web and mobile and how it will change when the digital world will bridge into new dimensions. Would we still use keyboard and mouse or gestures or will we use something else? In this talk we will get a glimpse into the future where we will control apps with our thoughts. Literally. It’s not a thought experiment, but a journey into our brainwaves with consumer EEG headset. We will explore how we can use them and AI to create futuristic experiences, which will lay a foundation stone to our future interactions with the digital world.

Virtual Reality gives us an ability to experience virtual worlds from the comfort of our homes. But it doesn't have to be experienced alone. In this talk we will see how we can use React, WebVR and GraphQL to create social VR experience in the browser. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Blockchain is arguably a future technology that can be somewhat confusing to get started. Even though there are plenty of resources scattered across the web, but to get started developing distributed apps in React on the blockchain can sound intimidating. In this talk, Vladimir Novick will share how we can get started and what you should know about blockchain architecture. If you always wanted to get into Blockchain development and didn't know where to start, this talk is for you. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>