On 6/23/2010 6:32 AM, Arjan van de Ven wrote:
On 6/23/2010 6:27 AM, Rob Staudinger wrote:
On Wed, 2010-06-23 at 14:06 +0100, Dave Neary wrote:
[...]
Good point - it would be great to know when you're on battery, and do
even less.
What would be even more helpful than going back and forth
"apps should know about battery" ..
"no they should not" ..
"but they need to" ..
would be if people who have concerns about their apps would bring actual
use-cases forward.
Once the tradeoff between user experience and power consumption is clear
there are generally tradeoffs, sure.
but battery tends to be not the right input to that.
ask any datacenter operator.
but even on phones.... most often performance is temperature limited,
as is battery charging.
if you suddenly make the phone hot due to heavy cpu work, your battery
will charge slower.
And/or you may have less capacity to raise the cpu speed due to the
system being warmer already.
_____________
btw one thing to add; if you degrade the user experience (that's what
"tradeoff" implies) on batter, you need
to also come to grips with the mobile usage model; it's not unthinkable
that a large portion of mobile device users
(be it phone or tablet) is using his device only ever on battery (and
charges his/her device when he's not using it).
That'd basically mean that you provide a 100% degraded experience to a
sizeable portion of your userbase.
_______________________________________________
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
