The latest articles on Forem by Vladislav Baranov (@vlad_mobi). https://forem.com/vlad_mobi https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3804191%2Fae853df3-601a-45da-bdee-68dc13fae15d.png https://forem.com/vlad_mobi en Vladislav Baranov Tue, 03 Mar 2026 15:44:03 +0000 https://forem.com/vlad_mobi/stop-manually-translating-whats-new-in-app-store-connect-1cad https://forem.com/vlad_mobi/stop-manually-translating-whats-new-in-app-store-connect-1cad <h2> Every iOS Release, the Same Routine </h2> <ul> <li>Add new version in App Store Connect </li> <li>Update “What’s New” </li> <li>Copy the text </li> <li>Translate it </li> <li>Paste it into every single locale </li> <li>Repeat again for the next release </li> </ul> <p>If you support multiple languages, this quickly becomes the most boring part of shipping.</p> <h2> The Real Problem </h2> <p>App Store Connect doesn’t provide:</p> <ul> <li>Bulk translation for release notes </li> <li>Smart reuse of previous updates </li> <li>Fast multilingual workflows </li> </ul> <p>So every version turns into repetitive manual work.</p> <p>And if you also publish on Google Play — you have to repeat the same process there too, following their formatting rules.</p> <h2> What I Built </h2> <p>I built a small Chrome extension that works directly inside App Store Connect and helps automate the “What’s New” workflow.</p> <p>No API setup.<br><br> No App Store Connect keys.<br><br> No external dashboards.</p> <p>It works directly in the browser, inside the existing publishing interface.</p> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F241agbqddq9hhzhgp1xl.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F241agbqddq9hhzhgp1xl.png" alt=" " width="400" height="400"></a></p> <h2> You Can </h2> <ul> <li>Write your update text in one language </li> <li>Automatically translate it into all other localizations </li> <li>Instantly fill localized “What’s New” fields </li> <li>Generate properly formatted text for Google Play as well </li> </ul> <p>Instead of switching between tabs, translators, spreadsheets, and documents — everything happens in one place.</p> <h2> Why This Matters </h2> <p>If you ship often, this saves real time.</p> <p>If you support 5–15 languages, this removes a lot of repetitive copy-paste work.</p> <p>It doesn’t replace your localization strategy —<br><br> it just removes the mechanical part of writing release notes.</p> <h2> Who This Is For </h2> <ul> <li>Indie iOS developers </li> <li>Teams shipping frequent updates </li> <li>Apps supporting multiple markets </li> <li>Developers publishing on both App Store and Google Play </li> </ul> <p>If you only support one language, you probably don’t need it.</p> <p>If you localize every release — this helps.</p> <h2> Closing </h2> <p>Shipping updates should feel exciting — not administrative.</p> <p>If you're curious, you can try it here:<br><br> <a href="https://rinly.app/" rel="noopener noreferrer">https://rinly.app/</a></p> <p>I’d genuinely love feedback from other iOS developers.</p> ios productivity webdev chrome