WebRTC extra
Version 3 (Adrian Georgescu, 02/19/2018 10:36 am) → Version 4/7 (Adrian Georgescu, 02/19/2018 03:41 pm)
h1. Sylk WebRTC roadmap
h2. Better Mac support
Safari recently added WebRTC support in its iOS and OSX operating systems. Unfortunately, Unfortunately there are many situations satuations where the software does not work because of interoperability issues. The software must be tuned to support Safari Web browser on both mobile and desktop platforms. browser.
h2. Mobile support
Because of limited browser support, navigating the web page using a mobile phone should offer the users the option to run or download the corresponding app from the store in order to benefit of all the features. The landing page should present the users with 3 choices:
* Open in Web Browser
* Open in already Installed App
* Download app from the Store
The mobile app shall be rebuilt for both iOS and Android using latest SylkServer version as now there is a disconnect between desktop and mobile behaviour.
h2. Media Better media handling
h3. Audio only conferences
While the software is designed around video conferencing there is a need to support participants that join only with audio. There may be privacy issues, or technical limitations in the platform used to join the conference. The interface must be adjusted accordingly to support this capability.
h3. Multiple cameras support
Currently only one camera is supported. Ideally, a camera should be selected prior entering the conference. This can be done by adding a preview stage, before starting the actual call. This way the user can see its surrounding, adjust her hair. , etc... The feature is more usable for Mobile devices that typically have dual cameras, and for desktop can be seen from a perspective of privacy (chasing no camera at all).
h3. Add/remove video
While in a call, it should be possible to change camera or promote an audio only call to a video call. This should be theoretically possible with the addition of WebRTC replace media primitive. Needs to be investigate if poissible with the current chain of dependencies as all must support this feature.
h2. Chat sessions
Each participant should be able to enter short messages disseminated to all other participants. The Chat screen can be collapsed/promoted bye each user.
h2. Better Mac support
Safari recently added WebRTC support in its iOS and OSX operating systems. Unfortunately, Unfortunately there are many situations satuations where the software does not work because of interoperability issues. The software must be tuned to support Safari Web browser on both mobile and desktop platforms. browser.
h2. Mobile support
Because of limited browser support, navigating the web page using a mobile phone should offer the users the option to run or download the corresponding app from the store in order to benefit of all the features. The landing page should present the users with 3 choices:
* Open in Web Browser
* Open in already Installed App
* Download app from the Store
The mobile app shall be rebuilt for both iOS and Android using latest SylkServer version as now there is a disconnect between desktop and mobile behaviour.
h2. Media Better media handling
h3. Audio only conferences
While the software is designed around video conferencing there is a need to support participants that join only with audio. There may be privacy issues, or technical limitations in the platform used to join the conference. The interface must be adjusted accordingly to support this capability.
h3. Multiple cameras support
Currently only one camera is supported. Ideally, a camera should be selected prior entering the conference. This can be done by adding a preview stage, before starting the actual call. This way the user can see its surrounding, adjust her hair. , etc... The feature is more usable for Mobile devices that typically have dual cameras, and for desktop can be seen from a perspective of privacy (chasing no camera at all).
h3. Add/remove video
While in a call, it should be possible to change camera or promote an audio only call to a video call. This should be theoretically possible with the addition of WebRTC replace media primitive. Needs to be investigate if poissible with the current chain of dependencies as all must support this feature.
h2. Chat sessions
Each participant should be able to enter short messages disseminated to all other participants. The Chat screen can be collapsed/promoted bye each user.