Modular Quasar:Reducing Cognitive Overhead In Large Applications
summary
Shows a concrete architecture: page → view → components where views own API requests and global state while leaf components receive props and emit events, never reading the store. Uses generators (Hydrogen) to enforce naming and folders and even scaffold tests, and composables like useFetchResources composable and extracted helpers (example: useTodosFetcher) to centralize fetching, filtering and error handling. Demonstrates a working to‑do list with QList/QItem/QCheckbox, event-up/props-down delete flow, and backend patterns using Laravel Orion + Pinia ORM and resource composables (useCreateResource/useUpdateResource).
AI-written summary · about
chapters (14)
- 0:00Modular Quasar architecture
- 2:49Generators for folder structure
- 5:59Folders for components
- 7:02Composables for backend
- 11:16Logic out of views
- 14:29Decoupling components
- 22:57Live coding demo
- 23:19Q&A
- 25:25Quasar vs other frameworks
- 27:53TypeScript in Quasar
- 29:19Useful Quasar components
- 31:04Laravel and Quasar tips
- 33:32Quasar UI standalone
- 35:18Closing remarks
related talks
23mQuasar: come for the UI library, stay for the integrations
51mBuilding Amazing Single Page Applications the Right Way
34mModular Flutter App Architecture Answering the What, When and How
32m6 App building patterns your Seniors didn't want to know
25mHow to stay sane while managing complex state, in Vue js
29mA New Paradigm: How Do I Optimally Break my UI Into Queries?
21mModern State Management with Vue 3
09mCommunicating Between Components