News for hackers. Stuff that matters.
Re:Dealing with Android fragmentation – experiences from our... by VLM on Monday August 05, 2013 @11:03AM (#6160492)
The biggest problem I see from experience is memory limitations impacting design.

I have a republic wireless android phone that ships with very little free memory until you root it. Have to be Very careful and pick and choose which apps you install based on size. Is it worth uninstalling evernote to fit this new app? Or is your new app worth the $100/month it would cost to switch to a carrier with a more advanced phone where space wouldn't matter?

I also have a 32 gig nexus7 tablet where I pretty much don't have to care about app size. 500 meg game, well OK whatever.

The article advises fooling around with different UI depending on device size. Users actually hate that. I can't stand how baconreader renders differently on my phone and on my tablet, when they should be the same. gmail is another offender. I want the phone gmail on my tablet and the tablet baconreader on my phone (or was it the other way around?) Users can understand screen and finger size issues but can't tolerate arbitrary foolin around with UI design.

Re:Dealing with Android fragmentation – experiences from our... by outworlder on Monday August 05, 2013 @01:11PM (#6161351)
So, by "memory", you mean internal storage, not RAM?

They are two different things, with their own problems,so it is better to try to be precise.

Re:Dealing with Android fragmentation – experiences from our... by VLM on Monday August 05, 2013 @01:43PM (#6161559)
Yes, although I imagine there are devices that are RAM limited.

I have enough ram not to be ram limited, but for example per my "running" tab, tunein radio pro burns up about 20 megs continuously. No idea why and I don't think I'm getting 20 megs worth of battery draining "anything" out of it. Too bad, because when I'm actually using it, its an awesome app. Google Goggles burns a bit less than 6 megs continuously, even if you're not using it, to do... what exactly?

This all costs battery, if nothing else. I'd rather have an extra hour of runtime rather than goggles and tunein starting up slightly faster when I use them.

There should be a configurable android setting where "piggish" apps can ask to start a battery sucking and ram sucking 24x7x365 service, but this specific app is simply not allowed to do so because its a pig-app.