IMI

R1.2. - The style guides linked in this requirement have been updated. More detail.

R2.1.1 - Development must be compatible with iOS16 or higher versions. Apps compatible with iOS 14 or lower versions will not be published. More detail.

R3.1.1 - New applications and updates (starting from May) must be targeted at least to Android 14 (API 34). More detail.

The change in requirement R1.2. implies that there have been changes in the design of some resources, such as the app icon or splash screen, and these changes must be made for both new apps and updates to existing apps. This requirement is mandatory from the moment this email is sent.

We remind you that you can consult the requirements here, in the section of "Highlighted Information for the Publication of Mobile Applications."

This schedule only affects the release of versions, as all publication processes related to the OSAM cycle will continue as usual (development version validation, builds, Firebase distribution, smoke tests, support, among others).

In case a significant incident occurs in the production environment, we will be available for its release, if necessary.

• R1.1.6.4 – It must be reported before the release of a new version whether it will be a full roll-out or progressive. More details.
• R1.2.2 - This requirement has been modified, removing the section referring to the favorites icon. More details.
• R1.11.2 – It is now mandatory to meet the code quality criteria indicated in SonarQube. If not met, the app will not be published. More details.
• R3.3.1 – This requirement has been clarified, explaining that it involves displaying a new screen that complies with the design requirements for the splash screen. More details.

We remind you that you can consult the requirements here, in the section of "Highlighted Information for the Publication of Mobile Applications."

This schedule only affects the release of versions, as all publication processes related to the OSAM cycle will continue as usual (development version validation, builds, Firebase distribution, smoke tests, support, among others).

In case a significant incident occurs in the production environment, we will be available for its release, if necessary.

• R1.11 - This has been reorganised and divided into a section relating to the Test Plan (R1.11.1) and a new section relating to the quality of software (R1.11.2), which will only be a recommendation until the third quarter of 2023. More details
• R3.1.1 - Android versions must be compatible with version 8.0 (api 26) or superior of the operating system. More details

The procedure for publishing mobile apps has also been updated, with a new section added:

Expiry of version ready to be published according to the number of days the version remains in this state before being released to markets. More details

A brief overview of the changes in this version:

R1.3.2 - Message has to be shown in the lower part of the screen, reminding the user that a licence for the app has been denied. Instructions have also been given for applying for the licence for correctly managing push notifications for Android 13 or higher devices.

R3.1.1 - New existing apps have to be geared to Android 13 (API 33). Updates will be compulsory, as of May.

R3.3 - The way the Splash Screen is implemented changes from Android 12 on.

Please note that you can find all the updated requirements in here

What We Offer > Services > Mobile Services Office > Mobile App Publication Highlights

A brief overview of the changes in this version:

R1.5.1 - It is now a requirement to register the device language and indicate the language selected on starting the app.

R1.6.2 - Use of the OSAM common module for device information and adding it to the contact email.

R1.6.6 - If the application involves arriving at a destination, and this destination is external to the app, the user must be given the option of selecting among the different navigation applications installed on their device.

Please note that you can find all the updated requirements in the Mobile App Publication Highlights section of OSAM's website.

What We Offer > Services > Mobile Services Office > Mobile App Publication Highlights

• R1.4.3 - Apps must have a system to disable service calls, both from third-party and proprietary sources. More details.
• R1.11.2 - Starting in October, it will be a requirement to comply with code quality criteria for app publication. More details.

In this new version, a thorough review of the requirements has been carried out, updating or eliminating those that are outdated. New requirements have also been added, including two very important ones, which we highlight here:

R1.7.3 - OSAM Common Module.

OSAM has developed a new library to store and improve the functionalities of the version control and rating modules. Use of this new library - called the OSAM common module - will be obligatory, under the following conditions:

All new apps must incorporate the OSAM common module.

From 1 September 2022, all updates to City Council apps must include the common module.

R1.14 - Integration with municipal mapping.

The official map framework for the City Council's apps is Mapbox. To this effect, Mapbox is mandatory for apps with an exclusive territorial scope of Barcelona. This obligation takes the following form:

All new apps must integrate Mapbox and use the City Council’s municipal mapping.

From 1 January 2023, all updates to the City Council's apps must include Mapbox and the municipal mapping.

A brief summary of the other significant changes in this version:

R1.1.4 - Flutter must be used for new developments.

R1.5.3 - You must have a topic to be able to send push notifications to a specific version.

R2.2 - The nomenclature of the bundle field shall have the following format: yyyymmddhh.

Keep the links to the requirements on hand:

CAT: http://www.bcn.cat/mobil/apps/docsdsv/requerimentsAppsAjmnt_ca.htm

ES: http://www.bcn.cat/mobil/apps/docsdsv/requerimentsAppsAjmnt_es.htm