My two cents as an imagined user of this application:
Do not log me out just because your activity was deactivated.
If I'm using your application and want to respond to an incoming phone
call, or another event (such as an SMS or a new email notification) -
when done with that quick interruption, I want to come back to your
application and continue with whatever I was doing.
Requiring me to log in again, even though I was away for a short time,
would seriously interrupt the flow of interacting with the phone.
Rather, implement a scheme where sessions are time limited.
This of course assumes that the application does not contain
security-sensitive data, then it's different (but I don't see you saying
it is).
-- Kostya
11.02.2011 15:12, mah пишет:
If your intention is to call another activity in order to perform some
work -- do you control that activity? Start it "for result" rather
than simply starting it. That way you'll get a callback (with its
result) when it finishes.
I agree with Mark, you should not care about what activities outside
of your control do. You should code as if they don't exist, and if
there's some reason to consider the user "logged out", it should not
be based on what activity is current. Is there some use case you can
think of that justifies taking special action just because the user,
for example, opened their messaging app to reply to the message they
just received?
--
Kostya Vasilyev -- WiFi Manager + pretty widget -- http://kmansoft.wordpress.com
--
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
