When you create a project, you specify settings for any platform you're targeting: iOS, Android, Windows, and Desktop Web Viewer. Many of the project settings you specify affect the behavior of the app.
Creating a project requires signing in to the on-demand portal using an Adobe ID that has a Master Admin role. Editing a project requires either a Master Admin role or a user role with a "Manage Projects and Users" permission.
Project Setup video
The Submit button is dimmed until the required fields are specified. We recommend that you pay attention to the following options when creating the project:
Project Title (Required) Specify the name of your application or publication.
Link Reference (Required) Use reverse DNS format (such as com.company.application) so that you can link to the app externally.
Report Suite (Required) Specify the name of the Analytics Report Suite. You cannot edit this value once you specify it. See the option description later in this article for details.
App Navigation Once you create the project, you cannot edit this setting at this time. See the option description later in this article for details.
Project Title Specify the project title for referencing within the portal. The project title is not customer facing.
Link Reference Use the reverse DNS format (such as com.company.application) to specify a link reference. For example, if you create a com.adobe.learn link reference, you can create a hyperlink (com.adobe.learn://) that opens the app on iOS devices.
Enable Social Sharing If you select this option, the top navigation bar in each article will include a social sharing menu that lets your users share the article with others. If this option is not selected, this menu does not appear in the app. See Social sharing in AEM Mobile apps.
Enable China Distribution This option appears only if your company has signed the China Addendum to allow content to be distributed in China. See Enabling content distribution in China.
Brand Image Specify a .jpg or .png mage that appears in the app menu and on the landing pages of shared articles. For best results, we recommend uploading a transparent .png image with a width or height of 800 pixels.
Use the Store settings tab to specify platform-specific information for iTunes App Store, Google Play Store, and Windows Store.
iTunes Connect Shared Secret If your iOS app includes iTunes subscriptions, you must specify the shared secret information in project settings. You can copy the shared secret information from iTunes Connect. Use the same shared secret for all iOS apps in your company account. For details, see the iOS publishing guide for AEM Mobile.
iTunes App URL This URL is used in the social sharing workflow to let share recipients download the app if it’s not installed. It's important to specify this URL so that share recipients can tap a link to download or open your app.
You can obtain the iTunes App URL even if Apple has not yet approved the app. In iTunes Connect, click the app and use the "View in App Store" link, or right-click the app and choose Copy Link Address.
Google Play Shared Secret If your Android app includes in-app purchases, you must specify the shared secret information in project settings. The shared secret is also referred to as a "license key." You can copy the shared secret information from the Google Play Developer Console. For details, see the Android publishing guide for AEM Mobile.
Google Play App URL Specify the Google Play App URL to improve the social sharing experience on Android devices—when social sharing becomes supported.
Windows Main Package Identity Name Specify the Windows Main Package Identity Name for any app you submit to Windows store. For details, see the Windows publishing guide for AEM Mobile.
Windows Store App URL Specify the Windows Store App URL to improve the social sharing experience on Windows devices—when social sharing becomes supported.
Collection Defaults When you publish a collection, the Product ID you specify is added to the Products & Subscriptions panel. Use the Collection Defaults setting to determine whether the product associated with the collection is set to Free, Entitlement Required, or Restricted by default. Free collections are available to all users regardless of article settings. Entitled collections appear in the app, but metered or protected articles include a paywall that prompts users to sign in or make a purchase. See Paywalls and article preview in AEM Mobile apps. Restricted collections are hidden until the user signs in to gain access. For details, see Restricted collections in AEM Mobile apps.
You can use Products & Subscriptions section of the Portal to edit the Product Type setting at any time.
Enable Article Preview Select this option to allow users to preview articles in an "Entitlement Required" collection. Edit properties for each article to determine whether the article is Free, Protected, or Metered. If the user has not signed in or purchased the collection, protected articles in entitlement collections are obscured by a paywall. However, if articles are set to Metered, unentitled users can preview articles until they reach the threshold that you specify. Users can view free articles even if Enable Article Preview is not selected.
If the collection is free, all articles within that collection are also free, even if they're set to Metered or Protected.
For details, see Paywalls and article preview in AEM Mobile apps.
The Article Threshold setting lets your users download and view the specified number of articles marked as "Metered" within the specified time when previewing articles in "Entitlement Required" collections. Once a user reaches the limit specified in Article Threshold, a paywall message appears when they browse to metered articles. When the threshold time elapses at the specified Start Time, users can view metered articles again. The threshold applies to metered articles in the app, not just within a collection.
If users swipe through articles without staying on any article for a specific time, the articles do not count against the threshold. The threshold is reached only when once the user stays on an article for a period of time, called the dwell time. The dwell time is 25 seconds (tablet) and 15 seconds (phone).
For more information, see Paywalls and article preview in AEM Mobile apps.
Enable Extensibility Features If this option is selected, the "Enable Extensibility Features" option in article properties will be selected for all new articles by default. You can override the default in article properties. This project setting has no effect on existing articles.
You can improve content discovery by enabling in-app searching in your app. When you enable search indexing, article metadata is indexed when you create articles.
Note that once you enable search indexing, you cannot disable this option in project settings. Article metadata will continue to be indexed. However, you can disable the search option in your production or preflight app.
Indicate whether in-app search is availabe in your production apps or your custom preflight apps. If you enable search in your app, a Search option appears in the app menu.
To enable search in your app, you must rebuild it by selecting the app, clicking the edit icon, and clicking Submit.
If you enable in-app searching in your production apps, your users can then perform searches based on metadata of published articles, such as finding articles by a specific author or finding all articles with a company name. If any metadata field includes the search string, the article appears in the list of search results.
Specify the default language for your search. You can edit individual articles to override the default language setting. An article will appear in search results only if its language setting matches the device language setting. For example, articles indexed as Spanish will not appear in search results if the device language is French.
Search includes all the public-facing properties that have text fields, such as Article Title, Author, Abstract, and Department. It doesn't cover internal properties such as Article Name or Internal Keywords, nor does it cover selection items such as Metered (for Article Access) or High (for Article Importance).
Restricted content is hidden from search results unless the user is signed in and has access to the restricted content. Articles from a collection that is set to “Entitled” or “Free” are still displayed in search results. Free articles always appear in search results. In collections that are set to Restricted, protected or metered (non-free) articles are hidden from search results.
Note the following issues with search:
- Search does not distinguish phone- or tablet-only content at this time. Search results might include tablet content even though the request came from a phone article.
- At this time, the display of cards in search results is determined by the Default Layout in the Layout Templates section of the Portal.
- In-app search does not support search of HTML article content.
Report Suite Specify a unique Report Suite name for your app. We recommend that you use a reverse DNS format such as com.company.application. For details. see Analytics for AEM Mobile.
You can use one top-level collection for both phones and tablets or create separate default collections for tablets and phones.
Create separate default collections for tablets and phones if you want to do either of the following:
- Use a different set of collections or articles in phones and tablets.
- Use different fixed-layout articles for phones (such as 1136x640 articles) and tablets (such as 1024x768 articles). Uploading multiple renditions of article files within each article is not yet supported, so you would need to create separate phone and tablet versions of the articles and add them to different collections.
Note that you can create multiple layouts within a layout template. With layout renditions, it is no longer necessary to create two top-level collections in order to apply different layouts to tablets and phones. Creating cards and layouts: Layout renditions.
At this time, you cannot edit this project setting to switch between 1 and 2 top-level collections.
|1 Top Level Collection||2 Top Level Collections|
Using two top-level collections in your project limits the social sharing workflow. Specifically, users on mobile devices can tap a link to open an article in the app only if the project includes one top-level collection.
You can avoid clutter in the On-Demand Portal by hiding unused projects. A Master Admin or a user with a "Manage Project & Users" permission can hide a project. When a project administrator marks a project as hidden, the project does not appear by default in the Portal UI for users who have access to the project.
Users can toggle a button to display or hide projects marked as hidden. When displayed, hidden projects are dimmed.
You can edit project settings at any time by selecting the project and clicking Edit Project. Editing a project requires the "Manage Projects and Users" permission.
Note that you cannot edit certain project settings such as the Report Suite name or the top-level nav collection option.
After you edit project settings, it is not necessary to update any app that you've created. For example, if you enable Article Preview or Direct Entitlement, the changes are reflected nearly immediately in your existing app.