QUOTE
Andy suggested this idea to me earlier. While possible, it is not desireable. When we pursue this, it will be done as an XBC interface and not 'hijacking' someone elses interface. From our point of view, there is no advantage in using the xlink interface.
I suggested adapting your XBC engine to talk to Kai UI's before. What I just proposed was considerably different.
Lemme lay it out:
User downloads XBC package, from xbconnect.com - looks like a normal XBC installer (pictures, etc. etc.)
Package contains:
> kaiEngine, called whatever-you-want - branded with XBC logo - whatever.
> xbcUI.exe - *your* UI - which your users know and love
Now see, this would be nice - your users wouldn't know the difference, they would still get a game list like now, and they would just play.
As to the "advantage" you don't see, well, XBMC, Ava, Linux, WRT, OSX, hella big userbase, lower support load, potential for xbox only engine, no server costs - I could go on..
Point is, there are no *disadvantages* to you, in my opinion.. can you think of any?
TD