Technical Trigger

The introduction of gradio.Server which extends FastAPI, allowing developers to use custom frontends with Gradio’s backend engine. The @app.api() decorator is used to define API endpoints that are compatible with Gradio’s queuing engine and gradio_client.

Developer / Implementation Hook

Developers can start using gradio.Server to build custom applications with Gradio’s backend engine. They can define custom API endpoints using the @app.api() decorator and use the gradio_client to interact with their applications. The gradio.Server also supports serving static HTML files using the @app.get() decorator.

Structural Shift

The introduction of gradio.Server represents a shift from Gradio being a UI-centric framework to a more flexible backend framework that can be used with custom frontends.

Early Warning — Act Before Mainstream

To take advantage of this change, developers can start by: * Using the gradio.Server to build custom applications with Gradio’s backend engine * Defining custom API endpoints using the @app.api() decorator * Using the gradio_client to interact with their applications