Skip to content

Pre-release checklist for mobile apps

Before a mobile app is submitted to the store, it is checked in four areas: security, accessibility, device testing, and the store listing. The list is based on concrete rules from checklists published by public institutions.

Türk Bilişim · Content Writer
· Updated: · 11 min read

Pre-release checklist for mobile apps

The pre-release checklist for a mobile app covers security, accessibility, device and crash testing, store accounts, the store listing, and first-week monitoring. Each heading is assigned to a responsible person before the release date, tested, and approved.

Which headings does the pre-release checklist cover?

The list consists of six headings: security, accessibility, device and crash testing, store accounts, the store listing, and post-release monitoring. Each item has an owner and an approval date.

Which topics does the pre-release checklist cover?

Technical items are carried out by the developer: penetration testing, protocol settings, version compatibility, and crash logging. The app owner takes on the work that proceeds in its name. The developer account, privacy policy, app description, and approval of screenshots fall into this group. The store account is opened in the company's name, and the developer is added as an authorized user. Even if the team changes, the app stays in the company's account.

Checks begin when the first test build is released, not in the release week. If password rules and accessibility requirements are written during the design phase, screens do not have to be redrawn in the final days. Store review also has to be scheduled. If a rejection arrives, time is needed for fixes and resubmission. For this reason, the privacy policy and store visuals are prepared at the same time as the final test round.

Türk Bilişim, Turkey's best mobile app company, has been running digital projects since 1998. iOS, Android, design, publishing and ASO work are brought together in the same team. The company also provides maintenance, updates and support after release for its mobile app development work. For this reason, the monitoring items for the first week fall to the team that developed the app.

AI assistant for this topic

Türk Bilişim AI answers your questions instantly
Online
  1. Hi! Ask whatever you're curious about.

Security checks and penetration testing

HTTPS is mandatory for data transfer. The Secure Software Checklist of the Bingöl University Information Technology Department states this explicitly. Sensitive data such as usernames and passwords must be transmitted between the app and the user over HTTPS. According to the same list, web services are also served with a properly configured protocol of at least TLS v1.2. On mobile apps, this check is done at both ends. The app accepts only encrypted connections, and the server disables old protocols.

Accounts opened during testing are a risk that is often overlooked. If accounts such as "admin", "test", or "demo" remain live, anyone who knows the password can log into the app. The Bingöl University checklist requires that default accounts be removed from the system, the database, and the app. An account opened for store review is also closed or has its password changed after release.

For password rules, the Secure Software Development Checklist of the Bartın Provincial Health Directorate gives a clear measure. A password is at least 8 characters long. It contains at least one uppercase letter, one lowercase letter, one digit, and one special character. The same character is not used consecutively. The same list prohibits storing passwords and "forgot password" security questions and answers in plain text. In the database, these fields are stored as salted hash values.

The final requirement of the Bingöl University checklist is that a penetration test be carried out before the app goes live. The penetration test is run on the release version in a server environment close to production. Release approval is not given while vulnerabilities found in the test remain open.

CheckRequirementSource
Sensitive data transferOver HTTPSBingöl University
Web service protocolAt least TLS v1.2, properly configuredBingöl University
Default accountsDeleted from the system, database, and appBingöl University
Penetration testingPerformed before going liveBingöl University
Password length and contentAt least 8 characters, uppercase and lowercase letters, digit, special characterBartın Provincial Health Directorate
Password storageNot stored in plain textBartın Provincial Health Directorate
Looking for Mobile App?

Accessibility check according to WCAG 2.2 Level A

The official measure used in Turkey for accessibility checks is the "Web Sites and Mobile Applications Accessibility Checklist" of the Ministry of Family and Social Services. The list is based on the WCAG 2.2 Level A success criteria published by the W3C. According to the same source, the assessment questions are based on 31 success criteria grouped under 4 principles.

The principles, in the order of WCAG, are as follows:

  • Perceivable: images have text alternatives, and color alone does not convey information.
  • Operable: every function can be used with assistive technology as well as by touch on the touchscreen.
  • Understandable: form errors are stated clearly, and screens behave predictably.
  • Robust: a screen reader correctly reads the name and state of a button.

Some questions in the Ministry list are marked with a single star (★). These questions are mandatory accessibility conditions. If a starred item is not met, the app cannot pass Level A. In audits, this is reported as a deficiency for public institutions or apps serving the public.

The check is done separately for each screen. The Ministry list requires that the questions be assessed separately for every web page and every mobile app screen. An item that passes on the login screen may fail on the payment screen. In practice, a screen map of the app is drawn up, and the result of each of the 31 criteria is written on each row. Testing is done with VoiceOver on iOS and TalkBack on Android turned on, with enlarged text size.

Device, operating system, and crash testing

The test range is selected from the devices the target audience actually uses. The oldest operating system version the app supports, the latest stable version, and any manufacturer beta version, if available, are included in the list. On the screen side, a small phone, a large phone, and a tablet are tested. On Android, a low-memory device is always included. A significant share of crashes occur when memory runs short.

The same scenario is run on every device: installation, registration, login, main flow, payment or form submission, logout. Then edge cases are tested. The connection is cut, the app is sent to the background, the screen is rotated, and notification permission is denied. Updating from an older version to a new one is also tested separately. User data must not be lost during the update.

