Purpose of the IOSDeviceLib's interface

If we would like to state the following:

• "The node code is there to be able to act as a proxy between the spawned process and the rest of the code"
  If this is true.. functions like upload,download, postNotifications should not be defined in the javascript code.

• "The node code should serve as both proxy and api to be used from applications"
  If this is true... named functions are a nice idea.
  What seems wrong is the fact that currently the only ways to find what to pass in the uploadArray, downloadArray or postNotificationArray are to take a look at the mobile-cli-lib or go to the native code to see how we are parsing the array.

It seems the purpose of IOSDeviceLib's interface is not clear enough with the current implementation.
Please correct me if I don't understand correctly.

Beginne mit dem Vergleich der JavaScript-Schnittstelle mit der Verwendung von mobile-cli-lib und dem nativen Code, der uploadArray, downloadArray und postNotificationArray verarbeitet. Kläre, ob IOSDeviceLib als Proxy oder als anwendungsseitige API gedacht ist, und definiere anschließend die erforderlichen Schnittstellenänderungen, um diesen Zweck und die akzeptierten Argumente ausdrücklich festzulegen.