What is the main difference between Studio, App Engine Studio and UI Builder?

[Kenneth3]

Hi All,

With the release of Quebec, we have new tools like App Engine Studio and UI Builder.

I am a little bit confused which tool I can use best for developping a simple App (in my case this is a simple dashboard App that have to be available in the ServiceNow Store).

I am able to build this in Studio, but with this new tools, is it not better to use these? Will Studio slowly disappears?

Hope somebody can clarify this for me.

Thanks,

Kenneth

[Prasad Pagar]

Hi,

Application studio is BEST to develop custom application. ServiceNow recommends to use Application Studio over native UI to develop any custom application.

Thank you
Prasad

[DirkRedeker · Accepted solution]

Hi

All of these tools works hand-in-hand. They do not exclude each other and you can / need to use the tools depending on your need and level of no-code / low-code / procode.

AppEngine Studio (AES) is the new No-Code /Low-Code starting point for citizen developers, which helps easily to jump-start creating new applications. There is a growing number of application templates, you can leverage to build your own custom solutions on.

The resulting artifacts, created during / with AES are also accessible and changeable through ServiceNow Studio, as each new App will be located in it's own Application scope.

It is recommended to get as far as possible with AES, but you surely can continue to extend your custom applications with Studio.

So, for more advanced pro-code development, you may (today) need to switch from AES to Studio.

I never have heard, that Studio will disappear and will be replaced by AES. As said above, AES is the one-stop shop for citizen developers, to grow into application development.

Take a look at it, it is a GREAT extension to ServiceNow!

UI Builder is just the designer tool for the new UI Experience, which was first used in Agent Workspace and now is opened more and more to the public for development. With Quebec, the UI Builder now ships with a huge number of components OOB, which you can use to build your custom workspaces.

Workspaces may, but do not need to replace the Service Portal experience in ServiceNow.

It is just the next gen environment, with a fresh new environment for building your (customer and internally facing) custom UIs. UI Builder is a great new tools, and you also can create your own custom UI Experience Components to be used IN UI Builder.

So, just like designing Classic UI Pages with UI Designer, or Service Portsl Pages with the Portal Editor, you will use the UI Builder to create and manage you New Workspace like UI Experience Pages/Sites. 

In this way, UI Builder adds as a new tool to ServiceNow and does NOT replace any existing tool.

If you are interested in how to jump start building your own UIX Components, you can have a look at my article following the link below:

Article #11 - Fast Track to your first "Now Experience UI Framework Component"

Let me know if that answers your question and mark my answer as correct and helpful.

Have fun building on ServiceNow and

BR

Dirk

[Kenneth3]

Thank you Dirk for your elaborated answer. Much appreciated!

[DirkRedeker]

You are very welcome! Thanks for your feedback.

BR

Dirk