Mobile app creation - App Engine studio vs Global app creator

[PaulSylo]

Hello All,

When you are about to start your mobile app creation it is very common to come to end up in to use which functionality to create the app, whether it is on App Engine Studio (AES) or Global App Creator ( GAC). When I am stuck with this question, Servicenow documents/learning materials explain this clearly. I have taken those references and given them here as quick comparisons between both functionalities.

Features within the mobile app	App engine Studio	Global App Creator
Launcher screens	Launcher screens are created as part of an experience and are a vertically-oriented icon section with a feed count. This uses the name set for the Experience.	In GAC, Launcher screens are created with the same name as the application and are a horizontally-oriented icon section. The name of the data item matches the application name.
Data Items	Data Items are created for each list screen created, and conditions can be set to control the returned records. The name is the one set for the screen.	There is a data item for each table selected, but all records are returned. The name of the data item matches the application name with the table name appended.
Screen(s) and necessary card(s) and icon(s)	a list screen with a record screen or a mobile web screen depending on the selection made. The number of screens depends on the configuration, and the name is the name set for the screen.	a list screen and record screen is created for each table selected and named according to the table. It uses the data item with the same table appended and is named according to the table.
Functions - New, Edit, Delete	All three functions are created for each table or screen configured with the table name or screen name in parentheses. However, despite creating similar initial records, there are some differences of which to be aware.	all created elements use the same naming convention of the names of the tables, which often need to be updated and are not necessarily valuable or concise.
Base configuration	With AES, the initial configuration can be added to Mobile Agent, Now Mobile, or both.	With GAC, it is always added to Mobile Agent, which means that edits must be made to add and delete the configuration to and from the apps if a different assignment is desired.
Screens	With AES, either a list screen or a mobile web screen can be selected.	With GAC, the first screen created is always a list screen.
Conditions	conditions can be set for the data item(s) in AES	No conditions are set and it will return all records
Table Usage	With AES, each table selection needs to be done via a screen creation within the Experience, but due to filtering, the same table could be used multiple times with different conditions set.	With GAC, multiple tables can be selected at once, but only one screen is created for each table. but GAC has the option to create an application in the global scope rather than a new scope.

In rare cases, it might make sense to use Global app creator instead of AES (e.g., creating the application in the Global scope is needed), but in most cases, App Engine studio is preferred, and Global app creator should only be used if the organization does not have App Engine studio.

Pls, feel free to add your thoughts and points, and let's make this collaboratively useful for others.

[Munipalli Kiran]

very useful info 

[Troy Dewant]

Choosing between App Engine Studio (AES) and Global App Creator (GAC) for mobile app creation can be a crucial decision. It's great that you've provided a quick comparison of their features, which can help others facing the same choice. For those who might need further guidance on mobile app development or optimizing their apps, Radaso Agency could be a valuable resource. They specialize in app store optimization (ASO) and might offer insights to enhance app visibility and performance. Thanks for sharing your insights, and I hope it helps others make informed decisions on their app development journey.