I think it's a case of optimization. You can either build a handles-all-situations MS-Office, or you can optimize for an 80/20. When your feature set grows out of the 80/20 you run into issues.
For me, a perfect example is locking/unlocking the pivot on the iPhone by double-clicking the home button, sliding the bottom bar rightwards, clicking an icon with a turny-lock on it. That's total madness, but I understand how it got there. When I finally discovered that I mailed all my iPhone-owning friends, none who knew the trick.
Similarly, killing apps that remain in memory. Double-click home, hold down one of the icons until all the in-memory apps show a (-), then delete each of them. Granny will never get that. I'd personally like a settings page that just lets me set a default on/off for in-memory for each app so I don't have to keep cleaning up apps that want to use GPS and memory.
So, rather than having 10 buttons on your iPhone you now have one button and have to use morse-code to tell the thing what you want. Rather than an ugly screen menu, you have to use Google to figure out how to take a screenshot or un-lock the swivel.
When all you have is a home-button, everything looks like a nail. Or something.
I've made similar optimizations/(later possible "mistakes") myself. I tend to put a lot of effort into few features to do exactly what's required, but that always has to be balanced with possible future feature expectations. It's possible to paint myself into a corner with that, so I often think "is this app meant to be 'tight' like an Apple app, or should I optimize for extensibility?"
Those aren't necessarily apps that remain in memory. The first few might be, but not if they haven't been used in a while. The rest of the entries are merely a list of recently used apps that are neither using processor time nor in memory.
Point taken, but when I want to remove a GPS-using app because the GPS indicator is still on, I need to go there and kill it. Usually I do this for recently-used apps because I no longer need them. Granny wouldn't have a clue, even though she's now "stopped" the app. And I do try to make sure all apps know to not run in the background, but even that's extra admin.
For me, a perfect example is locking/unlocking the pivot on the iPhone by double-clicking the home button, sliding the bottom bar rightwards, clicking an icon with a turny-lock on it. That's total madness, but I understand how it got there. When I finally discovered that I mailed all my iPhone-owning friends, none who knew the trick.
Similarly, killing apps that remain in memory. Double-click home, hold down one of the icons until all the in-memory apps show a (-), then delete each of them. Granny will never get that. I'd personally like a settings page that just lets me set a default on/off for in-memory for each app so I don't have to keep cleaning up apps that want to use GPS and memory.
So, rather than having 10 buttons on your iPhone you now have one button and have to use morse-code to tell the thing what you want. Rather than an ugly screen menu, you have to use Google to figure out how to take a screenshot or un-lock the swivel.
When all you have is a home-button, everything looks like a nail. Or something.
I've made similar optimizations/(later possible "mistakes") myself. I tend to put a lot of effort into few features to do exactly what's required, but that always has to be balanced with possible future feature expectations. It's possible to paint myself into a corner with that, so I often think "is this app meant to be 'tight' like an Apple app, or should I optimize for extensibility?"