Re: Sysapp Runtime: Hosted App

In the current spirit of the specification, Marcos is right. Though, the
runtime specification is far from mature and having a specified
behaviour closer to A2 or A3 could be an option.

In other words, the relation between an installed web app and its
non-installed (browser context) version are inexistant for the moment
but we could imagine a model where, if you go to a website using your
browser would be the same experience as installing the application as
long as the manifest would be there. This is something that would be
worth experimenting and I would be interested to know the results of
that experimentation.

--
Mounir

On 07/07/13 01:18, Marcos Caceres wrote:
> Based on my current understanding…   
> 
> On Wednesday, 3 July 2013 at 17:23, SUWIRYA Darmawan wrote:
>> Hi,
>>  
>> We would like to request for clarification regarding Hosted App type.
>>  
>> Use case example.  
>>  
>> Part #1 :
>>  
>> 1. My-App is a hosted app, hosted at www.my-app.com (http://www.my-app.com).
>> 2. It hosts the manifest.webapp under www.my-app.com/manifest.webapp (http://www.my-app.com/manifest..webapp).
>> 3. In its manifest, it asks for permission to access Contact API.
>> 4. User opens Firefox BROWSER, go to www.my-app.com (http://www.my-app.com) for the very first time.  
>> 5. What should happen here ?  
>> A. Will it parse and check the manifest.webapp - and :
>> A.1. offer user choice to install ?
>>  
> 
> Yes.   
>> A.2. or, offer user choice to grant a ONE TIME permission to access Contact API ( valid for this session only ) – without install ?
>>  
> 
> No.   
>> A.3. or, offer user both choices above ?
>>  
> 
> No.
>>  
>> A.4. or, will it force to automatically trigger install ?
>>  
> 
> No.  
>> B. Or will it ignore existence of manifest.webapp there, and will just run it as traditional web app – and :
>> B.1. simply failed on the page where the Contact API is used ?
>>  
> 
> Yes.
>> B.2. or will it popup for permission request on the page where the Contact API is used ?
>>  
> 
> No.   
>>  
>>  
>> Part #2 :
>>  
>> 1. This time, let’s say that user has already had My-App installed.
>> 2. User opens Firefox BROWSER, go to www.my-app.com (http://www.my-app.com).
>> 3. What should happen now ?
>> A. Will it launch the already installed My-App out-of-browser as standalone app ?
>>  
> 
> No.   
>> B. Will it continue running www.my-app.com (http://www.my-app.com) in the browser ?
>>  
> 
> Yes.   
>> B.1. and automatically inherit the permission to access Contact API that’s already granted for the previously installed My-App ?
>>  
> 
> No.   
>>  
>>  
>> We think it would be best if we could expect to have A.3 and B.1. mentioned above as the behavior.  
>>  
>> Can we expect to have this kind of clarification to be explicitly mentioned somewhere in the runtime spec as well ?
>>  
> 
> I'm not sure… are hosted apps still in scope for the runtime spec, or just packaged apps?  
> 
>

Received on Monday, 12 August 2013 13:57:14 UTC