Testing and releases

An app release affects software, store metadata and the editorial experience at the same time. Use a written acceptance check and name one release owner before submitting changes.

Release checklist

• open the front page, sections and several article formats;
• test internal links, external links and native sharing;
• verify notification opening and permission handling;
• review branding, legal links and support information;
• test current supported iOS and Android versions;
• record known limitations and the rollback or follow-up plan.

Store review and staged distribution may add lead time. Do not promise an exact public date until the relevant store has approved the release. Content changes in WordPress can often appear without a binary app release, while native navigation, permissions or branding may require one.

After release

Monitor reader reports, crash information available to the app owner and a small set of critical journeys. Keep the previous release notes and decision record so support can distinguish a content issue from an app regression.