Insane if you think about how little functionality this kind of app needs. Millions of lines of code for what?
I bet they have a copy of every native library they use except like libc, and probably don’t do any dead code elimination on those. And maybe they also have copies of the app for different ARM versions. And then an additional 20MB of JavaScript because everyone does these days.
Don’t be silly, the whole app is JS!
Gotta bundle the entirety of nwjs/electron. There’s simply no other way.
I used a linux os for my phone for a while called SailfishOS and it was great having fully fledged apps for things like maps, music, etc in the kB range. The app i used for public transport schedules was 15kB.
I’d love to learn more about this. With hyprland I could see a passable “mobile” UI that feels like an extension of my main system, but I’ve not taken the dive into trying to get Linux working on a phone making calls and everything.
I have a Fairphone and i really wanna try out ubuntu touch on there some time. The functionality support with that is pretty amazing now, basically all relevant features are supported. The only issues are VoLTE not working and GPS being slow, but thats because of missing google services so cant be helped.
This also comes with waydroid btw, an android emulator thats pretty fast for all normal applications.
Fairphone 4 feature support: https://devices.ubuntu-touch.io/device/fp4/
Device list for ubuntu touch: https://devices.ubuntu-touch.io/promoted/
I am very conscious of how much data I use due to where I now live. I have noticed that flatpak’s have a massive download size (100’s of megs), especially when compared to the deb package (kb to mb) 2-3 orders of magnitude more.
Anyone correct me if im wrong but afaik, .deb packages just install the actual program and can utilize your systems existing packages as dependencies, while flatpaks are completely isolated and need to bring loads of dependencies with them. This whole trend towards isolated software packages is nice for security and compatibility, but yeah size and performance are comparably dogshit.
Wouldn’t it mostly be assets like logos, maps, icons, etc?
Maps would be much more. Maybe some icons but the app is online only so most things could be loaded live. Its probably just god awful bloated js libraries.
All the little car icons add up to a lot of space, you need a separate one for each driver
Thats a good one :)
high level abstractions
Sell your data
