Jules, might you consider creating a Juce wiki? This would provide a structure that would allow the community to document this technology, and help future beginners.
It looks like Juce is the only way forward for me, and once I get comfortable on this framework I will never need to switch again.
But the initial learning curve is steep, and I am really floundering, as I always flounder with a new technology.
I've been writing my own musical training software for five years, which has taken me through iOS (Accelerate framework, GLES2, CoreAnimation, etc), Unity3d (C#/.NET), Blender (Python), autotools, etc, and have come to recognise the pattern of having to punch through a number of brick walls in order to get any technology working. Each stumbling block can take days or weeks to surmount, involving forum posts, subscribing to obscure mailing lists, filing bug reports, etc.
I am amazed at the incredible amount of work you have put into this engine, that one person could have punched through so many brick walls.
I have just spent a whole day getting nowhere, trying to build on android. Once I understand the process I'm sure it will fit into place and seem so simple and obvious that I will wonder how I could have been so stupid. And I will straightaway run into another brick wall.
If there were some wiki, I would gladly contribute as I learn, and I think others will also. Forum posts could direct to appropriate points on the wiki, and knowledge could be organised and kept current more easily.