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

推荐订阅源

N
News and Events Feed by Topic
Malwarebytes
Malwarebytes
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
C
Cybersecurity and Infrastructure Security Agency CISA
F
Future of Privacy Forum
C
Cisco Blogs
T
The Exploit Database - CXSecurity.com
A
Arctic Wolf
S
Securelist
K
Kaspersky official blog
S
Schneier on Security
T
ThreatConnect
T
Tenable Blog
Spread Privacy
Spread Privacy
T
True Tiger Recordings
AWS News Blog
AWS News Blog
F
Fox-IT International blog
量子位
T
Threatpost
V
Vulnerabilities – Threatpost
C
CERT Recently Published Vulnerability Notes
Cisco Talos Blog
Cisco Talos Blog
GbyAI
GbyAI
宝玉的分享
宝玉的分享
腾讯CDC
G
Google Developers Blog
aimingoo的专栏
aimingoo的专栏
Cyberwarzone
Cyberwarzone
有赞技术团队
有赞技术团队
S
SegmentFault 最新的问题
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
V
Visual Studio Blog
U
Unit 42
雷峰网
雷峰网
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
Simon Willison's Weblog
Simon Willison's Weblog
O
OpenAI News
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The GitHub Blog
The GitHub Blog
The Register - Security
The Register - Security
MyScale Blog
MyScale Blog
小众软件
小众软件
A
About on SuperTechFans
Last Week in AI
Last Week in AI
Y
Y Combinator Blog
博客园 - 三生石上(FineUI控件)
美团技术团队
Google Online Security Blog
Google Online Security Blog
P
Proofpoint News Feed
MongoDB | Blog
MongoDB | Blog

DEV Community

