EricssonResearch / EricssonResearch/openwebrtc-android-sdk
JDK sdk
- Dominant language
- Java
- Stars
- 45
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
Hi! Would it be possible to release openwebrtc-android-sdk as regular java api? Maybe extract the components that are unspecific to android and cross-release it as a seperate jar? Most of the SDP rendering/parsing and certificate related stuff would be really useful for [jvm users](https://github.com/danielwegener/openwebrtc-java) too!
So would it be feasible to release the "core" as platform independent jar and inject the specifics depending on the runtime?
I did a quick [poc](https://github.com/danielwegener/openwebrtc-android-sdk/commit/1b69c74dfedeeb28067a23ebd563fa6f7489d0ec) to show what classes are android specific - and they are [not so many](https://github.com/danielwegener/openwebrtc-android-sdk/tree/kick-android/sdk/src/main/java/android).
Best regards
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the referenced proof-of-concept commit and the classes under sdk/src/main/java/android to identify the Android-specific components. Compare those classes with the SDP rendering/parsing and certificate-related components mentioned in the issue. Done means the feasible scope and design for a platform-independent JVM jar, with runtime-specific behavior separated, are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- api, mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100