Regarding the firewall, the FAQ includes a pictured step-by-step How- 
To on how to configure the Leopard and Tiger firewall correctly 
respectively.

With the current implementation of the firewall in Leopard, I lack to 
see a real use for the average user in activating it while at the same 
time, it can cause many non-obvious problems for unexperienced users 
due to the way it interacts with code signing. Code signing can be a 
security plus, but also cause unwanted side effects if a user breaks 
the signing of an app - which is easy enough. For copies of apps whose 
code signing has been broken, the Leopard firewall will still display 
the app in its list of exceptions, but not apply them. The 
consequences: the configuration seems correct, yet the firewall will 
behave differently and the app in question can no longer accept 
ingoing connections. Only removing the app's entry, deleting the copy 
of the .app bundle, reinstalling a fresh, unaltered copy of the .app 
bundle in question (with code signing intact), then readding it to the 
list of exceptions will make the Leopard firewall do what it says it 
does in System Preferences.

Regarding the FAQ entries on typical network issues - although not a 
task or part of Remote Buddy - the most common ones as well as some 
special ones are covered there, too: from setting up your Mac-hosted 
WiFi network to solving problems with neighbouring WiFi networks using 
the same channel all the way through to diagnosing packet drops, 
determining the reliability of your WiFi network, documenting general 
WiFi driver problems in OS releases prior to 10.5.2 when using 
802.11n, descriptions on how to select a different 802.11 standard, 
listing sources of interference (including concurrent use of 
Bluetooth), etc, etc.

None of this is caused by or under control of Remote Buddy. Remote 
Buddy is not a network setup or debugging utility. It merely utilizes 
existing TCP/IP networks (be it Ethernet, IP-over-Firewire, WiFi, VPNs 
or anything else that transports your Mac's TCP/IP traffic) like any 
other network software. It doesn't differ from FireFox, Safari or - if 
you so want - ping in that regard.

Since neither network setup, nor TCP/IP stack, nor Firewall, nor WiFi 
drivers nor WiFi hardware are part of Remote Buddy or its feature set, 
IOSPIRIT's support is (just like the makers of f.ex. FireFox) also not 
the right adressee regarding problems and questions with these.

The right adressees for those are the makers of the respective 
components - which typically are Apple / AppleCare and/or the sellers 
or makers of the hardware in use.

Regarding speed: you need to differentiate between the speed of Remote 
Buddy - and the speed of the device that renders the delivered 
content. Remote Buddy itself is lightning fast (just use the AJAX 
Remote in Safari on your Mac via http://localhost:8888/ to see 
yourself).

The rendering of the web interface in the iPhone's web browser, on the 
other hand, can never be at the speed of a desktop client. The more 
functionality you offer through it, the more compact you offer it and 
the more graphical gems (especially transparency and transitions) you 
add, the more CPU time will of course be needed. Yet I find that AJAX 
Remote balance performance and visual appearance very well and is 
highly usable even with bigger libraries.

That said, we can expect speed to automatically further (and vastly) 
improve in the future - the team working on WebKit (Safari's rendering 
engine) is apparantly hard at work to deliver much better performance 
with future releases:

http://webkit.org/blog/189/announcing-squirrelfish/

Best regards, 
Felix Schwarz