title: What is exactly "Adaptive battery", and what does it mean for app developers?
body: <h2>Background</h2>
  
  <p>Google has announced on Google IO 2018 something that's called "Adaptive battery":</p>
  
  <p><a href="https://youtu.be/ogfYd705cRs?t=3562" rel="noreferrer">https://youtu.be/ogfYd705cRs?t=3562</a></p>
  
  <p>As a user, this sounds promising, but as a developer, this could be an issue in some cases.</p>
  
  <h2>The problem</h2>
  
  <p>They said it checks which apps are used more often using AI, and that the "OS adapts to your usage pattern" :</p>
  
  <blockquote>
    <p>Adaptive Battery uses on-device machine learning to figure out which
    apps you’ll use in the next few hours and which you won’t use until
    later, if at all today</p>
  </blockquote>
  
  <p>To me it sounds like it might be yet another step in the "war against background processing apps".</p>
  
  <h2>What I've found</h2>
  
  <p>Since this is very new, I haven't found anything of how it works, and if developers should be concerned about it and need to change apps.</p>
  
  <p>Only things I've found are articles from user-point-of-view.</p>
  
  <h2>The questions</h2>
  
  <ol>
  <li><p>What is exactly "Adaptive battery"? </p></li>
  <li><p>Should developers be worried when it's being enabled? </p></li>
  <li><p>Which app components, background-processing classes, alarms, wakelocks, syncing classes, background/foreground services etc... - might be affected by it? </p></li>
  <li><p>If indeed it can affect the nature of the app, is there any API to check if it's enabled, and act accordingly? If so, how?</p></li>
  <li><p>How does it compare to other battery-saving mechanisms?</p></li>
  </ol>