Well, the start pages states "Vector maps from OpenStreetMap" 3 times. Technically it is up to app developer to add proper attribution, as our SDK can be used with other sources also. OSM is provided just for convenience. But point taken, I'll add reminder about attribution requirements to the developer guides also.
The developer portal at https://developer.nutiteq.com mentions OpenStreetMap, but the start and product pages doesn't. No link either. Perhaps you provide more sources, I haven't looked into the product very carefully. Your support told me OSM is used as map data source, didn't mention any other source. My understanding of the OSM license agreement is that you have to make it more explicit. But I'm no lawyer.
Sure, I'm daily OpenStreetMapper myself. The other map options can be added in project basis, as the geodata from any other sources tends to be extremely expensive for average end-user app developers. Of course it has to be attributed properly in each app.
This has been asked quite a lot, but HTML5/WebGL approach would require another complete rewrite. One of our key advantages: showing maps without network would not really work there, but this could be resolved with a storage-enabled wrapper like Cordova. We have even thought about making native plugin for Cordova, then existing code (with fast performance etc) would work.
TL;DR: is for more demanding app requirements.
For end-user apps: offline maps support. Google Maps has it as app (and not everywhere), we provide SDK where it works globally. For more demanding needs you can add 3D objects to map, use it for HUD navigation (Google terms prohibit it), use completely own/custom base map etc. See https://www.nutiteq.com/nutiteq-sdk/comparison/ for more more differences and similarities
http://wiki.openstreetmap.org/wiki/Legal_FAQ#3a._I_would_lik...