Overview of Progress Data Objects, Services, and Catalogs : App development options
  

App development options

Before you can build and test client apps (web or mobile) to access Progress Data Objects using JSDO technology, you must obtain access to one or more Progress Data Object Services, depending on the app development option that you plan to use:
*OpenEdge Data Object Services — Create one or more ABL Business Entities to expose OpenEdge temp-tables and ProDataSets as Data Object resources in an OpenEdge Data Object Service. Then, create the Data Object Service to generate and deploy a Data Service Catalog for these Data Object resources. For more information on creating ABL Business Entities to implement Data Objects, see the sections on Data Object Services in OpenEdge Development: Web Services.
For information on creating and deploying Data Object Services to OpenEdge application servers and accessing the Data Service Catalog for a given Data Object Service, see the topics on Data Objects and Data Object Services in the Progress Developer Studio for OpenEdge Online Help.
*Rollbase Data Object Services — Generate a Data Service Catalog with selected Rollbase objects as its Data Object resources. For more information on generating a Data Service Catalog to access Rollbase data from the Telerik Platform, see the Rollbase documentation topic, Creating Progress Data Catalogs for use in the Telerik Platform.
The current release of Progress Data Objects support two options for developing mobile and web apps with access to Progress Data Object Services.
* Progress Kendo UI support
* NativeScript support
* Other UI support