I don't think you quite understand what I'm saying. First off,
regarding music and radio apps the paid app I have originally had a lot
of back presses to exit. Apparently the developer got some flack on that
and the new version doesn't do that. There's just one main screen with
the menus and then the player part so a lot of back presses aren't
needed. The radio station apps put exits on there because they were
quite layered and more than just a player. I would argue strongly that
if you have a lot of layers you may want an "exit" button or your users
will be unhappy.
Most of the problems are probably from web apps that tend to get layered
and take too many back presses to get to the main screen. My own apps at
most have two layers and dialogs that can be opened but that's all. As
for putting the app in the background, my app requires some calculations
and if it were relaunched I would see the progress dialog again while
the calculations are occurring that's not happen so that assumption is
wrong.
You mentioned the Weather and News app. I recently got the Google Nexus
phone and am a little disappointed in the email apps. My prior phone
was HTC and their email app much better.
And just because "Google Sez" doesn't mean much because most of their
developers have had little experience in the real world of commercial
software sold globally. It's mostly theory from college profs with no
experience either.
On 10/07/2012 01:51 AM, RichardC wrote:
Look at the built-in media player (music). When it is actively playing if
you then just press Home then it shows it is still active (and playing) by
displaying in the Notification area. If you pause it first, then press
Home there is nothing in the Notification area because the application is
doing nothing.
Try and get away from the idea that Android apps need to "exit". When in
the background they should be idle unless they display a Notification.
Also when an app is in the background the system can recover the resources
the app uses if it needs them. An App in the background but not yet
"killed" by the system means that it "re-launches" faster if the end-user
switches back to it.
On Saturday, October 6, 2012 11:31:50 PM UTC+1, jtoolsdev wrote:
On 10/06/2012 02:50 PM, Johan Appelgren wrote:
It gets paused which is what you want to happen.
Not necessarily. That depends on the app and what it does. For
instance I have used two streaming radio apps that the developers
realized that the user might want to exit immediately and provided the
exit either in the menu or on the screen. That's because their was
often a menu or two above the player screen. Just sayin' if you've got
a lot back key pushes to get out of the app one might consider an exit.
--
You received this message because you are subscribed to the Google Groups "Android
Discuss" 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-discuss?hl=en.
