6 App building patterns your Seniors didn't want to know
summary
Large B2B app experience (about 1,400 components and 600 demos) shows that rolling custom UI costs weeks and hidden maintenance; prefer existing ecosystems like Vuetify, Quasar, Admin UI and only fork when unavoidable. For Vue data flow use a hierarchy: props → modules → provide/inject → Vuex, avoiding global magic. Protect frontend from backend drift with classes, mappers, repositories and snapshot checks. Test components cheaply with Storybook/Viewbook, use Jest for unit logic and Cypress/Selenium for high-level e2e. Use CSS Modules or BEM to avoid style conflicts.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:52Custom framework
- 7:49Library selection
- 8:31Data handling problems
- 13:35Invalid data handling
- 18:42Component testing
- 24:04Style issues
- 27:26Summary
- 31:22Q&A
related talks
29mAdvanced Vue.js features and patterns in the enterprise
48mPatterns for Large Scale Vue JS Applications
37mPatterns for Large Scale Vue.js Applications
19mPatterns for Large Scale Vue.js Applications
24mPatterns for Large Scale Vue.js Applications
25mLessons Learned from Crafting a Thriving Vue.js SaaS Behemoth
51mBuilding Amazing Single Page Applications the Right Way
36mAngular, React, Vue and co: Harmoniously united by web components and micro apps?
