Code components, full-stack web apps and AI — Webflow Talk with Christian Schmitt

Level:
Preview result
Icon für einen externen Link
Im Webflow Designer öffnen und klonen
Icon für einen externen Link
Open and clone in Webflow Designer
Icon für einen externen Link

In this Webflow Talk, I talk to Christian Schmitt about the new Code Components, Webflow Cloud & Full‑Stack Web Apps. We dive into technical details, advantages over traditional API use, performance, AI generation, and future trends in Webflow.

Christian Schmitt online

Code Components & Webflow Cloud: Where is the journey going?

In the latest Webflow Talk, I talk to Christian Schmitt about the brand-new ideas about Code Components, Webflow Cloud, and AI‑generated web apps. If you're wondering what it's all good for and whether it's relevant for you too — here's your overview.

What are Code Components & Full‑Stack Web Apps in Webflow?

  • APIs are the foundation. They are interfaces that Webflow, tools, and external systems use to communicate.
  • Webflow Cloud/Full‑Stack Web Apps: Your Webflow design becomes a web app, hosted via Cloudflare, connected to a GitHub repository.
  • Code Components are small UI components that you can integrate directly into Webflow: e.g. calendars, shaders, special filters. These components can be connected to the CMS and then visually configured. Webflow's AI can generate such components with prompt input.
  • Because the code runs on the server side, you have advantages: better performance, no problem with ad blockers, no break with third-party requests.

Advantages over classic JavaScript/ API approach

CriterionClassic approachCode Components in WebflowPerformanceExternal APIs & JavaScript integrated on the server side, faster customization by customersOnly via code/developerVisually controllable in the designerAdblocker riskExternal scripts can be blocked via your own domain link with cmDetours required Direct connection possible

Limits, risks, and challenges

  • Projects are becoming more complex, not every component is trivial to use or adapt.
  • The need for support is increasing: AI is powerful, but not error-free.
  • Version control, backup & security (especially API keys!) are mandatory.
  • Not every function is usefully replaced by AI. You're more likely to want to control critical logic (such as payments) yourself.

Technology: Languages, Frameworks & Future

  • Currently is Astro.js set as a supported language in Webflow Cloud.
  • Other JS frameworks, such as Svelte, are to follow later.
  • Real-time preview in Designer
  • Switching between code/design modes are concepts that are being worked on.
  • Working with Cloudflare is moving Webflow more towards an all-in-one platform.

What does that mean for web designers and agencies?

  • You don't have to become a full-time developer, but you should start to understand how components & APIs work together.
  • With AI‐generated code modules, you can offer more technical features (e.g. filters, portals, small web apps), often faster than via classic architecture.
  • Tools such as Wized lose importance in the long term if Webflow itself can increasingly integrate visual extensions.
  • The way you work is changing: Customers can go into less technical detail, more focus is on UX & visual fine-tuning.

Tips on how to get started

  1. Follow the Webflow docs about Code Components & Webflow Cloud
  2. Generate a simple code component, such as filters or calendars, and integrate it into a project.
  3. Pay attention to security and data storage every time you use APIs & external services.
  4. Stay active in the community to see new patterns and use cases.