2 ms·

It's weird that they frame the growth of web frameworks as a reaction to feature-rich mobile apps. > From the get go, mobile apps on iOS and Android were full

It's weird that they frame the growth of web frameworks as a reaction to feature-rich mobile apps. > From the get go, mobile apps on iOS and Android were full applications written in Serious Languages™ like Objective C and Java...This [deeper integration] resulted a much better UX... > Doing all of that with JavaScript was seen as ludicrous at first. But as time went on, applications started to get more ambitious. Social networks added chat and DMs and other real-time features, Gmail and Google Docs... Desktop-similar Google Docs and Gmail predate smart phones. Meebo was running a desktop-like chat app in 2005. At the time, it felt ludicrous. Rich client-side web frameworks were already pretty far along by the time the App Store came out in 2008.

deaddodo 5y ago
On top of that, most of the techniques that mobile apps leverage today were developed for web apps of old. REST + JSON was built as a lightweight data transmission option for Ajax/XmlHttpRequest versus transmitting HTML over the line. Component-based/Reactive UX came about because of the unknowability and variability over browser windows. Asynchronous development paradigms came to prominence due to the high latency of frontend<->backend apps combined with fault-intolerance assumptions. Etc.