Avoid Cross Module Dependencies with Dependency Cruiser Invariant-Driven Architecture: 20M transactions on a €80/mo Cloud VM. Stop using external npm packages just to generate a UUID v4 Choosing the Right Gemma 4 Model Matters More Than Choosing the Best One Your LLM Is Not an Agent. Your Framework Is Not Enough. You Need a Harness. From Creation to Consumption: How Antigravity 2.0 and Gemini Spark Are Defining the Agentic Era 10 Mistakes I Wish I Knew Before Taking the CKA Exam AI That Actually Does Stuff: Autonomous Agents Explained Exploring AI workflow Orchestration: Comparing Weft, Python & Alternative Pipeline Approaches El Poder del Aprendizaje Federado: Cuando los Algoritmos Distribuidos Entrenan a la IA Email Marketing Automation in 2026: 5 Tools (and 1 Self-Hosted) Through Their APIs A Replay Runbook For Missed Publishing Windows Why timeout handling matters more than most backend logic How I Make $6,800/Month Selling Niche VS Code Extensions Model Routing Cost Checklist: Hosted APIs, Open Models, Or Self-Hosted Inference? ORA-00207 오류 원인과 해결 방법 완벽 가이드 Deno 2.8 Operator Upgrade Checklist: CI, Lockfiles, Node Compatibility, And Rollback AI-Discovered Vulnerabilities Need A Triage Queue, Not A Panic Channel AI Agent Workboards Need Audit Controls Before They Need More Agents Demystifying DevRel: What It Actually Is (And Why Should You Become One?) Your AI, Your Device, Your Data - Introducing Aide Gemma 4 GenAI Coach - GenAI Concepts Made Easy with an Interactive Playground QuietPulse - Mood Tracker Principal Components in TypeScript (Part 3) The pgAudit Attribution Gap: Why Role-Level Logging Fails GDPR and How to Close It Gemma 4 CAD Orchestrator I built a local Postgres triage co-pilot because HIPAA says I can't paste plans into ChatGPT or Claude Live Holographic Editor In Fractal Time Everbench: A document management system with Local Intelligence Instanton in Fractal Time The Hidden Features of Claude How I Built an AI News Brief with Next.js, Supabase, Vercel, and GPT-4o-mini How We Built a Multi-Agent AI Documentation System (And What We Learned) I got tired of writing post-mortems — so I built RCAi for SREs MIA: A Futuristic AI Desktop Assistant Built with Voice, Gestures, and Controlled Chaos Best Programming Language for Backend Web Development: PHP vs Python PayPal Alternatives for Indian Businesses: Best Payment Gateways for International Card Payments (2026) Gemma 4 Made Me Rethink Local AI: Not Just Text, But Images Too Clean Architecture in .NET Explained (The Dependency Rule) I Compiled Rust to WebAssembly and Made My JavaScript 6 Faster Outlook.com Is the Final Boss of 'Just Send an Email' Conditional Statements and Control Flow in Python Insults & Cutlasses, Local LLM Sword Fighting on Melee Island Production Lab: ECS Fargate + Prometheus + Grafana + Loki + Alloy + Node Exporter How 12 AI agent frameworks handle human approval (most badly) The Four-Index Reality: Why AI Search Isn't One Thing I Scanned 1 Million AI Services. Here's What Worries Me More Than the Vulnerabilities Managing multiple docker hub accounts using docker-use System Design Interview: Decentralized Web Crawler Metric Cardinality: High or Low? 4 Steps to Making the Right Choice 로컬 LLM 셋업 가이드 (v23) GEO vs SEO in 2026 — What Google's May Guidance Changed Cursor Review 2026 — Honest 'Not For Me' Take From a VSCode User Hello from rikuq — a practitioner blog for solo AI SaaS founders Why DevOps Engineers Need Practical Tutorials, Not Just Theory AI Agents in CI/CD: Give Them Context, Not Production Authority Now I See Why Translators Are Panicking Over AI—Should Coders Panic Too? Why I Track HRV Every Morning (And How It Actually Changes My Day) Diffusion Language Models: How NVIDIA's Nemotron-Labs DLM Is Killing Token-by-Token Generation Chatbots GPT pour le support client : ce que les équipes françaises ont réellement besoin de savoir I Hit the 1,232-Byte Wall So You Don't Have To Google Just Rebuilt the Search Box (Again) — But This Time It's Different Aether: A local Android assistant built with Gemma 4 BoxAgnts Introduction (1) — Out of the Box mkdev: trusted HTTPS for localhost, mapped by name Just one question, one answer. Why Java Still Rules the Programming World in 2026 Four Architectures for Letting Claude Edit Elementor (and Why We Shipped Clone-and-Mutate) yard-yaml 0.1.1: safer UTF-8 handling for YAML documentation I Built a Mac App That Keeps Your Clipboard in Sync Across All Your Android Devices Stop Using UUIDs: Why B2B SaaS Needs ULIDs in Laravel 🐘 I'm a non-technical founder who built a Slack approval tool. Here's what actually broke first. Open-Sourcing Our Game AI Stack — SDKs, Templates, and CLI Tools for NPC Dialogue I Built an AI System That Makes 1,000 Decisions a Day. Here's Where I Drew the Line. Lets Encrypt DNS Challenge with Traefik and AWS Route 53 Building an agent-ready website: how to make your site readable for ChatGPT, Perplexity and autonomous agents A productivity tool with GitHub as your cloud database How We Built Dynamic NPC Dialogue with LLMs — Lessons from Early Access cmux: The Native macOS Terminal Built for Running AI Coding Agents in Parallel Deep Atlantic Storage: Rewriting in Rust How I Built a Bulk Image Optimizer with $0 Server Costs Using Vanilla JS and Canvas API Humans and Machines read differently, I think I have a fix? Claude Code Deleted 92 Images Without Asking. This Happens More Than You Think. Method Calling Stack in Java I Built Schedule Sensei & Pushed It to GitHub – Here's What's Inside (And I Need Your Help 👀) OIC: From a Working Toast Watcher to a General "Watch It for Me" Agent Memory is two-thirds of what an AI chip costs to build The XState persistence problem is five years old. Here is what we built to finally solve it. i added MCP support to my SaaS in an afternoon. here's the whole thing. Framework: Link Building ☁️ Importing existing S3 buckets into Terraform state made easy with terraform import existing s3 bucket I Built a Token System on Solana (Without Any Backend Code) 터미널 AI 에이전트 구축 (v21) I Built an AI 3D Model Generator — Here's How I Handle Meshes in the Browser 🛡️ PromptGuard: I Built a Local AI Privacy Firewall That Sanitizes Your Prompts Before They Leave Your Machine PostgreSQL WAL Bloat: Why Automatic Management Is Often Insufficient? Seven PRs Before Lunch: Parallel Claude Code Tabs Plus Audit-Before-Bump Deployment using all three Kubernetes probes Qwen 3.6 Has Four Tiers. Here's How to Route Without Burning Cash. RAG 시스템 실전 구축 (v21)
From HTTPS to UCP: Shopping Is About to Stop Being Your Problem
Ruvimbo Deli · 2026-05-25 · via DEV Community

