We would like to be able to build element-android client without the voip feature and its related dependences (webrtc, jitsi...)
A best solution would be to be able to custom the voip solution. The requested configuration would not be only with/withoutVoip, but a way to provide a module to handle the voip feature in the application
Why would you like to do it?
Ease customisation of Element
How would you like to achieve it?
add a flavorDimension voip and define 2 flavors withvoip and withoutvoip
or
extract the voip service in a module in order to be able to disable the service or customise the voip call handling in the application. For example this module may allow a fork of element-android to manage the voip calls outside the application
Your use case
What would you like to do?
We would like to be able to build element-android client without the voip feature and its related dependences (webrtc, jitsi...) A best solution would be to be able to custom the voip solution. The requested configuration would not be only with/withoutVoip, but a way to provide a module to handle the voip feature in the application
Why would you like to do it?
Ease customisation of Element
How would you like to achieve it?
voip
and define 2 flavorswithvoip
andwithoutvoip
orWe would prefer the second option
Have you considered any alternatives?
No response
Additional context
No response