This transcript features a conversation between two founders deeply invested in developer experience (DX) and exploring the evolving landscape of "agent experience" (AX), particularly in the context of email services. They discuss the shift from human-centric application development to a future where agents (AI entities) are the primary actors, requiring a fundamental rethink of product design and accessibility.
The conversation begins with the observation that much of the existing infrastructure, databases, and communication tools are built for and used by humans. However, the increasing prevalence of AI agents signals a paradigm shift, demanding that developers create experiences tailored to agent interaction. The discussion emphasizes that developers need to build not only services for humans, but also for agents.
The initial reaction from developers is that it is very difficult because not only do they need to build services for humans, they now need to build experiences for agents. The founders note that AX is not about replacing DX but augmenting it. Just like DX is the sum of all the little details, AX is also the sum of those same details. One of the biggest examples the founders mention in this discussion is the ability to onboard onto the tool to enable the sending of email. Before an agent can begin to send email, it has to onboard onto the platform or system.
The discussion shifts to the specific challenges and opportunities within the email domain. It questions whether agents will have their own email addresses, processing emails on behalf of humans, or require different instructions for programmatic service utilization. They use the analogy of autonomous cars navigating existing road infrastructure, suggesting that agents will initially leverage existing APIs, SDKs, and protocols rather than demanding a complete overhaul.
The speakers delve into the nuances of email formats, highlighting the unexpected value of plain text over HTML for agent processing. Plain text email has more useful tokens, is easier to parse, and costs less because it is a less complex format. Also they discuss the evolution of API keys and permissioning in the context of agents, pondering whether to treat them as individual users or service accounts.
The conversation highlights the need to send the right message to the right person at the right time. They touch on the role of AI-powered SDR tools, noting that simple customization based on LinkedIn messages is insufficient. Rendering challenges across different email clients are also acknowledged, emphasizing the importance of consistent display.
The discussion moves to the realm of prosumer applications and the growing accessibility of AI-driven content creation. The speaker notes that LLMs are able to perform a variety of tasks and it is important to think about it more than just generating code. Using code is just the aha moment and now there is a new call to action that developers can utilize. This type of thing is important because it enables the ability to customize what is happening in any given setting. The founders discussed how you can start with an idea for an email and in second, you can have the email template.
They explore potential use cases for empowering both consumers and developers to create email-integrated experiences, referencing the trend of "text-to-app" tools and their impact on redefining what a developer is. The founder mentioned they built this tool called new email that really helps like to go from zero from like an idea to an email template in seconds. This can enable not only developers that needed how to code, but marketers, designers, product managers, etc.
They then get into a discussion surrounding React email as an open source project, and their goal on modernizing the way emails are built. It's all about integrating TypeScript, React, and Teyawen into this industry to help it go forward and continue to innovate. With LLMs, this can shorten the creative loop for those non-technical users and enable them to build better things.
As a designer at Uber, they mentioned that they've built all of the prototypes using cursor or V0 or whatever the tools are, and they don't even open Figma anymore. All they need to do is focus on the copy and thinking about the angle. In general, they emphasize that it shortens the creative loop because it enables those who are the most creative to focus on creative aspects and do it faster.
The discussion explores the nature of generative experiences, questioning whether they qualify as agentic workflows. They define an agent as a set of tools executing to accomplish a specific task, potentially involving multiple steps.
Finally, they explore MCP (Meta Chat Protocol) as an emerging standard for AI agent communication. They discuss the potential of MCP to streamline interactions with various APIs, enabling agents to access and manipulate data across different platforms.
The future they envision is one where AI agents conduct the majority of online actions, necessitating a shift in product design to prioritize agent accessibility, rapid onboarding, and secure permissioning. Recording agent activities becomes crucial for understanding and mitigating potential issues. The conversation underscores the need for developers to adapt their toolsets and workflows to embrace this new reality.