On Saturday, March 2, 2013 2:32:23 PM UTC-6, John Coryat wrote:
it sounds like the bug on your side (no offense and sorry if I
misunderstood the problem)...
The problem isn't our app, it's the state of Android introductory
orientation. If users don't know how to properly end apps, then
On 07/30/2013 08:16 AM, Chris wrote:
On Saturday, March 2, 2013 2:32:23 PM UTC-6, John Coryat wrote:
it sounds like the bug on your side (no offense and sorry if I
misunderstood the problem)...
The problem isn't our app, it's the state of Android introductory
orientation. If users don't know
We had an option to display an exit button that we removed in the last
update. With millions of users, only one person complained that it was
missing. I think the majority of users get the idea that the back key
backs the user out of the application.
-John Coryat
On Tuesday, July 30, 2013
What's wrong with the home button? It should quickly exit the app unless it
has something active that should continue like playing music in which case
there should be an ongoing notification to make the user aware of it,
preferably with a pause/stop button in the notification. I rarely press
On 07/30/2013 11:15 AM, Johan Appelgren wrote:
What's wrong with the home button? It should quickly exit the app unless it
has something active that should continue like playing music in which case there should
be an ongoing notification to make the user aware of it, preferably with a
An exit button is probably only necessary that has too many UI layers
(usually done with Intents) that require a number of back keys to exit.
Makes perfect sense to have one then. There is a problem too of leaving
too many apps open and running out of memory to run an app especially if
it
On Tue, Jul 30, 2013 at 11:08 AM, Brian Conrad brianjto...@gmail.com wrote:
On 07/30/2013 08:16 AM, Chris wrote:
Where does it state in developer documentation that the back button is
supposed to end a program? I don't see what it has to do with Android
introductory orientation, especially
You're not supposed to exit Android apps period. At least not in the desktop
process centric meaning of exit. Works fine in most cases except for apps that
don't pause worker threads in onPause or abuse services, alarms and broadcast
receivers to stay alive or get restarted unnecessarily.
--
On 07/30/2013 01:12 PM, Johan Appelgren wrote:
You're not supposed to exit Android apps period. At least not in the desktop
process centric meaning of exit. Works fine in most cases except for apps that
don't pause worker threads in onPause or abuse services, alarms and broadcast
receivers
I think this guys is more of an outlier than representative of a typical
Android user . We got to calibrate UI assuming a minimum threshold of
intelligence / familiarity /proficiency
from user . I must say that for more than 90% of user i can safely say
that they either know that back key is the
The thing is I've gotten numerous emails over the years and comments on
Google Play regarding how our app doesn't end, or doesn't update imagery.
The only way that's possible is if the user ends the app with the home
key instead of the back key. It might be obvious to us, but it certainly
FWIW, John, I am a LONG time techie pro, my street cred dating back to
1970 (and one of your beta testers :), but I am also relatively new to
Android, having gotten only my 2nd device last Black Friday. I was NOT
aware until this thread there was a difference in the exits. Well, I knew
there were
I do think there is a significant number that doesn't know.
Also, on many systems, using the Home Screen button *does* end programs. I
say that because of the advanced setting Task Management = Aggressive.
Some phones ship with it on in their crusade for battery life.
I do not claim to know
Automatic refresh is a premium feature. Lame, I know, but it is one that
drives the users to go premium. There's a refresh button that a user can
use to update the imagery, but they have to: a) know what refresh means b)
recognize the button. That's already a stretch for a lot of them.
When
it sounds like the bug on your side (no offense and sorry if I
misunderstood the problem)
are you using onResume, etc?
you can do refresh in onResume which will be fired anyway
On Saturday, March 2, 2013 7:22:31 PM UTC+2, John Coryat wrote:
Automatic refresh is a premium feature. Lame, I
it sounds like the bug on your side (no offense and sorry if I
misunderstood the problem)...
The problem isn't our app, it's the state of Android introductory
orientation. If users don't know how to properly end apps, then they can
run into all kinds of problems. Case in point are task
On 03/02/2013 12:32 PM, John Coryat wrote:
it sounds like the bug on your side (no offense and sorry if I
misunderstood the problem)...
The problem isn't our app, it's the state of Android introductory
orientation. If users don't know how to properly end apps, then they can
run into all kinds
On 3/2/2013 1:32 PM, John Coryat wrote:
it sounds like the bug on your side (no offense and sorry if I misunderstood the
problem)...
The problem isn't our app, it's the state of Android introductory
orientation. If users don't know how to properly end apps, then they
can run into all kinds
On Saturday, March 2, 2013 9:22:31 AM UTC-8, John Coryat wrote:
Automatic refresh is a premium feature. Lame, I know, but it is one that
drives the users to go premium. There's a refresh button that a user can
use to update the imagery, but they have to: a) know what refresh means b)
19 matches
Mail list logo
