yes.
- the peer connection object provides all webRTC API, which by default does not include hardware capture, media rendering, and signaling. If you want a complete solution, you will need those 3 pieces.
- appRTCDemo code (webrtc.org), provides an implementation of audio and video capturers and renderers leveraging native iOS frameworks that you can reuse out of the box.
- You could then just replace the signaling (GAE Channel) by your own. Use the signaling for the original handshake (Offer/answer) and the media/data path setup (ICE candidate exchange) and the webRTC part will be taken care of.