Developing a watchface, what functionality are the biggest drain on battery?

Looking to optimize my code and minimize the amount of drain on my battery.

Some basic questions:

Is it better to spread Background tasks out across multiple small shorter calls or better to do one big one less frequently?

Is reading or writing from Storage or Fonts or Properties expensive?

Are calculations or lines of execution expensive when in non-sleep mode or does it not matter because it is just going to keep looping?

In general -- what should I be minimizing to maximize my battery life?

Thanks!

0 BobMiles over 4 years ago

I think the best for you would to use the profiler in the simulator. It will tell you exactly which part of your code needs what amount of processing time. And then try and reduce the total execution time.

You will see that storage calls are very expensive for example.

0 Heckles over 4 years ago in reply to BobMiles

Thanks! Didn’t know that was there. Very helpful.