Sounds like you're trying to use Reveal to inspect third-party apps on a jailbroken device. This use case is not officially supported by Reveal, and I'm afraid we don't provide technical support for issues related to this. However, the issue you're describing doesn't seem to be related to Reveal itself. You probably need to check that your device is jailbroken and you have unlocked the correct file permissions to modify the file system of your device.
Please note that Peter Steinberger's article is back from 2013, and it describes using Reveal v.1.x, while the current version of Reveal that we sell and maintain is Reveal v.7. There may be some incompatibilities in using Reveal v.2 and newer when attempting to use it for inspecting third-party apps. So if you'd like to try Reveal 1.6.3 instead, you can download it from here. A free trial is included. If you believe you need a license for Reveal 1.6.3, we can downgrade your Reveal 2+ license.
I am using 1.6.3, but the iphone doesn't appear in the "File>Connect to" list.
My question in other words could be: Does getting RevealServer.framework to /System/Library/Frameworks allow the Reveal app to inspect apps on iOS 10?
In order to use Reveal 1.6.3 to inspect an already compiled app, the dynamic library of Reveal Server (libReveal.dylib) must be loaded by that app. The ways this is achieved to inspect third-party apps are up to you, though. Peter Steinberger's article mentions copying libReveal.dylib onto the device, which seems to be the main requirement. I don't actually know why it also mentions copying RevealServer.framework, since in Reveal 1.6.3 RevealServer.framework is not a "real" framework and can only be linked statically during the build process. So I don't think that dropping that "framework" onto the device should be necessary or would work on itself.