App settings and release checks

Choose Settings in the rail to open App settings. It opens over your current workspace, so Design or Code and your panels stay as they were. Menu preferences… in the canvas's right-click menu opens it too, and so does app artwork listed under Used in your app in Assets.

A change applies when you finish a field, by moving to another field or pressing Enter (Ctrl / Cmd + Enter in a field with several lines). Switches and menus apply as you choose. Settings go through the same checked project history as your other edits, so they save with your project and Undo can take them back.

Build for, in General, chooses iOS, Android or both. The iOS and Android sections, their fields, search results and release checks follow that choice. Values for a platform you switch off are kept for when you switch it back on.

The sections run down the left of the dialog. iOS and Android appear only for the platforms you build for.

General

Project name in Appsanic, App display name under the installed icon, Project slug, Release version, Build for and Screen rotation: Automatic, Portrait only or Landscape only.

Appearance

System controls appearance (Light by default, Dark or Follow device) and the status bar: Show status bar and its icon colour. A page can use its own status bar settings in Page settings. Your app's colours stay in Theme.

iOS

iOS bundle identifier, iOS build number, Support iPad, Require full screen on iPad and Non-exempt encryption, your export-compliance answer. Appsanic never answers it for you.

Android

Android application ID and Android version code, a whole number that goes up with every upload.

Icons & launch

App icon, a 1024 × 1024 PNG with no transparency, the Launch screen image with its background colour and width, and the layers of Android's adaptive and themed icons. You choose each image from your assets.

Permissions

Camera, Photo library and Microphone. Each one declares access in the native build. With iOS selected, an allowed permission also needs the message people see in the prompt. People still choose whether to grant it.

App links

Custom URL schemes and Verified link domains, one per line, so links can open your installed app. Set the page a link opens in Pages, and host the association files on your own domain.

Store listing

Drafts of your listing for each store: name, language, descriptions, categories, keywords, What’s new, privacy, support and contact details, copyright, screenshots and the Google Play feature graphic. Text fields with a store limit show a counter.

Publishing

Answers about this release: Release type, and whether people can create an account, need to log in, see ads, buy digital content or subscriptions, and whether children are in the audience. It also holds Review instructions and, with iOS selected, the App Review contact.

Release checks

What a native build and each store still need, grouped by kind. See Release checks below.

Editor preferences

The Right-click menu switch for this session, and Project session: where the project is stored, its component count, revision and project format. After an older project is upgraded, its upgrade report appears here too.

Type in Search all settings… at the top of the dialog. It matches the names and descriptions of settings in every section that applies to your platforms. Each result names its section; select one to open that section with its control in focus.

Enter

Open the first match.

Down

Move from the search field into the results.

Escape

Clear the search. A second Escape closes the dialog.

Missing required shows only the inputs that still need attention, with their count. A badge reads Required, or Required · iOS or Required · Android when only one store asks for it. When applicable marks a field that only becomes required after certain answers. If nothing matches, Clear filters starts again.

Release checks compares your settings with what a native build and the stores need, and its count also shows beside the section name. Once every tracked input is complete, the summary reads “Required settings filled”; until then it counts the items that need attention. Native configuration, Publishing inputs and Store submission show where each part stands, and store submission always reads “Complete outside Appsanic”.

Required for native preparation

Configuration problems such as a missing identifier, required artwork or a permission message. Clear these before a native build.

Required publishing inputs

Listing, review and artwork inputs the stores ask for, including images whose format or size is known to be wrong. Complete them before you submit.

Verify before release

Things the browser cannot confirm, such as whether every referenced image file can be found.

Complete outside Appsanic

Signed builds, testing on real devices, store declarations, your developer accounts and the submission itself.

Each issue names its platform, and Open setting takes you to the exact control, including a permission message or a screenshot list. You can keep designing with an unfinished draft: listing and review inputs can wait until you submit. Links at the end open Expo's, Apple's and Google's own guides for the platforms you build for.

Some fields only become required because of an earlier answer, or because of something in your app. Release checks adds them as soon as that happens.

Every Publishing question needs an answer, and No counts as one. A first release can keep the defaults: version 1.0.0, and 1 for the iOS build number and Android version code. For an update, compare your numbers with every earlier upload in each store, including test tracks: Appsanic cannot see your store history.

App settings checks every value before applying it. A value it cannot accept stays in its field with the reason beneath it, and the footer counts your unapplied edits, so you can move between sections without losing what you typed.

• Use saved value puts the field back to the value that is saved.
• If the setting changed elsewhere while you were typing, the field says so and shows the current saved value. Choose Use saved value or Apply my edit: nothing is overwritten until you decide.
• Done, Escape and the close button apply your valid edits. If one cannot be applied, the dialog stays open on that field, and Discard unapplied edits drops it so you can close.
• Switching off a platform or a permission waits until you finish or discard an edit in a field it would hide.

The Publishing section only records answers about your release. Nothing goes to a store from App settings, and completing every release check does not submit anything.

In a project saved to your account, Publish in the top bar opens Publish your app. Its Project source section works today: Download project source saves your project as an Appsanic JSON file named after it and ending in .appsanic.json. The file holds your saved design, source code, settings and embedded assets; remote media stay as links. Appsanic applies your code drafts and waits for the save first, so the file matches your saved project.

The file includes your store listing drafts and App Review contact details, so share it with care.

• Preview and test on a phoneCheck the layout, keyboard and permissions on a real device.
• Theme, fonts and assetsAdd the icon, launch image and screenshots your settings use.
• Pages and navigationChoose the page a link to your app opens.