Re: [w3c/webpayments] Finer points of integration with Web App Manifest (#225)

> Firstly, I'm not sure why Web Payments is going to mandate things specific to Play (i.e., the Android platform). How will this work on other platforms? Will you need to specify a native app for each platform? Will we need to specify additional metadata in other platforms for related_applications?

The formal spec is still to be written, but we certainly won't include anything vendor-specific in it. It'll instead say something like "refer to each platform's documentation for additional fields that may be required".

>  The spec allows proprietary fields by vendor-prefixing them. 

Oh, I missed that. So the preferred extension mechanism would be

```json
{
  "related_applications": [
      {
        "platform": "play",
        "url": "https://play.google.com/store/apps/details?id=com.example.app1",
        "id": "com.example.app1",
        "play_version": "...",
        "play_sha256_cert_fingerprints": "..."
      }]
 }
```

? I guess that's not so bad.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/225#issuecomment-289951486