In 2015, we promised GraphQL would be “easy to learn and use.” Ten years, and hundreds of billions of daily API calls later, we’ve learned that not all our hopes and promises turned out to be true.
\n", + venue: "GraphQL Stage", + speakers: [ + { + id: 1, + name: "Braxton Bragg", + company: "Meta", + jobtitle: "Product Manager", + avatar: braxtonBraggAvatar, + socialurls: [ + { + service: "linkedin", + url: "https://www.linkedin.com/in/braxtonbragg/", + }, + ], + }, + { + id: 2, + name: "Elena Bukareva", + company: "Meta", + jobtitle: "Engineering Manager", + avatar: elenaBukarevaAvatar, + socialurls: [ + { + service: "linkedin", + url: "https://www.linkedin.com/in/elena-bukareva/", + }, + ], + }, + ], + }, + { + id: 2, + uuid: "teach-yourself-graphql-2026", + title: "Teach yourself GraphQL in 2026: an anti-blueprint", + start: "2026-05-13T14:40:00-04:00", + end: "2026-05-13T15:05:00-04:00", + tags: ["Learning", "Schema Design", "Best Practices"], + description: + "After eleven years as an open source technology, GraphQL has never had a more favorable learning curve. Clearer mental models, better educational materials, and a deeper collective understanding of best practices have transformed the “wild west” of 2015 to a much more manageable landscape today.
\nYou and your team are unique, so rather than a one-size-fits-all blueprint, this talk presents a practical guide to teaching yourself GraphQL in 2026. We’ll examine how beginners typically build their first mental model of GraphQL, the most common misconceptions, and the key design questions they encounter early.
\nSpecial attention will be paid to different modalities: schema-first vs. code-first, schema design principles, common pitfalls when considering enums, the proper use of fragments, and security and performance by default. Attendees will leave with a conceptual roadmap for self-study, a recipe book for context engineering in their agent, and an understanding of the major decision points along the journey ahead.
\n", + venue: "GraphQL Stage", + speakers: [ + { + id: 3, + name: "Jeff Auriemma", + company: "Apollo", + jobtitle: "Senior Engineering Manager", + avatar: jeffAuriemmaAvatar, + socialurls: [ + { + service: "linkedin", + url: "https://www.linkedin.com/in/jeffreyauriemma/", + }, + ], + }, + ], + }, + { + id: 3, + uuid: "graphql-execution-layer-ai-agents", + title: "GraphQL as the Execution Layer for AI Agents", + start: "2026-05-13T15:10:00-04:00", + end: "2026-05-13T15:35:00-04:00", + tags: ["AI Agents", "Federation", "Public Sector"], + description: + "Your next million API consumers won’t be developers. They’ll be AI agents. And they don’t read documentation, parse hypermedia links, or guess which of your 200 REST endpoints returns the data they need.
\nThis talk examines what happens when autonomous AI agents become the primary consumers of your API layer. Drawing on real data from Singapore’s public government APIs, I’ll show how REST responses waste 30–60% of an agent’s token budget on structural overhead, and how a typed, self-describing schema changes the equation entirely.
\nWe’ll walk through the three properties that make an API truly agent-native: discoverability, precision, and composability. We’ll look at what it would take to unify API estates like Singapore’s 3,000+ government APIs across 75+ agencies into a single, self-describing surface. A pattern Gartner expects 30% of enterprises to adopt by 2027.
\nYou’ll leave with a framework for what makes an API truly agent-native, why GraphQL’s type system and federation model get you there, and how to start without a rewrite.
\n", + venue: "GraphQL Stage", + speakers: [ + { + id: 4, + name: "Pascal Senn", + company: "ChilliCream", + jobtitle: "Founder", + avatar: pascalSennAvatar, + socialurls: [ + { + service: "linkedin", + url: "https://www.linkedin.com/in/pascal-senn-90899a15a", + }, + { service: "github", url: "https://github.com/PascalSenn" }, + { service: "website", url: "https://chillicream.com" }, + ], + }, + ], + }, + { + id: 4, + uuid: "closing-the-loop-coding-agents", + title: + "Closing the Loop: How GraphQL Gives Coding Agents Eyes on What Actually Matters", + start: "2026-05-13T15:40:00-04:00", + end: "2026-05-13T16:05:00-04:00", + tags: ["AI Agents", "Schema Evolution", "Observability"], + description: + "Coding agents are reshaping how we build software. Implementing features, refactoring systems, and shipping changes at a pace unthinkable 6 months ago. But to be successful with agents you need the right feedback loop. One that guides your agent to success, not into the spiral of death.
\nAsk Claude to add a review system to your product API. Without knowing what’s in use, it might reshape your types, move fields, and break your deployed clients because it is missing a crucial feedback loop of what’s in use in your clients.
\nGraphQL changes this. Every client operation explicitly declares the exact fields and types it needs. That gives you something rare: field-level usage data across your entire consumer base. Not endpoint hits, but actual demand, broken down to the individual field.
\nWhen coding agents can access this data, they stop guessing. Evolve your schema grounded in reality, not assumptions.
\nThis talk shows how GraphQL’s inherent usage visibility and the rise of coding agents create a feedback loop that didn’t exist before. And why it matters for anyone building APIs that need to evolve fast.
\n", + venue: "GraphQL Stage", + speakers: [ + { + id: 5, + name: "Michael Staib", + company: "ChilliCream", + jobtitle: "Founder", + avatar: michaelStaibAvatar, + socialurls: [ + { + service: "linkedin", + url: "https://www.linkedin.com/in/michael-staib-31519571/", + }, + { service: "github", url: "https://github.com/michaelstaib" }, + { service: "website", url: "https://chillicream.com" }, + ], + }, + ], + }, + { + id: 5, + uuid: "tbd-slot-1630", + title: "TBD", + start: "2026-05-13T16:30:00-04:00", + end: "2026-05-13T16:55:00-04:00", + tags: ["GraphQL"], + description: "", + venue: "GraphQL Stage", + speakers: [], + }, + { + id: 6, + uuid: "server-assisted-accessibility-graphql-ci", + title: + "Server Assisted Accessibility (Part 2): Enforcing Consistent Semantics via GraphQL + CI", + start: "2026-05-13T17:00:00-04:00", + end: "2026-05-13T17:25:00-04:00", + tags: ["Accessibility", "Schema Design", "CI/CD"], + description: + "In my apidays Paris session last year, I introduced a “shift left” pattern for accessibility: attach accessibility metadata to GraphQL fields using lightweight directives, expose it through code generation, and let Android (Jetpack Compose), iOS (SwiftUI), and web clients map it into native accessibility semantics for consistent defaults.
\nThis follow-up, Part 2, focuses on the next problem teams hit in production: keeping that metadata accurate as the schema changes. We’ll walk through a practical, low-friction approach adding CI-friendly validation that catches common contract regressions before changes ship: missing required metadata, invalid values, and template drift.
\nThis approach standardizes the repeatable, high-leverage semantics (labels, roles, states, templated summaries) so clients can focus on the platform-specific work that truly belongs in the UI (complex interactions, focus order, and behavior). You’ll leave with schema examples you can adapt, a realistic enforcement blueprint that fits into pull requests and CI, and rollout patterns for introducing rules gradually without breaking existing clients.
\n", + venue: "GraphQL Stage", + speakers: [ + { + id: 7, + name: "Vanessa Johnson", + company: "The New York Times", + jobtitle: "Android Engineer", + avatar: vanessaJohnsonAvatar, + socialurls: [ + { + service: "linkedin", + url: "https://www.linkedin.com/in/vanessa-johnson999/", + }, + ], + }, + ], + }, +] diff --git a/src/app/day/2026/nyc/speakers/braxton-bragg.jpg b/src/app/day/2026/nyc/speakers/braxton-bragg.jpg new file mode 100644 index 0000000000..cff3551511 Binary files /dev/null and b/src/app/day/2026/nyc/speakers/braxton-bragg.jpg differ diff --git a/src/app/day/2026/nyc/speakers/elena-bukareva.jpg b/src/app/day/2026/nyc/speakers/elena-bukareva.jpg new file mode 100644 index 0000000000..d27db7266b Binary files /dev/null and b/src/app/day/2026/nyc/speakers/elena-bukareva.jpg differ diff --git a/src/app/day/2026/nyc/speakers/jeff-auriemma.jpg b/src/app/day/2026/nyc/speakers/jeff-auriemma.jpg new file mode 100644 index 0000000000..4bf99a939e Binary files /dev/null and b/src/app/day/2026/nyc/speakers/jeff-auriemma.jpg differ diff --git a/src/app/day/2026/nyc/speakers/michael-staib.webp b/src/app/day/2026/nyc/speakers/michael-staib.webp new file mode 100644 index 0000000000..34ccb4ee9c Binary files /dev/null and b/src/app/day/2026/nyc/speakers/michael-staib.webp differ diff --git a/src/app/day/2026/nyc/speakers/pascal-senn.webp b/src/app/day/2026/nyc/speakers/pascal-senn.webp new file mode 100644 index 0000000000..05c0399d37 Binary files /dev/null and b/src/app/day/2026/nyc/speakers/pascal-senn.webp differ diff --git a/src/app/day/2026/nyc/speakers/vanessa-johnson.webp b/src/app/day/2026/nyc/speakers/vanessa-johnson.webp new file mode 100644 index 0000000000..1002421565 Binary files /dev/null and b/src/app/day/2026/nyc/speakers/vanessa-johnson.webp differ diff --git a/src/app/day/2026/singapore/page.tsx b/src/app/day/2026/singapore/page.tsx index e1dd72d221..b3a2de4ee9 100644 --- a/src/app/day/2026/singapore/page.tsx +++ b/src/app/day/2026/singapore/page.tsx @@ -9,7 +9,13 @@ import { MarqueeRows } from "@/app/conf/2026/components/marquee-rows" import { PastSpeakersSection } from "../components/past-speakers" import { NavbarPlaceholder } from "../components/navbar" import { GallerySection } from "../../gallery-section" -import { ScheduleSection } from "./schedule-section" +import { EventScheduleSection } from "../components/event-schedule-section" +import { + singaporeSessions, + SINGAPORE_TIMEZONE, + SINGAPORE_TIMEZONE_LABEL, + tagColors, +} from "./schedule-data" const SCHEDULE_ANCHOR = "#schedule" @@ -61,7 +67,12 @@ export default function SingaporePage() {Schedule
-- All times in Singapore Time (SGT, UTC+8) -
--
-
-
...
` blocks) into the - * inner HTML of each paragraph so we can render them as real React `` - * siblings — needed so we can splice the speaker card in alongside the last - * couple of paragraphs at xl+. - */ -function parseParagraphs(html: string): string[] { - const formatted = formatDescription(html) - const matches = formatted.match(/
[\s\S]*?<\/p>/g) - if (!matches) return [formatted] - return matches.map(p => p.replace(/^
/, "").replace(/<\/p>$/, ""))
-}
-
-function SessionHeader({
- session,
- className,
-}: {
- session: SingaporeSession
- className?: string
-}) {
- const start = new Date(session.start)
- const end = new Date(session.end)
-
- return (
- {session.title}
-
{speaker.name}
- {subtitle && ( -- {subtitle} -
- )} -- ) -} diff --git a/src/app/day/layout.tsx b/src/app/day/layout.tsx index 84934d035f..db98b20709 100644 --- a/src/app/day/layout.tsx +++ b/src/app/day/layout.tsx @@ -50,6 +50,10 @@ export default function DayLayout({ children: "Singapore Schedule", href: "/day/2026/singapore#schedule", }, + { + children: "NYC Schedule", + href: "/day/2026/nyc#schedule", + }, { children: "Code of Conduct", href: "https://www.apidays.global/legal/code-of-conduct#:~:text=Individuals%20who%20participate%20(or%20plan,during%20or%20after%20the%20event.",