I have a Dreamcode: Build Apps, not Backends
summary
Claims that noBackend or Backend as a Service lets front-end developers build full apps in the browser, not just UIs: concrete examples include using Tumblr draft as JSON store to persist favorites, running hoodie to create users from the console and call store.add to save JSON without schema, sending multipart email from client, and installing a Protonet-like box with one command. The promise is working code, fast setup, offline and realtime features, and swap-outable backends.
AI-written summary · about
chapters (6)
- 0:00Start
- 8:44NOBACKEND is a design paradigm for architectures/ frameworks that abstract complex backend operations and technology into a simple to use REST API.
- 9:28Service or an installable package (runs server, DB, everything) -Ideally: One language, one data format Simple, built-in deployment Very quick to get going
- 10:15Very little config and boilerplate, build significant things immediately -Additional perks: offline modes, live sync, reactive views etc. Perfect for rapid prototyping with real data, behaviours and devices
- 16:20We must make [...] what I call "social machines", in which people can collaborate together, but do it in a way that's decentralised, so it's not based on one central hub. -Tim Berners-Lee
- 20:21We need great self-hosted applications, which we can use to manage our emails, personal pictures, documents, private messages with friends, blog posts, etc.
related talks
31mI have a Dreamcode: Build Apps, not Backends
10mBuilding Software for Vibe Coders
40mWeb Apps without Web Servers
47mMeet Your New BFF: Backend to Frontend without the Duct Tape
54mThe Future of the Web-Apps
41mLow-budget JavaScript: composable frontends that are fun and friendly
28mFunctional Web Apps: A New Paradigm For Web Development
30mBuilding Expo apps without code with Draftbit