Create Xcode Templates

Create Xcode templates to speed up our daywork and automatically create files and folders.

With Xcode we create files and groups everyday. We commonly create files for our classes, storyboards or XIBs. We organize them into folders in order to have a logically organized project. Our preferred IDE offers a number of useful built in templates that we can use to create different types of projects or files.

When we use architectural patterns such as MVVM or VIPER, just to name a few, we find ourselves dealing with numerous files that together define each module: we create a folder for the required module, we create each files we need, probably we create subfolders and put files inside of them and we repeat this time consuming job every time we need to create new modules.

Custom templates

We can create custom templates that tailor our needs and let us speed up our work. With a custom template we can automatically create from scratch groups and files for a new module and add them to our project.

The procedure to create template for Xcode is quite easy. With a little additional work we can also implement a sort of interaction with the user to allow him to make choices.

In this tutorial I will walk you through preparing a custom template for a simple MVVM project architecture.

Let’s start

Xcode keeps its default templates in a dedicated folder that you can find here:

/Applications/ Templates

We can use Terminal or Finder to go directly to this folder. With Finder we can use the Go Menu, then Go to folder option and paste the path above.

Inside we find numerous subfolders and inside of them there are others that have the extension .xctemplate as we can see in the picture below:

Inside we find numerous subfolders and inside of them there are others that have the extension .xctemplate.

If we open an existing project with Xcode, or create a new one, when we go to create a new file, we see a well known window that contains templates of files that we can use to create our projects. The File Templates folder previously opened with finder contains within it further subfolders whose names coincide with the categories shown in the Xcode window, you can find: Source, User Interface, Core Data, Apple Watch and so on.

If you open the folder Source with finder, you can see a certain number of files with extension .xctemplate inside, one for each type of file shown by Xcode in the category with the same name.

Inside Source, we can open the subfolder named Swift File.xctemplate and see a group of files named:

  • __FILEBASENAME__.swift
  • TemplateIcon.png
  • TemplateIcon@2.png
  • TemplateInfo.plist

At first look we can see a file with extension .swift, then we have two images and finally a .plist file.

You have already understood that what we are observing is the template that Xcode uses to create a simple Swift file through the wizard that provides us. If you preview one of the two images you will see that it is exactly the same icon that we have used a thousand times from the window of our IDE.

If we open the __FILEBASENAME__.swift file we can see its very simple content:

Import Foundation

And if we effectively create a new swift file from Xcode we can see this:

// TestXCTemplates
// Created by Davide Fin on 03/03/2029
// Copyright 2020...
Import Foundation

This means that, when we select a template, Xcode uses the corresponding folder, opens the __FILEBASENAME__.swift file that it finds inside and uses text macros to add or replace information. In this simple case it replaces the __FILEHEADER__ text with the common text containing info about the file name, project name, author name, etc.

The file templateInfo.plist contains information about the template:

It is a xml file that contains some important things:

the key Kind with its own particular value that is required for File Templates: Xcode.IDEFoundation.TextSubstituionFileTempalteKind.

We have some descriptive information in Description and Summary Keys:

The name of the swift file that will be used as template in the MainTemplateFile key.

If you open different original Xcode Templates you will see that their contents may differ and contain extra information. The following list of fields enumerates the most common keys you could find, their names are quite simple to understand:

  • Kind (type: string): Because we are creating a “File Template” the value of this key is always: Xcode.IDEKit.TextSubstitutionFileTemplateKind
  • Description (type: string): a brief description of the template file
  • DefaultCompletionName (type: string): the default name of file (without extension).
  • SortOrder (type: number): used to rearrange the order in the container category.
  • Summary (type: string): a brief description of the template file

