Earlier quoted context omitted.
Google Play supports this, which is mainly used for tablet vs phone, but could be used for different ARM architectures.. http://developer.android.com/guide/market/publishing/multipl...
I thought all Android apps ran in a Dalvik VM. What do you mean by "could be used for different ARM architectures"? Isn't Java bytecode independent of the underlying architecture?
The Apps are Too Damn Big
91–100 of 129 posts
Re: The Apps are Too Damn Big
#92But as I've run down on space, I've started to notice how odd various app's sizes are. There seems to be very little correlation between what I expect and the actual value. Here are some examples from my applications:
First, some apps that have sane sizes
Infinity Blade - 1 GB
Rage - 830 MB
Ghost Trick - 531 MB
Groove Coster - 154 MB
Steambirds Survival - 60 MB
Doodle Jump - 20 MB
But many apps seem to use way more space than I would ever expect: Worms 2 Armageddon - 688 MB
Worms - 209 MB
Catan - 171 MB
Boggle - 104 MB (really? REALLY?)
XFinity (Comcast App) - 41 MB (has downloaded another 50 on my device)Re: The Apps are Too Damn Big
#93Re: The Apps are Too Damn Big
#94Earlier quoted context omitted.
No, we have less than 4 pagefuls of apps on our (admittedly 16GB) 1st-gen iPad, and space is pretty tight. No music and we only keep around about 1-3 hours of video at a time. Games are by far the worst of course, but I'm sure part of that is down to the higher-res textures for iPad2/3 which are useless on the first iPad's much weaker GPU. (the difference is likely even worse between iPhone4S and iPhone 3GS or older)…
Whenever someone comes at me with this topic, I can't help but think of the greatest George Carlin quote of all time, "Simplify."
Re: The Apps are Too Damn Big
#95I don't understand why "universal binaries" exist at all on iOS. On desktops where the app space is more "free" it has a purpose, but it's not like users are regularly moving apps from one iDevice to another -- so what on earth is the point of having three different things altogether? The much more intelligent solution would have been to simply allow developers to upload 3 different binaries, but only present it as o…
I see your point, but users don't need to be moving apps from one device to the other. They just need to DL it on one and have it delivered to others, which is standard icloud procedure now. It's the same for backups, especially for apps that you want a copy nevermind what happens down the way (the app is deleted, the news version is crap, you can't connect to the store etc). As a matter of price, for the reasons abo…
Re: The Apps are Too Damn Big
#96Earlier quoted context omitted.
How many developers are willing to create and upload 3 different versions of their app? I seem to remember reading a thread here on HN complaining about that... Would Apple allow an app maker to release their app for only newer iPads and iPhones, and not for the older devices? (I have no idea...)
It would require no extra work on the developer's part. The 4 binaries could just be bundled in a "super" bundle and still even look like one thing and keep the ".app" extension. So we could actually keep everything as it is (code and resource wise), then when you hit compile, it simply makes 4 copies: 1 for iPhone (non-retina) which includes the .xibs for iPhone and non-HD images, one for iPhone HD (same but with HD…
Right now the situation is: toss whatever you want into the bundle and it's there everywhere. For what you're proposing to have any benefit it would have to be: add files, annotating them with whether they are needed for iphone/ipad, keeping those annotations updated as you work.
Re: The Apps are Too Damn Big
#97So here is the big question: Are you going to buy less apps because of this "issue"? If not then there is no incentive to really fix it, nor for developers is it a problem that will be addressed.
Re: The Apps are Too Damn Big
#98Instead, just about every response (save one on the actual linked page), addresses the issue at hand. It seems to suggests that there is an appropriate level of sensationalism to get your message heard. Anyone have some sort of algorithm that rates a post for how attention-grabbing vs. off-putting its words are?
Re: The Apps are Too Damn Big
#99On the iPad is it possible to download an app and somehow cache it onto some other storage medium (i.e a PC or Mac HDD) so you can uninstall it, backup all your personal files and then sync it back over later (via LAN or USB)? I ask because I was thinking of getting an iPad3 in the near future and was tempted to get the 16 GB model because I have many TBs of storage elsewhere on my PC/NAS/Servers so I'm not going to…
Yes. iTunes on your desktop machine can store (and update) apps that you are not currently syncing to the device. Then, when syncing the iPad, you can check a box in iTunes to indicate that the app should be included on the device.
Re: The Apps are Too Damn Big
#100Earlier quoted context omitted.
It would require no extra work on the developer's part. The 4 binaries could just be bundled in a "super" bundle and still even look like one thing and keep the ".app" extension. So we could actually keep everything as it is (code and resource wise), then when you hit compile, it simply makes 4 copies: 1 for iPhone (non-retina) which includes the .xibs for iPhone and non-HD images, one for iPhone HD (same but with HD…
This would definitely require more work on the developer's part! Right now the situation is: toss whatever you want into the bundle and it's there everywhere. For what you're proposing to have any benefit it would have to be: add files, annotating them with whether they are needed for iphone/ipad, keeping those annotations updated as you work.
When making a universal app you are already forced to do this. Take a look at the Twitter app: it is completely different on iPad vs iPhone. These labels are how it knows what interface to load on each device -- yet the code and resources to load either exist regardless of what device you are on.