Developer Experience Weekly — 2026-04-20

Key Highlights

Google Ads: April 2026 Display & Video 360 API Update

Google announced the April 2026 update to the Display & Video 360 API this week, including support for additional features on the advertising platform. The update is part of Google's regular cadence of API maintenance for its advertising developer ecosystem.

HERE Platform: New Documentation Site with Conversational AI

HERE launched a new product documentation site at docs.here.com as part of its April 2026 Platform Release Notes. Key improvements include enhanced navigation and search, plus a conversational "Ask AI" interface that enables developers to query documentation in natural language. The update also flags an action required: the Pipeline Stream-6.1 runtime environment for stream pipelines will be deprecated on May 1, 2026. Developers relying on HERE APIs, SDKs, and data services should review migration requirements before that deadline.

Mintlify: Enterprise API Developer Portal Evaluation Framework

Mintlify published a guide this week evaluating API developer portals across seven key areas: branding, governance, API reference quality, documentation maintenance automation, AI-agent readiness, analytics, and onboarding experience. The guide emphasizes that the right platform choice depends on shipping velocity, documentation contributor structure, and whether AI agent traffic to documentation is a priority — a forward-looking criterion reflecting the growing use of LLMs that read and act on API docs programmatically.

Analysis

What Makes a Great Developer Experience in 2026: The AI-Documentation Intersection

The HERE platform update and the Mintlify enterprise guide both point to an emerging design principle: developer documentation is no longer just for human readers. HERE's new "Ask AI" interface and Mintlify's explicit mention of "AI-agent readiness" as a portal evaluation criterion reflect a structural shift — documentation must now serve automated agents and LLM-powered tooling, not just the engineers who land on a docs page.

This aligns with the insight from GetDX's 2026 developer experience guide, which notes that inline code documentation increasingly serves both human readers and AI assistants — structured docstrings and type annotations now directly affect the quality of AI code suggestions developers receive in their IDEs.

The practical implication: teams investing in DX infrastructure should audit whether their documentation architecture is structured for machine readability (semantic markup, consistent schemas, type-annotated references) and not just human browsability. A portal that looks polished to engineers may still fail AI agents querying it programmatically.

Three dimensions still define core DX quality:

GetDX's 2026 framework continues to center developer experience on three core dimensions — feedback loops, cognitive load, and flow state — offering a measurement baseline for engineering orgs trying to quantify improvements.

What to Watch

• HERE Pipeline Stream-6.1 Deprecation — Teams using HERE's stream pipeline runtime have until May 1, 2026 to migrate. Review the HERE April Platform Release Notes for action items.

• OpenAI Assistants API Sunset — OpenAI has announced plans to sunset the Assistants API in 2026 (anticipated, after achieving full feature parity with the Responses API). Developers building on Assistants should begin tracking the Responses API migration path.

• Internal Developer Portal Strategy — Cortex published a practical framework guide for planning, deploying, and measuring Internal Developer Portal (IDP) initiatives in 2026, worth a read for platform engineering teams defining Q2–Q3 roadmaps.