A long-term goal of mustash is to be able to run ARC++ apps without the browser running. However, right now the ARC bridge service that connects the Android container to Chrome OS lives in the browser process. We need a design to handle this.

The lack of a design here is starting to cause problems like this crash:

https://bugs.chromium.org/p/chromium/issues/detail?id=774713
chrome!arc::internal::ArcBrowserContextKeyedServiceFactoryBase

which was caused in part by //components/arc gaining a dependency on ash and using ash::Shell.

 Issue 756056  tracks //ash references in //chrome/browser/chromeos/arc

Issue 768439 tracks Move ArcNotificationSurfaceManager out of the browser process

Note from  hidehiko in issue 768439:
"many ARC services depend on Profile, which is actually necessary (e.g., fileapi, tts, voice, settings, notification, bluetooth, auth flow, accessibility, policy, etc...)"

I think we need a design before we do too much hacking.

xiyuan, can you coordinate with the ARC guys and figure out a plan for this?