Android apps management architecture flaw?

Posted by kentnguyen on Friday September 16, 2011 @12:56AM
from the self-post dept.

I have just begun developing for Android and coming from iOS background. I'm really surprised to find out that a large number of Android phones including the Nexus One has so limited internal memory and it only takes about 5 apps to fill up that space despite having huge SD card memory.

From and end-user experience point of view, I couldn't understand why do I need to know how to move app to SD card and the worst part is that most of the apps that I need to use (map update, Facebook, Twitter, ...) can't be moved.

I couldn't shake the thought of a broken philosophy for user experience on Android.

I respect consumer choices but still... Can anyone enlightment me?

( 3 comments | on HN )

Re:Android apps management architecture flaw? by antrix on Friday September 16, 2011 @01:08AM (#3003273)

I think it was a bad decision to ship devices with limited internal memory. But I'm trying to figure out how this is an 'architecture flaw'.

[ Parent | on HN ]

Re:Android apps management architecture flaw? by kentnguyen on Friday September 16, 2011 @02:28AM (#3003397)

Might be not 'architecture' but I think that it's a flaw so fundamental which should not even be there in the first place.

A device having small internal memory is fine since it's expensive. But having a huge external memory and not able to use it for common tasks is just so wrong.

[ Parent | on HN ]

Re:Android apps management architecture flaw? by 2AM on Friday September 16, 2011 @06:58AM (#3003972)

there are many things that google could have done if time allowed, but the manufacturers needed something quickly to compete with Appl€. there's no other company or entity who could have made it better.

it's not fair to compare iOS and Android, it's not one device or even strictly controlled specs.

[ Parent | on HN ]