4 ms·
At the end of the day the web is interpreted, and developed on desktop computers. This result in two problems when doing web first on mobile. 1: bloated frame
by digi_owl 10y ago
At the end of the day the web is interpreted, and developed on desktop computers.
This result in two problems when doing web first on mobile.
1: bloated frameworks. Both in term of CPU usage, memory consumption, and the number of round trips needed to show something like a simple list of links.
2: "mobile" sites that may look right at first glance but that invariably show themselves to have elements that hint at having been designed on a large screen computer with a mouse attached.
But what sank FFOS was its availability. Its concept fitted perfectly into the SV mindset and the ongoing "maker" thinking.
But they were launched and sold to the "third" world as spruced up featurephones.
- slacka 10y ago> bloated frameworks. Both in term of CPU usage, memory consumption, and the number of round trips needed to show something like a simple list of links. You combine this with the fact they were targeting the low-end, entry level marketspace. and you have a recipe for failure. At a time when even low-end Android phones had finally overcome their sluggishness, the first Firefox OS device that I tried felt slow and unresponsive.