Dos & Donts when making Technology choices
Download as PPTX, PDF•2 likes•198 views
This document provides dos and don'ts for technology choices, including: - Plan for scale but don't overbuild for the initial needs - Avoid focusing too much on technical aspects over user experience - Spend time on the most important aspects, such as architecture design principles that decouple layers like data, user experience, and identity management
Dos & Donts when making Technology choices
- 1. Dos & Don’ts when making Technology Choices Vinci Rufus @areai51 Sr. Director SapientRazorfish Google Developer Expert
- 2. Other than being a GDE I have no other association with Google. Opinions and perspectives shared in this talk are my own and do not reflect that of any other organization. I don’t get paid by Google. (which sucks) All references to Google’s products or any other companies products are purely Coincidental. Disclaimer
- 4. 1996 2002 2003 2005 2007 Evolution of Smartphones
- 5. Watch this once every 2 months for a healthy dose of motivation https://www.youtube.com/watch?v=9hUIxyE2Ns8&t=126s
- 6. Dos & Don’ts
- 7. Plan for Scale but don’t necessarily go overboard building for one
- 10. Avoid #geekgasm
- 11. Be Paranoid about Speed & Payload
- 12. Stay Performant from Day 0 • Time for Dev Environment setup • Loading time during development • Build Time.
- 13. Spend time on what is more Important
- 15. Data / Content Layer User Experience Layer De-Couple
- 16. RDBMS Aggregation Machine Learning PWA Native Microservices Orchestration Layer API Gateway Be Future Proof Ready Data / Content Middleware User eXperience
- 17. RDBMS Aggregation Machine Learning PWA Native Microservices Orchestration Layer API Gateway De-Couple Identity Management Identity Management
- 18. ‘True’ Mobile first Strategy API Gateway / Graph QL Treat everything as just another device Microservices
- 19. Single Page Experience over SPA Home & Categories Gallery / Product Listing Product Details Checkout Flow My Account A Collection of smaller modular apps. www.bit.ly/why-spe
- 20. Leverage the Cloud • Cloud Native features • Go Serverless, Cloud Functions • QA & staging environments on cloud
- 21. Not Every App needs to be Native But every Responsive site needs to be a PWA
- 22. Reasons we went Native • We want Push Notifications • We wanted a good User Experience ( aka smooth scrolling) • Want it to work Offline • Leverage Device Capabilities.
- 23. PWAs can do All that .. atleast on Android
- 24. WTH is a Progressive Web App “... a new software development methodology for building modern frontend”
- 25. What Constitutes a PWA App Shell Model Instant Loading Offline Support 60 fps Add to Home Screen Push Notifications
- 26. Minimal Viable PWA • App Shell • Add to Home Screen • Full Screen • Offline Support
- 27. Full-on PWA • Push Notifications • Deeply Integrated PWA • Background Sync
- 28. • 3xmore time spent on site • 40%higher re-engagement rate • 70%greater conversion rate via homeScreen • 3xlower data usage Flipkart Lite
- 29. • ~60 MB on Android • ~100 MB on iOS • 0.5 MB as a PWA OLA PWA
- 30. PWA should replace your Responsive Site
- 32. AMP •AMP HTML AMP HTML is basically HTML extended with custom AMP properties •AMP JS The AMP JS library ensures the fast rendering of AMP HTML pages. •AMP Cache The Google AMP Cache can be used to serve cached AMP HTML pages.
- 33. PWA + AMP = PWAMP
- 34. Tech Team you Hire
- 35. Full Stack Developer Angular React JS Preact Vue JS Node Node Java Play Go Lang MongoDB MySQL Neo4J Cassendra Frontend Backend Database
- 36. Polyglot Developer Angular React JS Preact Vue JS Node Node Java Play Go Lang MongoDB MySQL Neo4J Cassendra Frontend Backend Database
- 37. Full stack to Polyglot Switch Early Stage Full Steam Fullstack Polyglot MVP is Shipped
Editor's Notes
- #8: Ask yourself the question what will you do if you get 10x users tomorrow? If your answer is I will need to change my tech stack, or move to a different data center then that’s wrong If your answer is I’ll need need to do anything, my app will just scale? I’ll need about a week or two to scale up.
- #9: Don’t try and be that super hero who goes about fighting all his or her battles all by yourself. The open source community & startup communities around the world are amazing communities Talk to People.. It really really helps
- #10: Angular dumped AtScript and moved to TypeScript
- #11: Air BnB for customer support 100 K users per second.
- #12: Just because most of your users have high end devices and are on 4G, that doesn’t give you an excuse to be sloppy. You’d say its just the first time the user downloads 50 MB. A heavy app is always going to be sluggish, slow to bootup and highly succeptable to be uninstalled when the user runs out of memory.