惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

WordPress大学
WordPress大学
Microsoft Azure Blog
Microsoft Azure Blog
aimingoo的专栏
aimingoo的专栏
Vercel News
Vercel News
U
Unit 42
L
LangChain Blog
J
Java Code Geeks
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
The Cloudflare Blog
F
Fortinet All Blogs
小众软件
小众软件
I
InfoQ
P
Proofpoint News Feed
D
DataBreaches.Net
Martin Fowler
Martin Fowler
H
Help Net Security
T
Tailwind CSS Blog
N
Netflix TechBlog - Medium
有赞技术团队
有赞技术团队
Y
Y Combinator Blog
Recent Announcements
Recent Announcements
B
Blog RSS Feed
酷 壳 – CoolShell
酷 壳 – CoolShell
B
Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Google Just Declared the Chat-Log Interface Dead. Here's ...
Om Shree · 2026-05-23 · via DEV Community

Every AI product launched in the last three years ships the same interface: a text box, a send button, a scrolling wall of markdown. Google just called that paradigm out by name - and shipped a replacement.

The Problem It's Solving

The chat-log format was never designed for AI. It was borrowed from messaging apps because it was familiar and fast to build. Type a prompt, get a response, scroll. For a demo, it works. At 900 million monthly active users, its limitations become the product's most visible failure.

Gemini's UI/UX lead Jenny Blackburn describes the output as "the giant wall of text" - and that framing is the honest diagnosis. Users type in questions and get back detailed written answers that require scanning, filtering, and manually unpacking paragraphs of monotone text to find anything actionable.

The deeper problem is that the chat-log format assumes the model's job ends at text generation. The user does the rendering - in their head, on their own. That works for simple factual lookups. It breaks down for anything that has structure: timelines, comparisons, processes, multi-step plans, visual data. These are exactly the use cases where AI assistance is most valuable, and exactly where a wall of markdown is least useful.

Neural Expressive is Google's structural answer to this.

How Neural Expressive Actually Works

Neural Expressive is described by Google as a vibrant, dynamic, and completely reimagined design language for Gemini. At the surface level: fluid animations, new typography, vibrant color palettes, haptic feedback, and a redesigned pill-shaped input box. That's the cosmetic read. The more consequential change is what happens to the response itself.

Gemini will now generate responses with richer formatting, including images, summaries, bolded text, interactive graphics, timelines, and even narrated videos to avoid showing users giant walls of text. The key word is "generate" - this isn't the developer manually specifying a display template. The model is making the rendering decision based on what the query actually calls for.

The redesign focuses on eliminating traditional walls of text: when users ask Gemini a question, it no longer simply outputs dense paragraphs, but instead generates customized reply formats in real time, seamlessly incorporating high-definition images, draggable interactive timelines, narrated short videos, and dynamic data visualizations.

Blackburn explains the design philosophy: "It stops feeling like you're scrolling through this endless chat log and more like the interface is organically adapting around the information that's being generated."

Voice is part of this too. Neural Expressive folds Gemini Live, the voice conversational interface, directly into the core experience, allowing users to switch between typing and speaking without breaking context. The microphone behavior was also redesigned: the underlying pause-detection logic has been reworked to allow extended pauses as users organize complex thoughts, preventing the AI from interrupting prematurely. That's a small change with a large UX impact - it's the difference between a conversation that feels interrupted and one that feels genuinely patient.

Regional accents and dialects support is also coming, signaling that this isn't just a visual redesign but a full re-thinking of the input and output layer of the AI experience.

Neural Expressive rolled out globally on May 19 across web, Android, and iOS - for all users, not just paid subscribers.

What This Means for Developers Building AI Products

This is where the story gets interesting beyond the consumer UX angle.

Blackburn articulates the underlying principle: "We think that as this technology becomes more capable, the interface should actually get simpler. Instead of you as a user having to learn and adapt to the software, which has been how software has been forever, we really see a future where the software adapts to the user and takes into account their specific needs."

That's a design philosophy, but it has direct implications for anyone building AI-powered products. Most AI applications today expose the same chat-log paradigm that Neural Expressive is retiring: a text output rendered in markdown, maybe with some syntax highlighting if there's code. The UX burden sits entirely with the developer - you choose the layout, you decide when to show a table versus a list, you decide what a "good" response looks like visually.

What Google is demonstrating with Neural Expressive is that this decision can be model-driven. The model knows whether the user asked for a timeline, a comparison, a step-by-step guide, or a quick factual answer - and the interface should render accordingly, not force every response into the same text container.

For developers building on Gemini API or Vertex AI, the practical question is whether Google exposes the rendering signals that power Neural Expressive at the API level - structured output types, response format hints, media embedding signals - so that third-party applications can build the same adaptive rendering behavior rather than always falling back to raw text. That API surface isn't publicly documented yet, but it's the natural next step if Google wants this design philosophy to propagate beyond its own apps.

The redesign also allowed the team to integrate Gemini Omni into the chatbot, which is the company's newly announced AI-video generating application. Together, it allows people to input a combination of images, audio, video, and text to generate and edit a video - all within the same interface. That integration is a direct consequence of the design architecture: when your response layer can render anything, you can connect any generative model to it without building a new product surface.

Why This Is a Bigger Deal Than It Looks

The chat-log format is the shared default of every major AI assistant - Claude, ChatGPT, Copilot, Gemini until now. It's the first layer users see and the layer that shapes what they think AI is capable of doing. When most people's experience of AI is "I type, it writes back in a text box," their mental model of the technology stays narrow.

The delivery format of AI-generated content is evolving from static Markdown text to dynamic, living layouts. That shift has been happening at the application layer in specialized tools for a while - AI-powered dashboards, code editors, research platforms. Neural Expressive is Google making it the default at the general-purpose assistant layer, for 900 million users simultaneously.

The benchmark this sets matters. When Gemini responds to a project planning question with an interactive draggable timeline rather than a bulleted list, and a competitor's assistant responds with the same markdown it's been generating since 2023, the comparison is visceral. The interface gap becomes the product gap.

For developers who have been treating AI UI as a solved problem - prompt box, output area, done - Neural Expressive is the clearest signal yet that the interface layer is where the next round of differentiation will happen.

Availability and Access

The Neural Expressive redesign is rolling out globally across Android, iOS, and the web for all Gemini users as of May 19. It ships alongside Gemini 3.5 Flash as the new default model. The full Gemini 3.5 Pro model is planned for June.

The chat log era had a good run. Google just ended it with a design language name and a global rollout. Whether competitors follow - or build their own version of adaptive rendering - will define what AI interfaces look like for the next few years.

Follow for more coverage on MCP, agentic AI, and AI infrastructure.