
The Web in the Mobile-First Era
How the web evolved from 1989 to 2020 and where it's heading next

How the web evolved from 1989 to 2020 and where it's heading next
How the web evolved from 1989 to 2020 and where it's heading next
From statistics to web developer prospects
Context: ecosystems and mobile first
Web/mobile timeline: 1989 → 2020
Web developer prospects and frontend trends
Fintech practice: web, PWA, cross-platform
The digital ecosystem development org
What our digital ecosystem org runs
Public web of the flagship sites
Mobile banking app
Data platform + acquisition automation
Special projects + shared infrastructure
Internet and mobile user statistics
4.57B — People online — Digital 2020, We Are Social
5.16B — Unique mobile users — about two thirds of the population
52% — Web traffic from mobile — desktop 45.3%, tablet 2.7%
Mobile-first design + performance
Phone-first design, or it fails
Performance budget > visuals
Touch first + 3G/offline resilience
Bundle size — the main frontend KPI
30+ years of web and mobile evolution
WWW + JS
1989 — WWW concept
1990–1991 — HTTP/URI/HTML
1993–1994 — Mosaic, Netscape, W3C
1995–1998 — JS, browser wars, CSS2/PHP
AJAX, jQuery, iPhone, Android
2000 — Windows Mobile
2004 — Web 2.0 and AJAX Gmail
2005–2006 — Rails, Maps, jQuery
2007–2009 — iPhone, Android, Chrome
SPA, hybrid, React Native, PWA
2010 — AngularJS, Backbone, SPAs
2011 — Apache Cordova, Windows Phone
2013 — React, micro-frontends emerging
2015–2019 — RN, ES2015, PWA, Flutter
Mature web + mobile + cross-platform
React, Vue, Angular — SPA standards
Next.js, Nuxt, SvelteKit — SSR meta-frameworks
PWA/RN/Flutter — near-native
WebAssembly, edge, serverless go mainstream
What's in demand right now
What the web wins over native development
A browser exists on every platform
No app stores and no review
Updates reach users instantly
A lower barrier to entry than native
What we do at a large fintech
By full functionality and by complexity
PWA — web plus a manifest
Hybrid — native shell around a WebView
Cross-platform — write once, run anywhere
Native — write twice, everything available
Then follow whatever the idea proves
Testing an idea — web and PWA
Need the stores — a native shell
The idea took off — native development
Avoid writing twice — React Native or Flutter
The pace of change is very high
Starting on the web is simple and fun
One stack, almost every platform
More constraints than native
start on the web, then follow the evidence
Mobile development is commoditizing
AI first — Facebook and Google, 2016
How does a web developer get there?
TensorFlow.js — in the browser and in Node.js
Where to go next
Mobile-first, standards, PWA, frontend
Digital 2020 + web.dev
MDN — the web standards reference
State of JS/CSS — annual surveys
Frontend channels and podcasts
polomodov.tech
All slides and links — in the Telegram channel
Alexander Polomodov, Technical Director & Fellow, T-Technologies
@book_cube