Scalable Front End Architecture with the Composition API and Composable Functions
summary
Argues that Vue 3 Composition API plus composable functions replace Options API for scalable front ends, showing concrete refactors from setup to reusable useCounter composable, using Pinia for global state and StackBlitz/VS Code in-browser for demos. Builds a small movie playlist app that calls the Open Movie Database API (requires an API key) and shares an addMovieToList function across sibling components; the demo fetches data and the add-to-list functionality works. Also notes OS poll results: Mac 46 Windows 22 Linux 30.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 14:29Demo App
- 15:11Open Movie Database
- 19:44Questions
- 20:40Composition API and Composable Functions
- 22:35When to use composable over component
- 23:49Wills take on the future of API
- 24:26Can you use composable for one component
- 24:55Limitations for mobile devices
- 25:51Composition API
- 26:56Why is the script under the template
- 27:42Composable reactivity
- 28:54QA
- 29:29Conclusion
related talks
21mVue 3 and Composition API
47mVue’s Composition API: Why it’s Important
31mIntroduction to Vue 3's Composition API
28mComposition API: a Quick overVue
19mVue Development Composition API vs Options API
27mIntroduction into the Composition API
46mComposable Vue 3
48mVUE3 & Pinia A Better Pattern for Global State Management