---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Exploring Creator Studio

# Exploring Creator Studio {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Creator Studio makes creating apps easier by dividing their creation into simple steps. In this section, we'll explain each one.
All the steps involve requests. So, we'll start by explaining how Creator Studio stores requests.  
Summary:  
After reading this section, you'll understand:

* How requests are stored
* How people enter requests
* How your app automatically does things
{#exploring-creator-studio__ul_ebx_2mf_s1c}

## Let's talk about storing requests {#exploring-creator-studio__section_zh1_gmf_s1c}

When people make a request, we have to store it somewhere so someone can review it later.

**Tables hold requests**

Creator Studio stores requests in a table. Each row in that table is a request. Here's a simplified version of a table with three requests.  
Use cases:  
* My monitor stopped working. I need a new one.
* I'm requesting a new mouse so I can have one at home and in the office.
* My laptop is over four years old. I want to request a replacement.
{#exploring-creator-studio__ul_ttx_cn3_t1c}

**People enter requests using forms**

How do people enter requests that eventually get stored in the app's table? They use your app to fill out a form. The questions on the form contain the information your fulfiller needs.

In our app's table, questions are stored as part of the [record](https://servicenow-prod.fluidtopics.net/nliD8WmMVPd9fJnZiLDpOw#gloss-record-creator-studio "A task or request that needs to be acted on. All rows in that table for an app are individual records. Records have different states depending on what actions have been taken."), which is composed of all the information on the form.  
{#exploring-creator-studio__table_edj_dl1_2bc__entry__4}

| Request | Name | Email | Request date |
|-|-|-|-|
| I need a new monitor. | Sushma Singh | SushmaSingh@example.com | 04-05-2024 |
| I need a new laptop. | Peter Smith | PeterSmith@example.com | 05-01-2024 |
[ ]

{#exploring-creator-studio__table_edj_dl1_2bc}  
In this example, the form has four fields:

* Request
* Requester's name
* Requester's email address
* Request date
{#exploring-creator-studio__ul_ovv_ddg_s1c}

These fields contain all the info the reviewer needs to accept or reject the request. You'll have to figure out all the information your reviewer needs to make a decision.
Later, we'll show you how to create a form (using Now Assist or on your own) in the section [Working with forms in Creator Studio](https://servicenow-prod.fluidtopics.net/MnEjqHT4MYv1XEBrspUPqQ "To add items or services to your catalog, you must create a different form for each thing being requested.").  
Key terms:  

Requester
:   Someone requesting something, like a piece of equipment or permission to do something.

Fulfiller
:   Someone who works on requests. Fulfillers may also approve or deny requests, depending on any approval automation for the app.

Okay, now you understand that requesters fill out forms to create requests and Creator Studio stores those requests in the app's table.

## Try Creator Studio on a PDI {#exploring-creator-studio__section_sdh_bvw_qbc}

Want to play with Creator Studio on your Personal Development Instance (PDI)? It comes automatically installed from the Application Manager on your PDI. For more information, see [Personal developer instance guide](https://servicenow-prod.fluidtopics.net/TmG3_ztSX8DFW~U7YVT~wQ "ServiceNow offers free personal developer instances (PDIs) to Developer Program members to learn, explore, and experiment with the ServiceNow AI Platform.").
* **[Example apps you can build in Creator Studio](https://servicenow-prod.fluidtopics.net/al18DXmAYGNPYGDiJEs11g)**   
  Creator Studio enables you to build apps where people can make requests.
* **[Use App Engine instead of customization](https://servicenow-prod.fluidtopics.net/wBOxV_qTsrvURZbbG_SXKA)**   
  App Engine development tools, such as Creator Studio, offer an excellent alternative to customizing existing applications on the ServiceNow AI Platform.
* **[Customization vs. configuration with Creator Studio](https://servicenow-prod.fluidtopics.net/inYng1sY1hTRneSzixTCfw)**   
  There are important differences between customizing and configuring ServiceNow applications. The ServiceNow platform is built to embrace customization and configuration but how you do so can have significant impacts on ServiceNow support, upgrading to future ServiceNow platform versions, and the functionality of the ServiceNow platform.
* **[Creating your first app with Creator Studio](https://servicenow-prod.fluidtopics.net/pSqXLocmrpwc3K5SBn5H2Q)**   
  Creator Studio helps you create your app by dividing it into smaller parts. Each does something special, and you work on them sequentially.
* **[Creator Studio quick start](https://servicenow-prod.fluidtopics.net/GfiYnfaWwnh9_malCVlLnw#creator-studio-quick-start)**   
  This quick start guides you through the process of building your first app in Creator Studio and requesting its deployment.
* **[Get help with Creator Studio](https://servicenow-prod.fluidtopics.net/TrvTXwVzabi5ZE8fgTJg4w)**   
  To get help with Creator Studio, your ServiceNow instance, plugins, permissions, and more, watch a short video to contact the ServiceNow admin who works in your company.
* **[Choosing your development experience](https://servicenow-prod.fluidtopics.net/GKORITTVWed0xD_eH1ZN_A)**   
  If you want to develop apps in a more robust environment than Creator Studio, which was designed for no-code developers, you can select a different experience directly from within Creator Studio.
* **[Service desks and Creator Studio](https://servicenow-prod.fluidtopics.net/p3XONbNuhkQERay2uqYDrw)**   
  Service desk apps enable users to request things, such as IT equipment or travel bookings, and track their fulfillment.
* **[Migrating to Creator Studio from Service Creator](https://servicenow-prod.fluidtopics.net/Ujdv0QCOnM0aI3Ox9hxvfA)**   
  Creator Studio is replacing the older Service Creator tool, which will be retired in the Australia release.
* **[App compatibility with Creator Studio](https://servicenow-prod.fluidtopics.net/kM3omd7ecanad2TxomznFw)**   
  You can open apps built in Creator Studio in other ServiceNow products, but only apps built in Creator Studio can be opened in Creator Studio.
* **[Creator Studio apps and tables](https://servicenow-prod.fluidtopics.net/ObYNhnlzpQDSst5UZg6jNQ)**   
  Creator Studio uses catalog templates to streamline the app creation process. Apps use the Request Task table by default, generating a new row for each submitted request, though admins can change the underlying table for an app.
* **[Publishing, activation, and deployment workflow for forms, automation, and apps](https://servicenow-prod.fluidtopics.net/vLCI6rSY3zGFKy2hLxjzVw)**   
  When you build an app in Creator Studio, you must create forms and automation. You can also customize the workspace list configurations and records that fulfillers use before everything is deployed to production.

