On 25 Okt., 20:18, Kostya Vasilyev <[email protected]> wrote:
> Yes, I also get those, and respond back that Android is different.
I mostly do that as well, sometimes in pretty long mails...
> Educating users is better than implementing kludges that users wish on a
> whim.
... but I think it's a sign of a not user friendly design if you have
to explain common users what's going on in the system depths.
If users need to read long explanations about what the task manager
shows, what's the difference between Back and Home, and still don't
know whether the "closed" app will do something in background or not,
there *is* something going wrong. I just hope future Android versions
will address those issues, because it's not only a problem of nasty
mails. It ranges from undesired 1-star-ratings ("stays in background
and spys at me! don't install that bullsh*t!" even if there isn't a
service at all) to dismissing the entire system as slow, battery
consuming, and hard to use.
> Re: Twitter - this should be controllable by the user. I can think of a
> nice away to handle this in the UI, so it must not be that hard.
Really? Which one? Do users have to go to the preferences each time
they want a different behaviour? Do they have to answer a nasty query
when the app's left with "back"? Do they have to look for a checkbox
"[ ] no updates in background" on the main screen?
Also, keep in mind most users wont differ between Back and Home, so
onFinalize() wouldn't be a good place, but also onPause() might cause
troubles because it's invoked when a sub activity or the lock screen
becomes visible.
Sorry, I don't think any of those ways is nearly as intuitive as the
"minimized" (or tray icon) vs. "closed" difference users are used to
by any desktop system. And it's different in each app, if possible at
all.
Besides, non of the Twitter apps I've seen so far offers anything but
a general update interval option in the preferences. And Twitter's
only an example.
> My personal take on task killers is: if my application stops working
> because of a task killer, then it's not my fault.
Sure it isn't, but that doesn't stop users from bad ratings and bad
word-of-moth dissuations. Not every user will contact you before doing
so.
> - Users realize that it's ok to just let Android do its thing, because
> it just works.
Only as long as the apps don't do anything in background (no matter if
by service, broadcasts, AlarmManager, ...). If there wasn't a problem
with that, there wouldn't be so many users which are using task
managers because they actually do improve performance and/or battery
usage.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
