Why to Use Design First and Server Side Swift if Everything Works Anyway

on YouTube ↗37m

" summary

Argues that using a Swift backend plus a design‑first OpenAPI workflow actually prevents the small, costly integration bugs that kill deadlines — examples: locale-dependent floats, inconsistent JSON date encodings, and enum casing that turned “suit” into “clothes” arguments. Shows using Vapor and code generators to produce shared Swift models and client+server stubs so the app and API use the same types and tests, speeding prototyping and avoiding hand‑written glue. Presents concrete numbers: 100k requests/sec with 7–8 MB memory and recommends OpenAPI/Swagger codegen.

AI-written summary · about

" chapters (8)

1. 0:00Introduction
2. 3:08Human factor issues
3. 11:37Design-first with Swift
4. 17:06Backend interaction errors
5. 22:10Team communication
6. 25:56Code generation tools
7. 30:43Server-side Swift benefits
8. 35:11When to use Swift

" related talks

• 34mServer Side SwiftJens Ravens · App Builders Switzerland 2017
• 41mGetting started with Server-Side Swift and VaporTim Condon · Swift Heroes 2018
• 36mFull stack development with Swift and VaporTim Condon · iOS Conf SG 2020
• 27mFull Stack Development with Swift and VaporTim Condon · #Pragma Conference 2019
• 30mAPI Code First vs Design FirstPhil Sturgeon · apidays New York 2020
• 20mUnlocking API Potential: Design First ApproachPatrick Brosse · Apidays Helsinki & North 2023
• 31mGetting Started With Server Side SwiftLeo Dion · 360|iDev 2021
• 19mServer-side Swift Using VaporTanner Nelson · try! Swift NYC 2017