Hi Paul,

There is certainly no problem in using Kentico as your data storage (or whatever you are going to use Kentico for) and then exposing this data using a web service call from your app. You can create a web service as you would do normally in .NET inside your Kentico project or If you want basic access to data then you can use the built in kentico Rest API (have a look at version 7 documentation).

If you are going to create your own web service I would strongly recommend creating a new JSon object to return from your web service and then using this in your application.

In essence the example from a Kentico point of view would be to either use the REST API interface or if you want something more complex/manipulate the data before you expose it then write your own web service and use the standard kentico API to return the data objects (I would recommend returning as JSon).

I've done something similair here in a blog post, however this is calling it from within the kentico website rather than from a 3rd party app but would give you the example of return a JSon typed object.

http://www.netconstruct.co.uk/matt-swain/may-2013/kentico-%E2%80%93-web-service-class/

Any questions just shout,

Thanks,

Matt