App Settings
Last updated
Was this helpful?
Last updated
Was this helpful?
App settings is where you configure and customize various aspects of your app. It is organized into the following sections:
To view or change your app settings:
On your project's Design tab, click the gear icon in the left sidebar.
This describes your app and how you intend it to be used. While it is unnecessary to fill this out in Thunkable, if you publish your app, you must enter this information on Thunkable, the Apple App Store or the Google Play Store.
The app name is the public name you choose for your app. It is what is displayed on the Google Play Store or Apple App Store and that users see when they install your app on their device. This name is also used to set the page title when you .
The best practice is to select a short one or two-word app name. The maximum length of an app name is 30 characters.
The app name is different from the project name, which is displayed at the top of your project. While the project name is Thunkable-specific and may include details specific to your team, the app name is user-facing.
The best practice is to set your project's default app layout before you add components to your app screens. If you add components to your app screens and then change your project's default app layout, your designs will not automatically respond to the new size and layout, meaning that neither the size of your existing components nor the distance between components will change.
Use the dropdown menu to select your app's default layout. The options are:
Phone + Portrait
Phone + Landscape
Tablet + Portrait
Tablet + Landscape
Your app icon is the image that represents your app on your users' mobile devices. This icon will also appear on your listing in the Google Play Store or Apple App Store and as your project icon on Thunkable.
Ensure the file you upload does not have the same name as another asset used in your app. This will result in an error.
Size
192 x 192 px (minimum)
Shape
Square (equal height and width)
File Type
Preferably .png (vs. jpg or other file types)
To access your app's splash screen image settings:
Navigate to the project’s Design tab.
Click the Settings icon in the left sidebar.
Click the ellipsis icon at the bottom of the Project Settings section to access the advanced settings.
To customize your app’s splash screen picture:
Click in the Picture field.
Click Upload files and select an image from your computer, or select an image from your app’s current assets.
Splash Screen Picture Requirements:
The picture must be square. Rectangle pictures will not render correctly.
The ideal dimensions for your splash screen picture are 1152x1152 pixels.
If you want a transparent background, a PNG file is recommended.
To customize the background color of your app’s splash screen:
Click in the Background Color field.
Use the color picker or input the HEX or RBGA codes to select your preferred color.
The maximum length is 155 characters.
It must have at least two segments (one or more dots) - ex. com.domain.creatorname.appname
Each segment must start with a letter (i.e. none of the segments can begin with a number).
All characters must be alphanumeric or an underscore.
A character cannot have an accent (e vs ë).
If this switch is set to true, Thunkable will automatically remove all unused fonts from your built app. Removing unused fonts will reduce the overall size of your app for downloading and/or publishing. Only fonts set in the design tab will be kept. Fonts set by blocks will also be removed.
If this switch is set to true, the sound will keep playing even when the app is minimized.
In app development, the "notch area" refers to the space on the screen of a mobile device where the front-facing camera, sensors, and sometimes the speaker are located. By default, Thunkable adds the notched-out safe area at the top of the screen, resulting in a non-rectangular display shape.
If you set the Ignore Notch Area property to true, the screen background color will extend to fill the screen. However, if you do this, to avoid your app elements being blocked by the notch, you must manually address this in your app design.
By default, the notch area background color is white. You can change this color here if you wish, however. This is an app-level setting, and you won’t be able to customize the color at the screen level.
When you add components that require permissions to your app, like the camera or map, you must add purpose strings for any relevant component in your app if you want to publish it to the App Store.
This feature may only be available for Creators on certain Thunkable plans. Please refer to our for more information.
This feature may only be available for Creators on certain Thunkable plans. Please refer to our for more information.
For publishing to the iOS , you will also need an app icon that does not have any transparency, or it may cause an error.
For publishing your app to the Google Play and Apple App Stores, you will need to create a separate icon with a higher resolution. For , the current requirement is 500 x 500 px. For the , it's 1024 x 1024 px.
This is a unique identifier for your app on the or . This field is auto-populated upon project creation, but if you choose to modify it, please ensure you follow the requirements below.
Creators on certain Thunkable plans can set their app to private. A private app will not be displayed in the Thunkable Public Gallery. Learn more about public and private apps here: and more about our Thunkable plans here: .
When you publish to the or the , you must increment (increase) your version number each time. If this switch is set to true, Thunkable will automatically increment your project's version number each time you publish your app (iOS) or download your app (Android).
Set a for this version of your Android app.
Set a for this version of your Android app.
Set a for this version of your iOS app.
If your app or any external service your app interacts with is gathering any type of identifiable information, this must be explicitly disclosed to the end user of your app using an in-app prompt. If you do not include this and your app engages in tracking, Apple will reject your submission and ask you to resubmit while including an appropriate tracking string. To learn more about when to include a tracking string,
If your app uses , , , or requires users to , you can enter your personal API keys for these integrations in the app settings.
To learn more about the Firebase integration, please see here: .
To learn more about the Google OAuth integration, please see here: .
To learn more about the Google Map integration, please see here: .
Enter the AdMob app ID for your iOS and/or Android app. To learn more, see here: .
Import and export an Android Keystore to/from your app. Learn more about the Android Keystore here: .
To learn more about the Cloudinary integration, please see here: .
