251–260 of 455 posts
Earlier quoted context omitted.
Because different graphics are shown are different resolutions, rather than purely scaling a highly detailed 1024x1024 SVG down to 128x128.
>1024x1024 SVG Vectors don't have pixels.
Earlier quoted context omitted.
Because the customers are the ones who are paying for that inefficiency, not the company. You can bet that those companies' infrastructure is optimized to hell and back.
You know, I'm not currently an Uber customer because their app is too big and I don't have enough spare space on my phone. There were a few times already that I thought about using them, but couldn't install it right at the time.
Things will only get worse. The application paradigm is unsustainable. https://medium.com/@miguelrochefort/the-application-paradigm...
You're entirely right, but "it is difficult to get a man to understand something, when his salary depends on his not understanding it" certainly applies to the entire "tech" industry, and the app factory in particular. I expect this realization will only become widespread when open-source folks actually fix their software's deep-seated usability problems. The way to do that is not by hiring UX designers or appifying…
Earlier quoted context omitted.
It's not that Devs don't care. It's because every metric anyone has ever gathered says that users don't care.
> It's because every metric anyone has ever gathered says that users don't care. A lot of people go to wal-mart. Doesn't mean that it's a good thing overall for mankind
Earlier quoted context omitted.
Because different graphics are shown are different resolutions, rather than purely scaling a highly detailed 1024x1024 SVG down to 128x128.
>1024x1024 SVG Vectors don't have pixels.
Earlier quoted context omitted.
Because different graphics are shown are different resolutions, rather than purely scaling a highly detailed 1024x1024 SVG down to 128x128.
>1024x1024 SVG Vectors don't have pixels.
Please, educate me. I'm all ears. :)
The situation is messy. Take Facebook.app. The reported size on the App Store is 377MB, the distributed .ipa is 241MB. But it is a universal app which includes fat binaries arm_v7 and arm64 and all the graphics 1x, 2x and 3x. App Thinning halves that size for end users. Yet the App Store reports the full size. There's more. App Store also provides some sort of delta updates [1], which save a lot bandwidth, but failin…
A simple solution to this would be for Apple (or the developer, via Apple) to distribute different builds based on the device installing the app. That is, developers could compile a different copy of the IPA for all target devices. Using variables like CPU architecture, screen size, and other feature flags, a smart compiler could cut a lot of code and assets that never run or display on certain devices. (Granted, thi…
Earlier quoted context omitted.
I was wondering why not use SVG (or any other vector file format) files and render all the graphic on the device, instead of including tons of PNG at various resolutions.
pcwalton's project Pathfinder ( https://github.com/pcwalton/pathfinder ) may eventually lead to an efficient GPU-based vector renderer, which would make this feasible.
In any case, I suspect something like lyon (https://github.com/nical/lyon) would be a better fit than pathfinder, which is both a) not super portable and b) very focused on rendering text, which it does very well.
I remember when apps used to take less than 4k of memory, because 4k was all the RAM in your computer. Then I remember downloading a 3 MB mp3 on my 9600 baud modem and being amazed at how much space was taken up by music that sounded realistic and not like just a bunch of beeps out of speakers that could only make beeps. Then came the old joke about EMACS standing for "Eight Megs and Constantly Swapping". Then I reme…