[ 
https://issues.apache.org/jira/browse/OPENMEETINGS-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426955#comment-17426955
 ] 

Sebastian Wagner commented on OPENMEETINGS-2683:
------------------------------------------------

Yeah doing a PMA (progressive web application) is an option I think. In general 
it means nothing else then: Saving the page to your home screen. Thats it.

It has some advantages and provides additional options (eg controlling full 
screen). This could be especially interesting for the Mobile Version of 
OpenMeetings. In order to compete with native Mobile Apps.

It makes it more like look and feel like an actual Mobile App, since you can 
start OpenMeetings directly from an icon on your device.

 

> Explore what features of manifest file are useful for OpenMeetings
> ------------------------------------------------------------------
>
>                 Key: OPENMEETINGS-2683
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2683
>             Project: Openmeetings
>          Issue Type: New Feature
>          Components: Mobile client
>            Reporter: Sebastian Wagner
>            Assignee: Sebastian Wagner
>            Priority: Major
>             Fix For: 7.0.0
>
>
> OpenMeetings on a Mobile device is almost unusable because the aspect ratio 
> on portrait mode is almost impossible to click any button.
> As well as the layout of the application is more width than height.
> Apparently there is a way to force the browser into landscape mode using the 
> manifest.json file. There might be also other features out of the manifest 
> file that may improve the experience. It is designed to help Progress Web 
> Apps to more look and feel like Native Apps on Mobile devices.
> See also:
>  * [https://www.w3.org/TR/appmanifest/]
>  * [https://developer.mozilla.org/en-US/docs/Web/Manifest] 
>  * [https://web.dev/add-manifest/] 
>  * 
> [https://stackoverflow.com/questions/14360581/force-landscape-orientation-mode]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to