# Licode android new client

**URL:** https://discourse.lynckia.com/t/licode-android-new-client/750
**Category:** Uncategorized
**Created:** [March 19, 2018, 7:57am UTC](https://discourse.lynckia.com/t/licode-android-new-client/750 "2018-03-19T07:57:06Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![dawn\_liuwei](https://avatars.discourse-cdn.com/v4/letter/d/71c47a/32.png) [@dawn\_liuwei](https://discourse.lynckia.com/u/dawn_liuwei)
#### Post date: [March 19, 2018, 7:57am UTC](https://discourse.lynckia.com/t/licode-android-new-client/750/1 "2018-03-19T07:57:06Z")

</div>

> **[K-GmbH/licodeAndroidClient](https://github.com/K-GmbH/licodeAndroidClient)**
>
> Android Client with WebRTC for Licode project. Contribute to K-GmbH/licodeAndroidClient development by creating an account on GitHub.

  
this client is too old

Is there a new version？

---

<div class="post-metadata">

### Author: ![chunchieh](https://avatars.discourse-cdn.com/v4/letter/c/ee59a6/32.png) [@chunchieh](https://discourse.lynckia.com/u/chunchieh)
#### Post date: [May 22, 2018, 2:05am UTC](https://discourse.lynckia.com/t/licode-android-new-client/750/2 "2018-05-22T02:05:36Z")

</div>

Have the same problem for K-GmbH/licodeAndroidClient six months ago, and then turn to make my own Licode-ErizoClientAndroid from referencing Licode-ErizoClientIOS and Android [apprtc](https://chromium.googlesource.com/external/webrtc/+/master/examples/androidapp). And I’m very sorry for **not opening this ErizoClientAndroid source** due to our company’s policy. But I can describe my steps to porting Licode-ErizoClientIOS to Licode-ErizoClientAndroid:

1. Trace Licode-ErizoClientIOS to understand Licode signaling & WebRTC RTCPeerConnection flow, you have to trace Objective-C source code and will be better to have iOS device and developer account. (About one week)
2. Integrate Licode signaling channel for emitting(token, publish, subscribe) and receiving(signaling\_message\_erizo) event, tested well for Licode pre-v5.4 and Android [Socket.io](http://Socket.io) client 1.0.0. (About one week)
3. 1 v.s. 1 video call: Use prebuilt google-webrtc version 1.0.20849 and reference apprtc to integrate your WebRTC RTCPeerConnection logic into above signaling exchange, especially for SDP and ice candidate info.(About one week)
4. Multiple vide calls: Need to manage multiple RTCPeerConnection: one for publish and many for subscribe (About two weeks)

And will be better to understand licode architecture diagram first before you start 😉
