What errors did you fix due to energy efficiency issues when developing mobile applications

For those who write mobile phone apps, what bugs / issues have you fixed to improve energy efficiency and how much has the fix improved?

The next question is: is energy efficiency considered as important as functions, and avoids functionality errors when writing mobile applications?

+3
source share
5 answers

To answer the following question, very few customers notice any difference in energy efficiency or battery life from using a particular application. This is almost never mentioned in App Store reviews. I write energy-efficient code mainly because I don’t want to run my own device batteries while testing and using my applications.

Some suggestions for iPhone apps:

  • Write your application so that it works on the slowest device (iPhone 2G or 3G) with the slowest OS (4.x on 3G). Then it can mainly work on much faster current devices.

  • In graphics routines, try not to redraw everything that is already drawn. Use a small CALayer or subview for localized updates / graphics changes.

  • async , .

  • C ( Foundation) , ARM, .

  • , . , , .

+1

.

, GPS , GPS . , , GPS , .

, : , , .

+1

EE , .

, . , .

, / .

+1
  • + , cpu ( iPhone + Android).
  • ,
  • , , , .
  • , ? , .
  • , (GPS ).
  • push over pull, .
+1

, opengl, .

, , .

LWP, 5 . , , . FPS FPS. . 60 , 30 .

, fps .

, , OLED, Android, , . - , OLED . , , . - , .

GPS, 3G, .

0

Source: https://habr.com/ru/post/1778636/


All Articles