Using Extended Scope

At times, the scope value isn't enough to specify the entirety of your app. If your webapp is emcompassed within a single url, then you should only use the W3C scope attribute as such:

{
   "start_url":"https://www.myapp.com",
   "scope":"https://www.myapp.com"
}

however, if your apps spans across multiple domains, then you'll want to use the extended scope to pick up the additional URLs:

{
   "start_url":"https://www.myapp.com",
   "scope":"https://www.myapp.com"
   "mjs_extended_scope":["http://www.myapp.com","http://www.myappauth.com"]
}

If your app uses only subdomain differences, then you may be able to set scope simply by domain:

{
   "start_url":"https://app.myapp.com",
   "scope":"https://myapp.com"
}

However, if you have some subdomains that should be opened in the browser, then you will want to use extended scope:

{
   "start_url":"https://app.myapp.com",
   "scope":"https://app.myapp.com"
   "mjs_extended_scope":["https://video.myapp.com","http://www.myappauth.com"]
}