The narrative of digital transformation in retail has been remarkably consistent. First, get online. Then build an app. Then optimize checkout. Add loyalty points, push notifications, maybe a chatbot.

For years, this was the right strategy. It moved retail from physical-only to omnichannel, giving customers access, convenience, and choice.

But something fundamental shifted at Google I/O 2026.

The conversation is no longer about getting customers to your storefront—digital or physical. The question retailers must now answer is: When your customer's agent comes shopping, will your business be ready?

This is the move from HTTP/HTTPS (where humans browse sites) to the Universal Commerce Protocol (UCP) (where agents act across platforms). It redefines not just the technology of retail, but the entire relationship between businesses, customers, and shopping itself.


The Technology: Where HTTPS Met Its Match

To understand what's happening, it helps to think about HTTP's role in web history. HTTP standardized how browsers and servers communicate, unlocking the web as we know it. Similarly, UCP is designed to standardize how agents—autonomous systems acting on behalf of customers—can understand and transact across different retailers, payment systems, inventory platforms, and fulfillment networks.

But UCP isn't just a protocol upgrade. It's accompanied by three critical technical announcements that fundamentally change what's possible:

1. Gemini Spark and Proactive Agent Commerce

Spark is a browser-based agent that doesn't wait for you to ask. It reads your calendar, understands your commitments, and anticipates your needs. This is where shopping transforms from a task you remember into a background process that simply happens.

For someone like me—juggling data science work, team leadership, community projects, and a dozen other commitments—Spark represents a genuine return of time. When I see on my calendar that I'm on "snack duty" for a weekend game, the agent can:

  • Understand the context (when, where, how many people)
  • Recall my constraints (dietary preferences, budget ranges, previous choices)
  • Proactively set up an Instacart order
  • Remember to exclude nuts because someone in the group has allergies
  • Present the order for approval before checkout

This isn't a recommendation. This is delegation.

2. Agent Payments Protocol (AP2) and Trust Through Guardrails

With great delegation comes the need for security. AP2 allows customers to set strict, tamper-proof guardrails that agents must follow:

  • Spending caps per transaction
  • Brand whitelists and blacklists
  • Category restrictions
  • Approval thresholds

Every transaction creates a cryptographically secure digital paper trail. The customer maintains full accountability and can revoke agent access instantly.

This solves what traditional fintech couldn't: How do you let an autonomous system handle money on your behalf while maintaining control?

3. Gemini Nano and Offline-First Shopping

The final piece is perhaps the most underrated: Gemini Nano 4, an on-device model powerful enough to run complex reasoning entirely locally—in airplane mode, with no internet connection.

This matters because shopping doesn't always happen online. Sometimes you're in a mall with spotty WiFi, trying to make style decisions for formal wear, and you need product information, sizing guides, or virtual try-on capabilities without relying on the network.

With Nano, a custom retail app can:

  • Store product catalogues locally
  • Run visual recognition for style matching
  • Provide detailed product comparisons
  • Offer sizing guidance
  • Create virtual try-ons

All without a data connection. The technology disappears, and you get back to what actually matters: the decision.


