Add ARC++ specific fields to launch data for specific apps.

extensions/common/api/app_runtime.idl

Index: extensions/common/api/app_runtime.idl
diff --git a/extensions/common/api/app_runtime.idl b/extensions/common/api/app_runtime.idl
index bd3f78f9a579f89f55cddf315c9a1916c15d507d..51cd7392e53fad2cfea8584182d6e10bf35f673d 100644
--- a/extensions/common/api/app_runtime.idl
+++ b/extensions/common/api/app_runtime.idl
@@ -47,6 +47,16 @@ namespace app.runtime {
     new_note
   };
 
+  // Status of the play store.
+  [nodoc] enum PlayStoreStatus {
+    // Indicates that the play store is enabled. It also implies available.
+    enabled,
+    // Indicates that the play store is available but not enabled.
+    available,
+    // Indicates that the play store status is unknown.
+    unknown
+  };
+
   // Optional data that includes action-specific launch information.
   dictionary ActionData {
     ActionType actionType;
@@ -90,6 +100,9 @@ namespace app.runtime {
     // launched with. This is null if the app was not launched with a specific
     // action intent.
     ActionData? actionData;
+
+    // Internal fields used to indicate ARC++ status on the device.
+    [nodoc] PlayStoreStatus? playStoreStatus;

[asargent_no_longer_on_chrome, 2016/08/24 21:50:32]

Is this status expected to change often? It's a little unusual to have something
that seems like a fairly static bit of device information that most apps don't
care about passed on every single app launch, as opposed to say having a
separate method for fetching that state for apps that care (and possibly an
event for finding out when it changes). 

[rkc, 2016/08/24 22:05:57]

This won't be set for all apps at the moment. Eventually knowing the kind of
device you're running on is useful information for an app to know when it starts
up. The same was as the launch source, is a public or kiosk session, etc.

The primary argument against not plugging this into an API that an app that
cares calls versus us providing it to an app we care about was whitelisting.

If an app calls back into an API to get this info, considering that we cannot
expose this to all apps, we have to whitelist that app for that API call. This
puts into the same cycle of needing to whitelist apps everytime a new one comes
along, the id changes, etc.


This way, 'whatever' demo app we launch (which later could be a vendor provided
one), this will always work and the app will always know whether playstore is
available or not on that device.

[asargent_no_longer_on_chrome, 2016/08/24 22:37:19]

On a given device, an app can either be launched in a public session or not, or
in a kiosk session or not. Can the PlayStoreStatus change similarly?
 
I'm not sure I understand your argument about whitelisting- wouldn't we either
need a whitelist or not regardless of *how* we provide this information? If we
provide it as a property of LaunchData, we either provide the value to all apps
or use some kind of whitelist to decide which apps see a non-null (or fake?)
value.

[rkc, 2016/08/24 22:41:38]

This value won't go to any apps at all except for the Demo App and the GetHelp
app. The playStoreStatus parameter defaults to UNKNOWN for all other apps. Only
when we're specifically launching the Demo app and the GetHelp app, do we
specify that we want to send this parameter and only those apps get this.

All other apps don't see this value at all (and since it is no-doc, they don't
see it in any documentation either).

   };
 
   // This object specifies details and operations to perform on the embedding