Earlier quoted context omitted.
As long as you don't need a lot of hi-res graphics. One of the no-frills icon themes installed on my Linux laptop (from which I'm typing) is 170M, just because it has a pack of icons rendered for each of the 8, 16, 18, 24, 32, 48, and 64 pixel sizes. (And no, vector icons are not equally useful in this whole range of resolutions; you need to lower the level of detail for small resolutions to avoid pixel sludge, and i…
You don't need "hi-res graphics" in an app.
Why is the Gmail app 700 MB?
361–370 of 403 posts
Re: Why is the Gmail app 700 MB?
#362Re: Why is the Gmail app 700 MB?
#363Earlier quoted context omitted.
Proper unicode font support is like 1.2GiB (noto, but I haven't found any complete unicode font collections that are significantly smaller). There's bloat for sure, but supporting universal text is one that I think is not a waste of space.
Unsure if this is useful to you but have you heard about GNU Unifont? It’s not as nice and comes with some asterisks but damn it’s very compact. I first read about it via this blog post: https://shkspr.mobi/blog/2019/04/banish-the-%ef%bf%bd-with-u...
Re: Why is the Gmail app 700 MB?
#3641.15 GB for me - dear god. There's a comment in the article with two helpful links: https://news.ycombinator.com/item?id=30443570 https://www.emergetools.com/app/example/ios/com.google.Gmail The bloat? Mostly "localization".
Re: Why is the Gmail app 700 MB?
#365Earlier quoted context omitted.
Not sure how that would help. SVGs aren't natively handled on iOS. They get rasterized during build time and that's what gets shipped with an app.
Huh, is there a requirement that they be rasterized at build time? If I had a choice, I'd rather ship the SVGs in the bundle alongside a renderer like ThorVG and render at runtime. The renders could even be cached if the rendering itself was expensive.
You can of course override this behavior and redraw your vector every 8.3 ms if you want, but I promise you that this is not faster. For sparse pyramid-tiled vector images like Google/Apple maps, this is a two step process using the latter method followed by the former.
Re: Why is the Gmail app 700 MB?
#366Earlier quoted context omitted.
It’s probably frameworks + localized assets. With dynamically linked frameworks you bear the cost of the entire framework (and its dependencies) even if you just use a few functions. iOS apps also need to include all localized assets in each app bundle.
>iOS apps also need to include all localized assets in each app bundle. Is this a hard requirement? I use two languages or at best three. The other 100 language don't matter to me. Why do I have to waste space on my smartphone. This adds up if I have hundreds of apps.
You could get localizations OTA, but that's engineering you need to do to make that happen.. or a product you purchase, as there's various localization managers offering these options in their software.
Re: Why is the Gmail app 700 MB?
#367Earlier quoted context omitted.
'90s Microsoft was like early christians: harshly persecuted, only for everyone else to eventually adopt their ways. In this metaphor, emperor Constantine is probably Steve Jobs.
Harshly persecuted how, exactly? They got a slap on the wrist, still continued to ship IE as the default browser and stayed dominant browser vendor until another monopoly started to abuse its position.
Re: Why is the Gmail app 700 MB?
#368> For most of that period, the size of the Gmail app hovered around 12 MB, with a sudden jump to more than 200 MB near the start of 2017... The Gmail app, on the App Store, is currently 760.7 MB in size. With charts: https://www.axios.com/2017/12/15/the-top-iphone-apps-are-tak... I had no idea common apps used to be just 10-30 MB. But are now hundreds of MB. Something like Gmail doesn't have massive hi-resolution bit…
We once ran Windows 95 with Encarta in about the same amount of disk space. We crossed lunacy long ago.
I agree, that we crossed lunacy long ago, and that LLMs have not helped in the slightest.
Re: Why is the Gmail app 700 MB?
#369Earlier quoted context omitted.
There's actually a bit more to it than that. A lot of what Apple apps actually do is hidden in frameworks made for that one specific app , which, unlike with 3rd-party applications, are part of the system, not of the app itself. Compare the size of Safari.app versus Safari Technology Preview.app (which actually ships all the frameworks it needs).
Sounds like how Internet Explorer used to be integrated in Windows. That was quite contentious at the time!