Uploading, UX triggering, pref management should all be abstracted in such a way that we can ship only relevant code on Android, and implement the equivalents in Java.

Shortest term: allow Android to only write prefs, not call a JS function, when enabling or disabling.

This splits out all of the logic that isn't concerned with uploading and prefs. This is step 1, with subsequent steps being to conditionalize the definition of HealthReporter and its bagheeraclient imports, define a class suitable for use on Android, and conditionally use that instead, and fix tests appropriately. I was planning to define MOZ_USE_EXTERNAL_HEALTHREPORTER to control this; do you have an opinion?

Comment on attachment 713194 [details] [diff] [review] Part 1: split out AbstractHealthReporter. v1 Review of attachment 713194 [details] [diff] [review]: ----------------------------------------------------------------- I didn't verify that the chunks moved to the new prototype didn't actually change. I trust you to not try pull off something mischievous :) When I had this refactoring designed in my head, I arrived at a slightly different API design. I won't talk about it unless you are interested. You got there first. You win :)

Part 1: https://hg.mozilla.org/services/services-central/rev/baa43b00de2b

I'm going to resolve this, because it crosses a release boundary. Will open another bug if necessary.