On 6/23/2010 8:15 AM, Dave Neary wrote:
I agree with Arjen that if your app is going to be in a context where
power is important, then you should just make power usage a top priority
regardless of "on A/C" or "not on A/C". But with netbooks and mobile
phones, we'll clearly be in a situation where some portion of the usage
time will be on A/C and in those situations, saving battery is not an
issue (general "being a good citizen" still is, of course).
other than while charging being in a thermal sensisitve environment you
mean ;)
Once the tradeoff between user experience and power consumption is clear
for a certain case it will be much easier to decide whether AC/battery
status information is needed.
Here's a few examples that come to mind:
* Video player - wants to give best experience possible when on A/C, so
goes with HD, high frame rate - but when on battery, reduces video
quality& frame rate to use less energy
but your phone and tablet almost always are only used on battery. So
basically you now have degraded behavior
all the time the user is using the device. sounds like a really bad plan
to me.
* Email application that checks for& downloads email every minute/5
minutes when you're hooked to A/C, but only every half an hour when on
the move
the difference between 5 minutes and 30 minutes is not power visible to
be honest; this would be a "how am I connected" tradeoff not a power one.
And .. half an hour on all phones all the time? you're kidding ;)
i can go on and on, but... with devices being almost always on battery,
and your examples very visibly and annoyingly degrading the experience...
(and often NOT being about AC/Battery.... but about where the device is
at that point in time)
_______________________________________________
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
