Effective collaboration with backend engineers
summary
Defines concrete practices: write RFCs/proposals that include API-change sections and alternatives, publish OpenAPI specs to generate client and server code, and adopt a backend-for-frontend layer so UIs get ready-to-render payloads and URIs for navigation. Use feature flags plus version duplication to avoid long-lived compatibility code, run company-wide nightly builds and testing parties, share CI and an internal CLI "Droid" and small web recipes to let backend and client engineers pair and fix issues together.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:04Mobile dev evolution
- 3:58Cross-platform teams
- 5:20T-shaped engineers
- 7:45Feature dev with RFCs
- 10:33API design discussions
- 12:18API contracts & BFF
- 14:24API design example
- 16:32Backend change collaboration
- 18:40Cross-stack engineers
- 20:43AI for collaboration
- 22:08Testing parties
- 23:12Feature rollout strategies
- 25:58Version duplication
- 27:04Internal testing
- 29:13App installation
- 30:40Breaking silos
- 31:02Closing & Q&A
related talks
46mHello from the other side: effective collaboration with backend engineers
33mCollaboration & Productivity-Missing Links in API Development
26mBalancing between internal and external developer experience
19mVersioning strategy for a complex internal API
37mBuilding Developer-Centric APIs in a Multi-Product SaaS Org
49mBuilding Software Better: API Lifecycle Management for Developers
35mBuilding Your API for Longevity
22mMake your APIs Developer-friendly