@viv first thanks for taking the time to answer - it certainly does help 
and I’ve updated the FAQ to where I think we are. Let me know if I need to change anything or feel free to edit it (as it is now a wiki post).
I have more questions but if you need to leave this aside for the time being no worries, we can pick it up later and leave these as place holders for how:
-
I’m wondering now if what I’ve written is pretty much it for the time being, or if there is an intention to provide a more extensive and stable/recommended API, that handles more than the simple RESTful style operations? Particularly what may or may not be planned in terms of NoSQL (e.g. Redis style) support, but also, for other areas.
-
Obviously an App could make use of any part of the MaidSafe libraries, but it will be helpful for App developers to be pointed to the most relevant areas of code, and guided to stable App interfaces, and have potentially unstable inter-library interfaces hidden away (or documented separately). Do you think this can be done within the source code documentation?
That’ll do for now I think! I can’t wait to see that full sample code SAFE App I’ve committed you to delivering 
Want!