Well, it's not just a matter of making or porting software, it's also a matter of decided what route to go with for a hardware bridge.
Thinking in a more complicated environment such as mine, where I may start moving video, audio and data down cat5 cabling, coupled with wifi, now I got more potential crud on the line, which means I should get a Layer 3 switch and use a lot of filtering and subnetting to keep traffic where it needs to be and not where it shouldn't be. It won't save me on cabling, but it will ensure only key bits of data cross subnets when and where absolutely necessary.
Connecting an iPhone or an Android, which way do we go? Cabled? Sure, I suppose, but it would be cool to be wireless so you can walk around and change scenes if you want to. So, how do we handle this? Do we do a dedicated wireless box that includes the 802.11a/b/g/n into it with an antenna, Cat5 and DMX out? Do we made it without the wireless and require you to provide the wifi connectivity? Do we encrypt the data or use some other method of security? I mean, MAC address security is certainly low-end, but it does let you avoid having to encrypt, which keeps your speeds up. And at the same time, how much security do you want to cram in there? How many MAC addresses do you want to support?
OH, I don't think that your idea is bad. No, far from it. But, we have to look at the market for MyDMX and the original design. Even adding a VLC plug-in module would break the MyDMX design objective, but would allow the best option for DMX bridging from a wireless device.
Now, I could certainly see the time and effort being integrated into CompuWare products. Not MyDMX though.
Then you have the last bit of problems: If you go iPhone, you have to get Apple's "blessing", or at least you do if you want to go through Apple's iTunes store. I'm not familiar with Android, but as much as I like Apple, sometimes things Apple does annoys me, so chances are the Android marketplace doesn't have this "overseer" element. But, coupled to that, you have the whole issue of "Well, if you do this, why don't you do that?", as in if you support Android, why not iPhone or vice versa.
But seriously, this is a valid idea that may already be done. But I see it as a viable option for those willing to pay for it(sorry, I'm thinking marketing and value add-on upgrades) via the CompuWare products. It's not soemthing I would want to pay for if it's something I have no intention of using, but if I think it's something I personally would find handy in my environment, then yes, I'd fork over the money for it. And would I? Well, yes, I would. First I'm moving in an area where MyDMX won't be leaving, but I am needing more capability, so Jingles has been talking to me about the correct Compu product I need to start giving serious consideration to, and as such, I'm trying to allocate budget to. It's going to happen, that is what I will say. I also have an iPhone and I like my iPhone. When my contract goes up in December, I'm going to get the new iPhone as well. While I don't see needing a remote feature as a Day 1 thing for my new Compu software, it would be something I would spring for if there is an iPhone and/or Android option, because I may have someone else need to run my lights, and I want the option, even if I personally won't use it right away.
And while we're at it, best to include the Ipad and iPodTouch to the list as well. Those are going to be viable options. If Apple is more generous about the integration of Java into some of their products, it could create an open platform for developers to tap into.
My choice? Along with the paid feature, I'd like to see an included set of apps made by the same company for the correct platform I choose to use.
So, yes, great idea. Definately something that if not being explored, should be. But not something for MyDMX. I think this is an area that ADJ or Elation should maybe give some thought to.