Why This Matters Personally (And Why It's Bigger Than Me)

For years, I've approached shopping the same way I approach most of life: pragmatically. I don't have time for multiple apps, price comparisons, or decision paralysis. I have outcomes I need.

The problem is that retail was built assuming everyone wants to browse, compare, and feel in control of the process. But that's not universal. People shop differently based on their constraints.

For the time-poor (me): The best shopping experience isn't browsing. It's delegation. Spark handles the thinking; I handle the approval.

For the efficiency-focused: It's not about the most beautiful app. It's about an agent that understands your priorities—best deals, minimal time, trusted brands—and orchestrates the entire journey. Tools like Antigravity 2.0, Google's agent-first development platform, allow retailers to build custom agents that act as mission control. These agents can map optimal routes across stores, identify real-time deals, research product quality, and even execute purchases under strict conditions using AP2. For someone who refuses to waste time but won't sacrifice value, this is transformative.

For the expert shoppers (like my cousin with formal wear): It's about augmentation. Having an on-device assistant that knows her style preferences, past purchases, and body measurements while she's physically shopping—even offline—amplifies her decision-making without replacing it.

The retail insight here is stark: Customers aren't losing interest in shopping. They're losing patience for friction. They're not abandoning carts because the prices are too high; they're abandoning because the decision-making burden is too heavy, the process too fragmented, the experience too disconnected from how they actually live.


The Business Case: Capturing the Opportunity Cost

Most retailers think about lost sales in terms of price, stock, marketing budget, or abandoned carts.

But there's another category that deserves attention: sales lost because shopping didn't fit into the customer's life.

A customer doesn't buy because they're busy. Another delays because they're overwhelmed by options. Another avoids the store because the trip feels exhausting. Another abandons the cart because comparing offers is too much work.

This is opportunity cost—and it's enormous.

Agentic retail has the potential to recover this by helping customers shop around their actual constraints, not just their preferences.

The business question shifts from: "What does this customer want?"

To: "What is making this purchase harder than it needs to be?"


Why Retailers Need to Get Agent-Ready Now

Here's where the strategic opportunity lies for retailers, especially those looking to compete globally.

UCP is open-source and protocol-based, which means it's not controlled by any single platform. But adoption requires retailers to think beyond their website or app. The backend systems—product data, inventory accuracy, pricing consistency, return policies, loyalty rules, payment flows—must be reliable enough for agents to understand and trust.

A traditional digital transformation question: "How do we get customers to our website or app?"

An agentic commerce question: "Are our systems clean, accurate, and trustworthy enough for an autonomous agent to recommend us?"

This sounds subtle, but it's profound. A beautiful website helps humans decide. Clean, consistent, machine-readable data helps agents recommend you.

The Universal Cart, which works across Search, YouTube, and Gmail, is an example of this in action. It can even apply intelligent reasoning—flagging when a processor selected in one cart isn't compatible with a motherboard in another, catching errors before purchase.

For retailers, this means:

  1. Invest in data infrastructure. Product catalogues, stock positions, pricing feeds, and policy documentation must be accurate and machine-readable.
  2. Think about agent-first UX. Not every customer needs a beautiful storefront anymore; some need to be easily found and trusted by an agent.
  3. Build for transparency. Agents will explain why they recommended your product over a competitor's. Can your systems support that narrative?

The Intelligence Question—And Why It Matters for Trust

Here's where this gets complex.

Traditional retail systems mostly see what you bought. An agentic system understands what you intended to buy, what you compared, what you rejected, what mattered most, and what constraint shaped the final decision.

That intelligence is valuable. It could improve demand planning, reduce waste, enable better promotions, and help retailers understand market behavior with real nuance.

But it also raises uncomfortable questions:

  • Who owns intent data? If an agent learns that you're willing to spend more on sustainable products, or that you're price-sensitive, who controls that insight?
  • What does real consent look like? A checkbox saying "I agree to share shopping data" isn't consent; it's legal cover.
  • Can you see what your agent shared? Transparency has to flow both ways.
  • Can you revoke access? Consent must be revocable, not permanent.
  • Why was this recommended over that? The agent's reasoning should be explainable.

This isn't just a technical problem to solve; it's a governance conversation.

The retailers who build agentic commerce responsibly—with transparent data handling, genuine consent, and customer control—will win trust. Those who treat it as an opportunity to extract data quietly in the background will eventually face backlash.

The strongest competitive advantage in agentic retail won't come from having the best algorithms. It will come from being the brand customers trust their agents with.


What Comes Next

The shift from HTTP to UCP represents more than a technology transition. It's a redefinition of what retail is for.

Shopping in the age of agents isn't about having more options. It's about removing the friction that keeps people from getting what they need.

For me, that means delegating the thinking.
For others, it means efficiency.
For some, it means confidence in a decision.

The retailer—and the technology platform—that understands this will thrive.

But understanding it means asking better questions:

  • What's making this purchase harder than it needs to be?
  • Are our systems ready for agents to trust us?
  • Are we building this responsibly?

These are the questions that will separate retail leaders from everyone else in the agentic era.

The question is no longer: "Does your retail business have an app?"

The question is: When your customer's agent comes shopping, will your business be ready?

And more importantly: Will your customer trust you with their agent?

This is a submission for the Google I/O Writing Challenge