My recommendation is C# web service using the .NET DataStore, which makes developing the C# web service like PowerBuilder development. 

If there is any existing business logic from your PowerBuilder app you want to convert, you can use the PowerScript Migrator to automatically convert that to the C# web service.

The advantage of using C# Web service as the back-end is so you can share the same business logic across multiple UI technologies.  Also, this leaves room for changing business/technical requirements in the future, for example you want to change the UI technology used or open up the business logic to external systems for integration.

If you want a mobile application then you have to build an application.  If not PS mobile, then some other application dev tool that builds the front end.

The webservice is just where some logic is.  sort of like a database stored procedure - you still need a front end to run it.

I agree with Armeen's recommendation: a C# web api and a light-weight platform-independent UI.

The Web API will be your long term investment, and you can reuse it from now on. With the new 2019R2 scaffolding feature, you will create the API in virtually zero time, and using a technology that you know perfectly (based on .Net DataStore).

Once you have the Web API, you are free to create whatever front-end suits your needs. We usually recommend (with PB Open) a React/Redux front-end, but basically you can choose whatever you like (we follow in this sense customers' preference). If, as Armeen suggests, you use a responsive HTML-based client, you will be able to run this application everywhere, with no deployment. If you will need one day a Native application (that is much more expensive to build, but that is also more feature-rich), you will still be using your Web API.

Good luck with your new app!

Armeen

Brand new app so no legacy code :) (in this project :) )

- I'm defo not a mobile app developer :) - Tried a simple helloworld-app on PowerServer2017 

So for the mobile development - which direction  ? 

Regards

Georgios

Hej Georgios,

I suggest follow Mike S' advice. He has experience with both PB and PowerServer.

No matter what you write server-side you still need to create a mobile front-end.
That's where PB + PS Mobile provides a "full-stack environment".

Your PB Universal (now PB CloudPro) also includes SnapDevelop for C#/.NET development. Incl. PowerScript => C# Migration. But writing great C# code takes practice. It may be favorable to choose PowerScript and DataWindow technology for both front-end, back-end, data persistence, and interoperability with external apps. It really depends on context.

Held og lykke! /Michael

thx for comment

I guess i'll try the PowerServer - as i can't see me going c# shift atm - as i said very simple mobile app (and very little BL) 

I'm a bit confused - and worried  

Is PowerServer Mobile going to deprecated ?

Regards

Georgios

Yes Michael :) 

I guess that will be the "hard work" in succeeding of migrating from PowerScript to c# 

Still have my doubts on this strategic approach :)

/georgios