Building applications for the next billion users
Submitted by Siddharth Kshetrapal (@sidkp) on Saturday, 3 June 2017
There are 340 million internet users in India, that’s more than the entire population of the US. Sadly, 86% of them are on slow networks. These harsh conditions bring out the best architecture patterns for building performant applications.
That does not mean that the developer experience has to be terrible. Let’s talk about server rendering, loading strategies and progressive enhancement to fulfil the gold standard performance checklist without breaking a sweat.
- Understand importance of performance for users + businesses
- Take-home performance checklist
- Architecture patterns that are friendly for developers + performant by default
- How can they implement these in their applications today
– Part 1: performance
Why should you care about performance?
1.1 Big numbers about the network spread in India (86% on slow networks)
1.2 Some scary stats about impact of performance on user behaviour + businesses
Understand web performance nicely
2.1 How to measure performance
2.2 Metrics that matter
2.2 Network constraints
What can I do to improve my application’s performance
3.1 Performance budget
3.2 Server side rendering (get to meaningful paint fast)
3.5 Lazy loading good-to-have features, analytics et al (second level of code-splitting)
3.6 Mention smaller frameworks (preact, react-lite, svelt, etc.)
We can do even better (advanced)
4.1 2 state architecture pattern
4.3 Think of each interactive component having 2 states (example in slides)
4.4 Use only static state on AMP pages and 2G and get that SEO juice.
Cache + Prefetch
5.1 Further optimisations: preload, h2 push
5.2 Prefetch resources based on the next step in user’s journey (service worker)
Enter React - What is so great about react
6.2 Share-able components (tiny love letter to CSS-in-JS)
6.3 We got a tooling upgrade (Code-splitting, tree shaking, hot module replacement)
– Part 2: productivity
7.1 js fatigue
7.2 Abstractions for productivity
7.3 creact-react-app (what is it great for, but where it fails in the perf checklist from 1.)
7.4 view on react boilerplates
7.5 architecture patterns that are friendly for developers + performant by default
7.6 data fetching on the server (problem + solution)
7.7 introduce my work: reaqt
Sum up take aways for audience
Folks who have built a react application or two. This isn’t very beginner friendly.
webperf fans will love this.
Why should you let me talk about this/Why am I excited about it?
- I spend a lot of time during my day job thinking about (and implementing) architecture patterns for a healthcare startup in India. (It is literally my job to talk about this :D)
- I am a regular speaker at ReactJS Meetup in Bangalore. Have talked about styling, testing, performance, designing and some more
- I make OSS projects for building performant apps easier: cost-of-modules, recreate, reaqt, css-constructor.
- I obsess over interfaces, web performance and developer experience.