> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/wemmodeler/project-settings/mobile-app-settings.md).
# Mobile App Settings
{% hint style="info" %}
[This forum document](https://my.wem.io/filestore/si/1026519/34/1049521/Characteristics%20of%20a%20Native%20Mobile%20App%20project%20in%20WEM.pdf?etag=c1069d555ab2234d1485c9fec75f90d0) has useful information and some characteristics of a native mobile app.
{% endhint %}
### Basic configurations
The WEM modeler supports creating apps for both android and IOS. Making an app in WEM works just like an Web app, with a few different settings and different portals. When creating an app you first give your project a name and select the App as project type, after that you get the localization settings just like with a Web app.
### Portal settings
The portal settings are the different for Apps. Instead of one default portal, you start with an Android and an IOS portal which each have their own settings. As with web application settings, the portal actions can be found in the top right corner of the portal settings canvas.
The first one portal action is "Basic settings" for both Android and IOS portals. This allows you to change the portal name and the homepage of the portal. Thereafter, you have the android app settings and the IOS app settings. Here you fill in the Application ID setting, the version setting and the Permissions the app requires.
Both portals have an app icon setting. For Android, a simple PNG picture of your preferred icon sufficient. However, for the IOS icon setting multiple files are required for different sizes of the icon. To add these icons click on the icon size you want to change and a pop up will let you select the file. In the image below you can see the required logo sized marked in yellow.
The app splash screen is the image that appears when you start up the app. This is a temporary loading screen and does not have any content. You can upload a PNG and choose the background color with hex color codes for both portals.
For now we have one master template per portal (for Android and IOS) with each their own design configuration. Just like web apps you can choose your own design, or a design from the WEM library and personalize it in the design configurations.
### Security settings and certificates
Certificates for works a bit different with mobile apps.
To be able to deploy an Apple app you need to create Apple specific certificates and a provisioning profiles in the developer portal of Apple. In [this document](https://my.wem.io/filestore/si/1026519/34/1049521/Characteristics%20of%20a%20Native%20Mobile%20App%20project%20in%20WEM.pdf?etag=c1069d555ab2234d1485c9fec75f90d0), you will find a small guide on how to get your IOS app to distribution.
You can only manage your certificates in the security settings not in the web service tab. Mobile apps only support consuming webservices so you will only find those under the webservice tab.
### Project Configuration and security settings
Project variables work just like the web app and allows you to add variables per portal. When you add a variable, the first column represents the android portal and the second one the IOS portal.
The project configuration tab is also where you can configure the languages which your project supports. When you select the languages settings a pop up appears. There you can find the available languages and add more languages to your project.
The Storage strategy allows you to define the database strategy. That is, either all portals use the same database, or each portal has its own database. This setting cannot be changed after the project has been published.
Processes settings for the mobile app is similar to the web app processes settings, and allows you to find process nodes by searching on a process.
Different from the web app project configuration is the absence of Google Analytics, and Query string configuration in the mobile app project settings.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.wem.io/platform/wemmodeler/project-settings/mobile-app-settings.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.