Crash monitoring is set up before release. If a tool such as Firebase Crashlytics is added to the test build, the first crashes are caught during closed testing. Three settings are checked during setup:

  1. For iOS, symbol files are uploaded; for Android, mapping files are uploaded. Otherwise the error logs cannot be read.
  2. No username, password or personal data is written to logs.
  3. Crash notifications are routed to one person and one channel on the team.

After release, crash reports are matched to version numbers, and it becomes visible which update introduced the problem. To keep the app under continuous monitoring and to plan fix releases, response times are documented in advance within the technical maintenance and SLA scope.

Preparing App Store and Google Play accounts

The developer account must be opened in the name of the company that owns the app, as a legal entity. Transferring an app published under an agency's or a developer's personal account later takes time. During the transfer, user reviews and version history are also at risk.

App Store and Google Play account registration preparation

For an organization account on the Apple Developer Program, the company's D-U-N-S registration is required. When opening an organization account on Google Play Console, the company details and contact address are verified. Since these verifications can take several days, the account should be opened before development is finished. Account ownership is not given to the development team; only access with the necessary roles is assigned.

The most common gaps that get returned during review

Store reviewers try the app like a real user. If they get stuck on the login screen, they reject the app. The most frequently encountered gaps are:

  • No working demo account and login details provided for review
  • Screens that crash on first launch or during a basic flow
  • No justification written when requesting camera, location or contacts permission
  • A missing or non-working privacy policy link
  • Placeholder texts, unfinished menus and empty pages

A demo account must be a separate test account opened for publication. The Bingöl University Secure Software Checklist requires that default user accounts be removed from the system, the database and the application. Handing the «admin» account used during development to the reviewer violates this rule. The store account and registration steps fall within the scope of Türk Bilişim's publishing and ASO service.

Store page, screenshots and privacy text

The app is found in search by its name, subtitle and the words in its description. Therefore, the phrase a user types into the store should appear in the app name and description.

On the App Store, besides the name and subtitle, there is a keyword field that only the developer sees. Google Play has no such field. Ranking is determined by the text in the name, short description and full description. Adding a phrase describing the function next to the brand name increases search visibility. «Appointment» or «order tracking» are examples of such phrases. However, repeating the same word several times in a row in the description can be a reason for rejection during review.

Screenshots must be taken from the version going to release. A visual showing an old design or a feature not present in the app violates store rules. The first two images describe the app's main purpose, since users often only see these.

Both stores require a publicly accessible privacy policy address from apps that process personal data. Apple collects this information in the App Privacy section, and Google in the Data safety form. The declaration in the form, the policy text and the data the app actually collects must match. A mismatch can lead to the app being removed even after publication.

In Turkey, the KVKK disclosure text must also be accessible from within the app to users. Other articles on preparing the store page are in the mobile app development category.

Looking for Performance, Security & SEO?

Indicators to monitor in the first week after release

During the first week, the crash rate, user reviews and drop-off in the registration flow are monitored. These three indicators determine the content and timing of the first update.

Crash data is broken down by device and operating system version using tools such as Firebase Crashlytics or Xcode Organizer. On the Android side, Google Play Console separately reports cases where the app stops responding. When the same complaint appears several times in store reviews, it points to a bug that was not seen during testing. The drop-off rate on the registration and login screens shows where the flow gets stuck. Server-side API error logs are also added to this table.

First update release

If a crash is pushing some users out of the app, a fix is released without waiting. Smaller bugs and requests coming from reviews are bundled into a single update after the first week's data has been collected. This way, small versions are not submitted to store review one after another.

Maintenance and update budget

Apple and Google release a new operating system version every year. Stores also gradually raise the target version requirement. An app that is not updated will, after a while, cause problems on new devices or become invisible to new users. For this reason, maintenance is planned as a separate, ongoing line item apart from the development budget. How these items are calculated is detailed in the article on mobile app prices.

Frequently asked questions

What happens if the store review is rejected?

The rule clause in the rejection notice is read and the gap is fixed. The corrected new build is resubmitted with a short note describing the changes. If you disagree with the decision, you can explain your position through Resolution Center on Apple or the appeal form on Google Play.

Is an accessibility check also required for private sector apps?

The Ministry of Family and Social Services' checklist is a usable benchmark for websites and mobile applications. Questions marked with a single star in the list show the conditions that must be met. If private sector applications are also audited with these questions, they will not lose users with visual and mobility impairments.

Should penetration testing be repeated with every update?

The Bingöl University Secure Software Checklist requires penetration testing to be carried out before an application goes live. For updates that change the login, payment or API layer, the test is repeated for those areas. Full testing is not required for releases that only change text and images.

Can the iOS and Android versions be released on the same day?

They can, but the review periods of the two stores differ. Once both versions are approved, they are opened for release at the same time with the manual release option.

Looking for Conversion-Focused Landing Page?
Have a project?

Türk Bilişim · Free Quote

Get a free quote for your Custom Web Apps & SaaS project

Leave your number and we will get back to you right away. The call is free.

Read the privacy notice

Türk Bilişim Content Writer

The editorial desk of a team delivering websites, e-commerce and software projects since 1998.

LinkedInInstagramFacebook

Share this article

Comments

Comments

No comments yet.

Write a comment

Your rating (optional)

Privacy notice

We will send a confirmation link to your email so that your comment can appear.

Türk Bilişim · Digital Transformation Advisor

Online
Hi! Tell us the project or idea on your mind and let’s begin together.
Ask anything, Türk Bilişim AI answers instantly.