I'm aware of the fact that Bluetooth and Wi-Fi use the same frequency. However, it is widely accepted that the two do not interfere with each other in any noticeable fashion. This is not true of cordless phones or microwaves (which also operate in the 2.4 GHz range), which can cause problems with Wi-Fi.

This is not a matter of interference. This appears to be an issue with the Bluetooth drivers in MacOS X "shutting down" Wi-Fi access while Bluetooth is actively seeking Bluetooth devices. During the passive scan that OS X performs to check for already paired devices, this is not an issue. However, the first time a device is paired, OS X will search far more diligently for devices and disable Wi-Fi during the process.

RemoteBuddy, on the other hand, ALWAYS shuts down Wi-Fi because it is constantly searching for new devices. You are correct that the only way to find new devices is to always look for remote controls at all times. One drawback to this is that Wi-Fi networking is effectively eliminated during this process.

What I propose is this:

In future updates to RemoteBuddy, add a feature that either disables "active Bluetooth searching" after a set period of time, or is toggled on and off with a keystroke. Obviously, I can disable the Remote searching at any time, but once I do that, the remotes that are already connected are immediately disconnected.

Therefore, if I want to use RemoteBuddy and a Wii remote to say, browse the Internet, I won't be able to do so over Wi-Fi as the two cannot coexist at the same time in the current implementation of Bluetooth handling that RemoteBuddy is doing.

You are correct that one size never fits all. I love this program and I use it all the time for controlling music and video, but I would love to be able to use it for far more than that one day. I hope that some of these features could one day make their way into RemoteBuddy, even if only as options and not defaults.