Learnings from building a CRM app at Google
summary
Internal CRM runs mission-critical production traffic and is built 100% Dart front end, serving live users for three years with 30 engineers, ~500k LOC and 40% code reuse across products. UI uses AngularDart (800 components) and moved business logic into plain Dart services for testable VM code. Network smoothing uses Streamy cache that returns cached value then an updated response. Mobile prototype uses Flutter, achieves about 3× productivity versus native Android and delivers native-feel, 60 fps experiences.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:15What is CRM
- 2:25Googles CRM system
- 3:17Numbers
- 5:00UI
- 5:42Why Dart
- 7:20Launching the app
- 8:46Scaling problems
- 14:48Angular
- 16:13Refresh cycles
- 16:44People on the team
- 17:50Missing something
- 21:25Prototype app
- 24:00Working with Flutter
- 26:09Conclusion
related talks
22mArchitecture First: Foundations for Long Term Success
44mRe-Platforming The Path For Betterment
40mGrowing Pains: Scaling and Re-architecting Apps Under Fire
23mFrom Auto Parts Manufacturer to Productized Cloud Service at a Large Automotive Supplier
58mMobile App Architecture: How to Conquer the Giant!
07mTransforming legacy systems with modern technology demands
48mNo Big Bang Theory: A Decade of Building Our Own Product
40mArchitecture: The LeanCode Guide