Backend for Frontend – The secret of a great mobile project
summary
A mobile team builds a Backend-for-Frontend that translates a legacy XML web API with only six endpoints into a JSON API removing roughly 80% unused fields, implemented in Kotlin using Ktor (alternatively Spring Boot, Go or Scala prototypes). The BFF reduces payload, enables per-app versioning, isolates failures so one bad client won’t take down everyone (self‑DoS case), and prompts the backend to adopt dedicated web and mobile BFFs.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker intro
- 1:09Problems with existing APIs
- 3:38Backend for Frontend concept explained
- 5:51Designing a good BFF API
- 7:17Implementing mobile BFF solution
- 8:42Expanding BFF to web and third parties
- 10:10Benefits of BFF for versioning and failures
- 13:11Technologies for BFF development
- 14:17Why BFF is beneficial for projects
- 16:23Closing and future talks
related talks
54mGiving the Frontend Only What It Needs, or Why You Need a BFF
21mEnhance and improve user experience with BFF
27mBackends for frontends with GraphQL
37mDiscussing Backend-For-Frontend
49mBFF (Backend For Frontend)
09mKeep your friends close and your APIs closer
24mMicrofrontends
41mDiscussing Backend For Front-end