Lessons Learned from Crafting a Thriving vue.js SAAS App
summary
A large Vue 3 SaaS messaging app runs on TypeScript + GraphQL with a six‑engineer team and around 800–1,000 components; real time is handled by composables that manage websockets, visibility events and pagination without UI coupling. Builds use the git commit hash for deterministic asset names to avoid version skew, the API sends a build header to force soft or hard reloads, testing relies on playwright + MSW and the app reports average sessions of 74 days.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker intro
- 7:59Tech stack and architecture choices
- 16:54Component organization and design system
- 27:49State management strategies
- 31:04Performance optimization lessons
- 40:51Testing approach and trade-offs
- 43:01Long-running sessions and version skew
- 47:14API versioning and compatibility
- 52:16Q&A session
related talks
25mLessons Learned from Crafting a Thriving Vue.js SaaS Behemoth
23mFull Stack Vue in the Era of Serverless Computing
47mReal and Scalable Applications with Nuxt, Vuex and Typescript
39mVue.js deep dive, looking to the future
06mMigrating a Large Legacy App to Vue
46mVueJS for Scalable Applications
21mVue JS Best Practices
44mBreak up a Massive Vue Front End