We optimized our polling pattern so the API we hit every 20 seconds returns only about 100 bytes representing what other APIs to call back to retrieve just what's changed. It's all done in a few milliseconds. If there are changes, we retrieve just those changes and reconcile with existing data in the app. Very fast and efficient.
I stand corrected on Android apps always running in background. That was an older version Android problem we ran into but since Marshmallow, this shouldn't be a problem for you. With both Doze and Standby, you shouldn't have to worry about your app using battery when it's not in the foreground unless you meet the criteria listed in the article. https://www.greenbot.com/article/3027918/android/how-doze-and-app-standby-finally-fixed-android-battery-life-in-marshmallow.html <https://www.greenbot.com/article/3027918/android/how-doze-and-app-standby-finally-fixed-android-battery-life-in-marshmallow.html> I have never tried to reduce frame rates. Erik On Jan 3, 2018, at 11:54 AM, bilbosax <waspenc...@comcast.net> wrote: Thanks for the information Erik. Wow, your app sounds seriously legit if you need to query your data every 20 seconds ;) My app feels expensive enough because of the amount of data that I am pushing, but yours sounds like it could have become a money pit if you had not come up with this solution. I ended up using Flashlabs Rich Webview ANE because I have to communicate with Javascript alot and found it not a simple task using StageWebView. Do you know if it is necessary to reduce your framerate to save battery when Event.DEACTIVATE is fired, or does Apple/Google suspend the app in a way that makes this unneccessary?? -- Sent from: http://apache-flex-users.2333346.n4.nabble.com/
