On 29 Okt., 13:14, Eric F ericfrie...@gmail.com wrote:
Then I suspect these may be more of the points of disagreement:
D) It's up to the developer of an application to offer the user
controls to tweak performance sapping or battery draining.
E) A user uninstalling an app that performs
You want users to complain less? Then get rid of task managers
entirely. They are the problem - they are the ones listing active
apps, when the app is simply just in memory doing nothing.
You want to get less complaints? Stop writing crappy apps and learn
the proper App lifecycle. It's not rocket
On 29 Okt., 04:49, Eric F ericfrie...@gmail.com wrote:
I think there are two problems here, both of them psychological and a
problem adapting from the desktop.
Regarding the problem when the hell is an app doing something when I
don't see it, it's not just psychological...
My recommended
On 28 Okt., 06:36, Syner idesignsgr...@aol.com wrote:
(...) most of the time i am using back or home to exit the
app which sounds like it is not exiting the app.
Depends on your definition of exiting ;)
By default, the foreground stuff is suspended until you resume to the
app, while a running
Ultimately, I think it boils down to a few things in a nutshell (and
my guess is that we agree here):
A) The user should have a good understanding of which applications
are hindering performance (running smoothness. Why is my home screen
so jerky?)
B) The user should have a good understanding
ok i never post but this is interesting. so i have an app that
constantly processes data via remote connection whenever it is open.
this is the nature of the app and i know this. i want to exit the app
when done because i will get a huge bill on my cell plan if i leave it
running all day. most
I think there are two problems here, both of them psychological and a
problem adapting from the desktop.
1) People equate a process existing with an application being
active.
My recommended solution, in all APIs and OS screens that report
active applications should only show/return applications
I would have to strongly disagree with this first statement. Lots and
lots of very popular Windows applications do NOT provide any
indication of background activity.
True, but I was more relating to the usual user experience. For most
Windows applications, one assumes they're running as long
On Wed, Oct 27, 2010 at 3:34 AM, mort m...@sto-helit.de wrote:
- Ready = waiting for AlarmManager/C2DM events (maybe with an alarm
clock as status icon?)
There should be no code running at this point; hence, IMHO, this
status is pointless and confusing.
There could even be an unified stop
On 27 Okt., 09:42, Mark Murphy mmur...@commonsware.com wrote:
- Ready = waiting for AlarmManager/C2DM events (maybe with an alarm
clock as status icon?)
There should be no code running at this point; hence, IMHO, this
status is pointless and confusing.
I don't think so. From a user's point
On Wed, Oct 27, 2010 at 5:01 AM, mort m...@sto-helit.de wrote:
There should be no code running at this point; hence, IMHO, this
status is pointless and confusing.
I don't think so. From a user's point of view, there's no difference
if there's a started service that's actually doing something
I don't think so. From a user's point of view, there's no difference
if there's a started service that's actually doing something by
Handler.postDelayed every 5 minutes and an app that does the same by a
repeating AlarmManager.
Sure there is. It's called a process and a big chunk of RAM.
On 25 Okt., 20:18, Kostya Vasilyev kmans...@gmail.com 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
26.10.2010 14:03, mort пишет:
On 25 Okt., 20:18, Kostya Vasilyevkmans...@gmail.com wrote:
[ snip ]
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
On Mon, Oct 25, 2010 at 10:31 AM, Bret Foreman bret.fore...@gmail.comwrote:
Does Clear Data restore the preferences to their default state?
It does a force stop (kills all app processes, removes notifications,
unregisters alarms), and then erases all of the app's data.
--
Dianne Hackborn
On Tue, Oct 26, 2010 at 4:37 AM, Kostya Vasilyev kmans...@gmail.com wrote:
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.
Ah.
So the issue is with applications.
What you're saying
Actually the official twitter application has a big sign out option in its
menu, right next to settings.
But what if a user just wants no updates temporarily until the app's
restarted, like he's used to by any other OS? And not have to sign on
again after the restart?
Also it is important to
But what if a user just wants no updates temporarily until the app's
restarted, like he's used to by any other OS? And not have to sign on
again after the restart?
Every popular application on windows that does anything in the
background has options within the app to control all of this.
Does onPause() { finish(); } work?
On Oct 25, 2010 11:10 AM, Miguel Morales therevolti...@gmail.com wrote:
I'd just make an automatic response explain to her that hitting home
is like you're minimizing the application, or getting it out of the
way.
Or ask her where in what other program or
I would have to strongly disagree with this first statement. Lots and
lots of very popular Windows applications do NOT provide any
indication of background activity. In fact, I would say it is
relatively rare for them to do so. It's less serious on Windows,
because the effect on battery life is
I would like to highlight mort's point.
As you may be aware, the iPhone recently was upgraded to have some
similar facilities. And I am continually annoyed by it. On balance, it
is a clear advance -- yet I have no way of knowing when I switch
applications, just what is happening to the old one.
On 25 Okt., 05:41, Frank Weiss fewe...@gmail.com wrote:
I kind of agree, but I think I'll stick with what I said. I think the issue
is that when developers see an app listed in what appears to be a list of
running processes (like unix ps or Windows Task Manager), they tend to jump
to the
On Sun, Oct 24, 2010 at 9:20 PM, Bret Foreman bret.fore...@gmail.comwrote:
Since most apps of even moderate complexity make liberal use of the
preferences database and also SQLite, restarting the app isn't going
to produces a known good state. A real factory reset is not going to
happen
Does Clear Data restore the preferences to their default state?
On Oct 25, 9:37 am, Dianne Hackborn hack...@android.com wrote:
On Sun, Oct 24, 2010 at 9:20 PM, Bret
Foremanbegin_of_the_skype_highlighting end_of_the_skype_highlightingbret.fore...@gmail.comwrote:
Since most apps of even
I've been debating this myself, so have been following this discussion
here with interest.
Another good read is this article
http://blog.radioactiveyak.com/2010/05/when-to-include-exit-button-in-android.html
I had a user contact me yesterday who said this
And I just discovered if you do not
I'd just make an automatic response explain to her that hitting home
is like you're minimizing the application, or getting it out of the
way.
Or ask her where in what other program or place do you hit home and
expect the application to close or exit?
Ask here what happens when she hits back on
[ long point-by-point reply below ]
25.10.2010 18:44, mort пишет:
On 25 Okt., 05:41, Frank Weissfewe...@gmail.com wrote:
I kind of agree, but I think I'll stick with what I said. I think the issue
is that when developers see an app listed in what appears to be a list of
running processes
PM
To: android-developers@googlegroups.com
Subject: Re: [android-developers] Re: Application still Running After Exit
[ long point-by-point reply below ]
25.10.2010 18:44, mort пишет:
On 25 Okt., 05:41, Frank Weissfewe...@gmail.com wrote:
I kind of agree, but I think I'll stick with what I
The only unfortunate part of the UI in manage apps which, yes, will be
improved in a future release.
On Sat, Oct 23, 2010 at 10:33 PM, Streets Of Boston flyingdutc...@gmail.com
wrote:
Why is that an *un*fortunate feature?
If your app is still running, it allows for a quicker startup next
'Unfortunate' may be too strong a word. However, as has already been
pointed out, it is a little disorienting, since most of us are used to
'exit' really being 'exit'.
Also, despite what Google has said in the past, there really are times
when the user really does want to just STOP the app, even
On Sun, Oct 24, 2010 at 5:51 PM, Indicator Veritatis mej1...@yahoo.comwrote:
'Unfortunate' may be too strong a word. However, as has already been
pointed out, it is a little disorienting, since most of us are used to
'exit' really being 'exit'.
I kind of agree, but I think I'll stick with
Well, the 'home' or 'back' button does not even imply 'exit. Spending
any time with the platform even a regular user can see that pressing
'home' is a lot like pressing the minimize button on a regular
application and pressing 'back' is simply like saying to the phone
'take me to the last screen
On Sun, Oct 24, 2010 at 9:05 PM, Miguel Morales therevolti...@gmail.comwrote:
Well, the 'home' or 'back' button does not even imply 'exit. Spending
any time with the platform even a regular user can see that pressing
'home' is a lot like pressing the minimize button on a regular
application
Since most apps of even moderate complexity make liberal use of the
preferences database and also SQLite, restarting the app isn't going
to produces a known good state. A real factory reset is not going to
happen without either some complex re-init code in the app or else a
reinstall.
--
You
Why is that an *un*fortunate feature?
If your app is still running, it allows for a quicker startup next
time.
Even if cold or warm startup times are not much different from each
other, what is unfortunate by having your process still running? The
Android OS will kill it when it needs resources.
35 matches
Mail list logo