You can also find these optional fields:

  • Platforms (type: array): the template file will be available for all platforms by default. If we want our template only for one platform we should define something like this (
  • MainTemplateFile (type: string) In case a template has more than one file, MainTemplateFile specifies which file should be opened first after template’s files has been created.
  • DefaultCompletionName (type: string)
  • Options (type: array) determine the options what you can configure in the first step of creating a new File. We will discuss this field later.

Build a new custom template

We can build our custom template in an easy way. I would like to create my own template container and make sure that it is presented on the screen together with the others already present such as Core Data, Source, User Interface etc. Also, I would like to see inside of it all the templates that I am going to create.

So, I can opt to create a container folder where Xcode stores all the others containers:

/Applications/ Templates

and then create inside of it a subfolder with the .xctemplate extension that will host all the required files and and / or subfolders.

But, this isn’t the smartest place to do this job. If we had to update Xcode, the File Templates folder would be deleted and replaced with the consequence that we would lose all our templates.

Instead, we can create our specific folder here:


Again, you can use Finder to reach the folder above but you will see that it does not exists. You can reach ~/Library/Developer/Xcode but the Folder Templates does not exists.

We must create it using Finder or Terminal. Once created we can add our specific container that I will name it: MVVM Templates.

Then, I will create a new subfolder called MVVM.xctemplate inside my container.

The new folder is empty, so if we use Xcode and try to create a file, our container and MVVM template are not listed.

I added to the MVVM.xctemplate folder a set of icons (2x 96x96 and 1x 48x48)

and a TemplateInfo.plist file with this content:

Again, the key Kind with its own particular value is required for File Templates: Xcode.IDEFoundation.TextSubstituionFileTempalteKind.

By default our template will be available for all platforms. We set the value associated to the Platform key to an array with a content:(

Finally we add a key called Options. This key allows us to configure a sort of “Select…” option that will appear in the file creation dialog window of Xcode once we select the template. We can set the type of this option, this means that we can choose the type of control that the user can see on the screen. We can set the type in order to display a TextBox where the user can write something or we can opt for a ComboBox where the user must select a value from a list of predefined items. We added this key because we want to ask the user a string containing the name of the module. We want to use the string to name all the files automatically created by the template. In short, we want that when the user selects our template, Xcode asks him the name of the module, for example: Login. Then we want that the template automatically generates a list of files with classes declared inside named: LoginViewController, LoginViewModel and eventually other files and classes with Login prefix in their filename.

Possible fields inside an Options node are:

  • Identifier (type: string): used to uniquely identify options. You can use it for creating references for using in other options or template file.
  • Default (type: string): selection or text.
  • Description (type: string): brief description of the option. You can see the text when the mouse hovers over it.
  • Name (type: string): Text is shown on the left side of the control.
  • Required (type: bool): determinate is option a required. If a Required option does not have a valid value the Next button on dialog window will be unavailable.
  • SortOrder (type: number): determine the position of option. It is used to change the order in which the options are displayed, otherwise, by default, they are displayed in the order they are entered in the Options array.
  • Type (type: string): of option. Eg checkbox, text, static, combo box, popup.
  • NotPersisted (type: bool): determinate if the value will be saved for the next time.
  • RequiredOptions (type: dictionary): can be used to enable the current option, only if certain values of another option are selected. For example, only enabling a checkbox for some values of another popup option. The key of the dictionary must be the identifier of the other option, and the value of the dictionary must be the array of subset of values from the popup or combo option that allow the current option to be enabled.
  • Values (type: array): using for defining option of combo box.

In our Options node we added an Identifier key with the value productName:

This Identifier key is a very important item that you must add with the value 'productName'. With this key Xcode knows that it is the base name we want to use for the files (and to populate the FILEBASENAME and FILEBASENAMEASIDENTIFIER macro).

Obviously the option that we use to prompt the user for the module name is a required one: we want do disable the next button if the user does not type a string: we have a Required key with value set to true.

We added a key called Name, its value contains a string (“Module:”) that is shown on the left side of the control:

Then we added a descriptive text using the key Description with value “The name of the MVVM Module”.

We added also the type of control, we want a textbox that the user can use to enter the name of the module: the key is Type and its value is text.

Now, all the configuration is ready. If we did everything right, Xcode should now list our container in the window for creating new files, along with the template we have created.

If we try to create a file using our new template you will see that nothing is created. This is because inside our MVVM.xctemplate folder there are no subfolders and / or files to be used as template for generating the module. It is time to create what we need.

With MVVM I like my modules organized in folders and subfolders. If for example I have two modules named respectively Scene1 and Scene2. Inside they both have subfolders for View and ViewModel. Eventually I can have additional subfolders containing specialized files that participate in the functioning of the module.

I want our new MVVM template to create the same subfolder structure and add the necessary files to them.

Go back to Finder in the folder that contains the contents of the MVVM.xctemplate and add 2 subfolders named respectively View and ViewModel.

Now, go back to Xcode. Create a new iOS Single View App project, do the conventional setup (name of the project, company name, etc. etc.).

When you are done, from Xcode create a group called Scenes or Modules in the project. Inside the new group create another one: give it the name Scene1.

Now right click over the Scene1 group and in the contextual menu select the option “New File…”.

Select the new MVVM template.

Type a name for the module, for example Scene.

Finally confirm the destination folder that will host the generated content.

Xcode will create the folders we put in our MVVM.xctemplate item.

Now these new folders are empty, we must add some .swift files inside our MVVM.xctemplate folder. Again, go back to the Finder window that displays the contents of our MVVM.xctemplate.

I will add the required files respectively in their specific subfolder:

Here you can observe the content of our ViewController:

The ViewController above contains some basic initialization for UI and ViewModel. You can see that is very easy to understand. There are lots of comments that the developer should use to remember what he has to do and where he should put things such as outlets, initialization of objects etc.

The most important thing here, is the usage of macros, such as ___FILEHEADER___ that we use to add info about the file and project name, copyright and the author name.

Then, at row 7 where we declare the class name you can find:


See also row number 12, we declared a lazy property that represents our ViewModel. We used the same macro to name it.

This kind of macro above retrieves the string typed by the user in the wizard used to create our MVVM module. We can access that value because in TemplateInfo.plist file we set an Option with an identifier called productName. That value is retrieved as a sort of variable. So, if the user writes Login as the module name, at the end of the process of creating files and folders, Xcode will make the necessary substitutions and the class will be called LoginViewController.

Same thing for the ViewModel below, the class will be named: LoginViewModel.

With patient and small effort you can setup your templates to best fit your needs adding more files and folders such as Protocols, Storyboards or XIBs and or customizing the content of your files.

Complete article

You can read the complete article on Medium available here.


Let’s hack with Location! 😛

This article discusses the use of the iOS CoreBluetooth framework, to detect surrounding devices and calculate an estimated distance. Enjoy the reading. 🤓
April 6, 2020
Get great insight from our expert team.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
By signing up you agree to our Terms & Conditions