<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Mosmox Journal]]></title><description><![CDATA[Mosmox Journal]]></description><link>https://mosmox.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6afb2fef67ead47edfde582c/c77e9263-ff4e-4b14-833f-71c538bdcba0.png</url><title>Mosmox Journal</title><link>https://mosmox.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 15:15:44 GMT</lastBuildDate><atom:link href="https://mosmox.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[App Startup Speed: Which Milliseconds Users Actually Feel]]></title><description><![CDATA[Users don't measure cold start with a stopwatch, but they feel the difference between a ready screen and a splash that seems stuck. Startup time is the…]]></description><link>https://mosmox.hashnode.dev/app-startup-speed-which-milliseconds-users-actually-feel</link><guid isPermaLink="true">https://mosmox.hashnode.dev/app-startup-speed-which-milliseconds-users-actually-feel</guid><category><![CDATA[Android]]></category><category><![CDATA[iOS]]></category><category><![CDATA[Mobile Development]]></category><category><![CDATA[performance]]></category><dc:creator><![CDATA[Mosmox Studio]]></dc:creator><pubDate>Wed, 18 Nov 2026 11:44:12 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6afb2fef67ead47edfde582c/a93e3c37-cc34-4dd7-9510-13ca446e4ee7.webp" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Users don't measure cold start with a stopwatch, but they feel the difference between a ready screen and a splash that seems stuck. Startup time is the first trust check: is it worth waiting for the product to get ready, or is it easier to close it and open a competitor?</p>
<p>In our projects, the conversation about startup speed almost always begins with "it's fast on my phone". So the first step is agreeing on what exactly we measure, on which devices and against which thresholds. Below are the metrics, targets, tools and optimisation sequence we use on Android and iOS.</p>
<h2>Three startup moments that are easy to confuse</h2>
<p>Measure the time from tapping the icon to three different events. These are fundamentally different moments:</p>
<ul>
<li><strong>First frame (TTID, time to initial display).</strong> The system has shown the first frame of the app's UI. Android records this metric automatically, and it's what Android vitals uses.</li>
<li><strong>Ready to use (TTFD, time to full display).</strong> Primary content has loaded and the person can perform the action they came for. The system can't know this moment on its own: the app must report it via reportFullyDrawn() or, in Compose, via ReportDrawnWhen.</li>
<li><strong>Fully loaded.</strong> Secondary blocks, images and recommendations have arrived. For the user, this moment usually matters least.</li>
</ul>
<p>A screen that's drawn quickly but doesn't respond to touch is not a fast experience. So for the product, the key metric is TTFD; TTID is a technical indicator.</p>
<p>Also distinguish startup types. <strong>Cold</strong> — the process is created from scratch, for example after a phone reboot. <strong>Warm</strong> — the process is alive, but the activity is recreated. <strong>Hot</strong> — the app simply returns from the background. Optimise assuming a cold start: that improves the other two as well.</p>
<h2>Thresholds and targets</h2>
<table>
<thead>
<tr>
<th>What we measure</th>
<th>Threshold or target</th>
<th>Source</th>
</tr>
</thead>
<tbody><tr>
<td>Cold start, Android</td>
<td>5 s or longer is excessive</td>
<td>Android vitals</td>
</tr>
<tr>
<td>Warm start, Android</td>
<td>2 s or longer is excessive</td>
<td>Android vitals</td>
</tr>
<tr>
<td>Hot start, Android</td>
<td>1.5 s or longer is excessive</td>
<td>Android vitals</td>
</tr>
<tr>
<td>First frame, iOS</td>
<td>target of about 400 ms</td>
<td>Apple, WWDC 2019 "Optimizing App Launch"</td>
</tr>
<tr>
<td>Feels instantaneous</td>
<td>about 0.1 s</td>
<td>Nielsen Norman Group</td>
</tr>
<tr>
<td>Limit of uninterrupted attention</td>
<td>about 1 s</td>
<td>Nielsen Norman Group</td>
</tr>
</tbody></table>
<p>Vitals thresholds are not a goal but the floor of decency. From our experience, service and e-commerce apps should aim for a cold TTFD under 2 seconds on mid-range devices. That's a studio estimate, not a standard, and it should be calibrated against your own data and audience.</p>
<h2>How to measure: tools</h2>
<ul>
<li><strong>In the lab on Android:</strong> Jetpack Macrobenchmark with StartupTimingMetric gives stable TTID and TTFD on a real device. For deep analysis, a Perfetto trace with the Android App Startups row.</li>
<li><strong>In the lab on iOS:</strong> the App Launch template in Instruments and XCTApplicationLaunchMetric in UI tests.</li>
<li><strong>In the field on Android:</strong> Android vitals in Play Console, with comparison against a peer group of similar apps.</li>
<li><strong>In the field on iOS:</strong> Xcode Organizer shows launch time by version, and MetricKit delivers aggregated metrics from users' devices.</li>
</ul>
<p>Compare the median and the tails of the distribution — p90 and p95 — not just the average. Users on weak devices can have a completely different experience, and they're the ones most likely to abandon the app. We explained why lab testing on a flagship is misleading in our article on <a href="https://mosmox.com/en/posts/testuvannia-mobilnoho-zastosunku-na-nedorohykh-prystroiakh">testing on inexpensive devices</a>.</p>
<h2>The method: trace, hypothesis, controlled release</h2>
<p>In the <a href="https://developer.android.com/topic/performance/appstartup/case-study-gmail-wear">Gmail Wear OS</a> case study, the team analysed Perfetto traces: main thread state, time in the Runnable state (a sign of CPU contention), DEX file reading, binder transactions and JIT activity. Based on the findings, they made two groups of changes. Replacing the animated spinner with a static image and deferring the shimmer state improved startup latency by 50%. Enabling R8 rewriting of Baseline Profiles added another 20%.</p>
<p>What matters is not the percentage itself — on a two-core watch, removing an animation naturally has a bigger effect than on a phone — but the method: trace first, then a hypothesis, a controlled change and re-measurement. The team specifically recommends automating trace collection and validating every hypothesis with an A/B test.</p>
<p>The business side is well illustrated by the Lyft case from the Android Developers Blog: a 21% reduction in the drivers app's startup time came with a 5% increase in driver sessions.</p>
<h2>First optimisation steps</h2>
<ol>
<li><strong>Measure a baseline.</strong> Cold TTID and TTFD on 2–3 devices of different classes, median and p90.</li>
<li><strong>Clean up Application.onCreate.</strong> Defer secondary SDK initialisation — analytics, chat, ads — until after the first screen or until first use. On Android, the App Startup library and lazy initialisation via Hilt help.</li>
<li><strong>Don't load what you don't need.</strong> The first screen should request only the data it displays. Cache the previous session's result and show it immediately.</li>
<li><strong>Get work off the main thread.</strong> Disk, network, deserialising large JSON — background only.</li>
<li><strong>Check heavy animations and layout.</strong> Animated splash, Lottie on the first screen, deep view hierarchies.</li>
<li><strong>Add Baseline Profiles</strong> for key journeys and verify the effect with Macrobenchmark. Don't forget R8 and, for profile rewriting, AGP 8.2 or newer.</li>
<li><strong>Protect the result.</strong> Add a startup benchmark to CI and compare every release with the previous one.</li>
</ol>
<h2>Typical mistakes</h2>
<ul>
<li>Measuring only TTID and reporting success while the user stares at a skeleton for several more seconds.</li>
<li>Testing a debug build: it lacks ART and R8 optimisations, so the numbers are meaningless.</li>
<li>Artificially extending the splash screen "for the brand" — users perceive it as slowness.</li>
<li>Relying on the average instead of p90.</li>
<li>Initialising a dozen SDKs in Application.onCreate "because the docs say so".</li>
<li>Optimising without re-measuring: some "improvements" have no effect at all.</li>
</ul>
<h2>Action plan</h2>
<ol>
<li>Define the moment after which the user can actually work, and mark it with reportFullyDrawn().</li>
<li>Set up Macrobenchmark or XCTApplicationLaunchMetric for cold start.</li>
<li>Capture a baseline on a low-end, mid-range and flagship device.</li>
<li>Check field data in Android vitals and Xcode Organizer.</li>
<li>Work through the optimisation list above, one change at a time, re-measuring each.</li>
<li>Add the benchmark to CI and watch for regressions.</li>
</ol>
<p>Fast startup isn't a race for the smallest number. It's a short path to the first useful action, without the deception of skeleton screens and hidden unreadiness. We wrote about how that path fits into the overall first impression in our article on <a href="https://mosmox.com/en/posts/pershi-60-sekund-u-mobilnomu-zastosunku">the first 60 seconds in an app</a>, and about the business effect of speed using <a href="https://mosmox.com/en/posts/zomato-shvydkist-zastosunku-ta-trymannia-korystuvachiv">Zomato's experience</a>.</p>
<p><strong>Sources:</strong> <a href="https://developer.android.com/topic/performance/appstartup/case-study-gmail-wear">Android Developers: How Gmail Wear OS improved startup</a>; <a href="https://developer.android.com/topic/performance/vitals/launch-time">Android Developers: App startup time</a>; <a href="https://developer.android.com/google/play/vitals/launch-time">Android vitals: App startup time</a>; <a href="https://developer.apple.com/videos/play/wwdc2019/423/">Apple WWDC 2019: Optimizing App Launch</a>; <a href="https://android-developers.googleblog.com/2022/03/how-single-android-developer-improved.html">Android Developers Blog: How a single Android developer improved Lyft's Drivers app startup time by 21% in one month</a>; <a href="https://www.nngroup.com/articles/response-times-3-important-limits/">Nielsen Norman Group: Response Times</a>.</p>
<p>Originally published on the Mosmox journal: <a href="https://mosmox.com/en/posts/shvydkist-zapusku-mobilnoho-zastosunku-metryky">App Startup Speed: Which Milliseconds Users Actually Feel</a></p>
]]></content:encoded></item><item><title><![CDATA[How Error Messages Shape Trust in a Mobile App]]></title><description><![CDATA[An error is the moment when the system fails to keep its promise. "Something went wrong" leaves the user alone with uncertainty: was the money charged, was…]]></description><link>https://mosmox.hashnode.dev/how-error-messages-shape-trust-in-a-mobile-app</link><guid isPermaLink="true">https://mosmox.hashnode.dev/how-error-messages-shape-trust-in-a-mobile-app</guid><category><![CDATA[UX]]></category><category><![CDATA[Mobile Development]]></category><category><![CDATA[Accessibility]]></category><category><![CDATA[app design]]></category><category><![CDATA[iOS]]></category><dc:creator><![CDATA[Mosmox Studio]]></dc:creator><pubDate>Tue, 17 Nov 2026 09:45:36 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6afb2fef67ead47edfde582c/7304b951-eb7b-4688-a519-1219a89ab60b.webp" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>An error is the moment when the system fails to keep its promise. "Something went wrong" leaves the user alone with uncertainty: was the money charged, was the request saved, should they tap again? A good message, by contrast, explains the state and helps them move forward.</p>
<p>In our projects we've noticed that error moments are exactly when users most often contact support, leave low ratings and uninstall the app. The cause isn't the error itself — failures happen to everyone — but the fact that the person doesn't understand what happened or what to do. Here's how we design error messages so they preserve trust.</p>
<h2>What a message should contain</h2>
<p>Nielsen's heuristic #9 frames the task as helping users recognise, diagnose and recover from errors. In practice, a good message answers five questions:</p>
<ul>
<li><strong>What happened</strong> — in plain words, without jargon: "We couldn't send your order", not "Error 500".</li>
<li><strong>Whether data was kept</strong> — "Your cart and address are saved".</li>
<li><strong>What to do now</strong> — a specific action: "Try again", "Change card", "Check connection".</li>
<li><strong>Whether to wait</strong> — "We'll send it automatically as soon as you're back online".</li>
<li><strong>Where to get help</strong> if the problem persists — with a request ID support can find in the logs.</li>
</ul>
<p>Don't show a technical code instead of an explanation. The team's log can contain a stack trace and request ID, but the interface must answer the person's questions. A code can sit in small print beneath the explanation — it helps support but doesn't replace the text.</p>
<h2>An error map: from technical cause to copy</h2>
<p>To avoid inventing copy from scratch each time, we build an error map together with backend developers. Here's a baseline version.</p>
<table>
<thead>
<tr>
<th>Technical cause</th>
<th>What the user sees</th>
<th>Action in the UI</th>
</tr>
</thead>
<tbody><tr>
<td>No network</td>
<td>"No connection. Your changes are saved on the device"</td>
<td>automatic retry once the network is back</td>
</tr>
<tr>
<td>Timeout</td>
<td>"The server is taking longer than usual"</td>
<td>"Try again", with no loss of input</td>
</tr>
<tr>
<td>401 — session expired</td>
<td>"Sign in again to continue"</td>
<td>re-authentication returning to the same screen</td>
</tr>
<tr>
<td>403 — no permission</td>
<td>"You don't have access to this section"</td>
<td>explanation of how to get access</td>
</tr>
<tr>
<td>404 — object not found</td>
<td>"This order was deleted or moved"</td>
<td>go to the list</td>
</tr>
<tr>
<td>409 — conflict</td>
<td>"The data changed on another device"</td>
<td>show the current version and offer a choice</td>
</tr>
<tr>
<td>422 — validation error</td>
<td>text next to the specific field</td>
<td>focus on the first invalid field</td>
</tr>
<tr>
<td>429 — too many requests</td>
<td>"Too many attempts. Try again in 30 seconds"</td>
<td>countdown to the next attempt</td>
</tr>
<tr>
<td>5xx — server failure</td>
<td>"We're having technical issues and are already on it"</td>
<td>delayed retry, support contact</td>
</tr>
</tbody></table>
<p>For forms, the most important rule is to show the error next to the field, not as a generic banner at the top. We covered this in detail in our article on <a href="https://mosmox.com/en/posts/mobilni-formy-iak-zmenshyty-pomylky-vvedennia">mobile forms</a>.</p>
<h2>Payments and irreversible actions: three states, not two</h2>
<p>For a payment, file upload or application submission, distinguishing "success" from "error" isn't enough. You need at least three states: "not sent", "processing" and "completed". The most dangerous scenario is a timeout during payment: the customer doesn't know whether the payment went through, while the server may already have processed it.</p>
<ul>
<li>Use idempotency keys for payment requests: a repeated tap won't create a second charge.</li>
<li>Disable the button after the first tap and show the processing status, not just a spinner.</li>
<li>After a timeout, ask the server for the operation status before offering "Try again".</li>
<li>For irreversible actions, as WCAG criterion 3.3.4 requires, let users review, confirm or cancel the action.</li>
</ul>
<p>We discussed how to design the action button itself so it honestly reflects state in our article on the <a href="https://mosmox.com/en/posts/knopka-dii-u-mobilnomu-interfeisi">primary action button</a>.</p>
<h2>Errors are part of the scenario, not an exception</h2>
<p>The <a href="https://developer.android.com/topic/performance/appstartup/case-study-gmail-wear">Gmail Wear OS</a> case study on Android Developers shows the value of measuring real startup and finding bottlenecks: the team replaced an animated spinner with a static image and got a faster start. For error design the lesson is similar — don't hide uncertain states behind an endless spinner. If an operation takes more than a few seconds, show an honest status, and after a reasonable timeout, a clear message and a controlled retry.</p>
<p>Presentation matters too. A transient snackbar is fine for non-critical events ("Couldn't refresh the feed"), but not for data loss or a failed payment: the person may miss it. Critical errors must stay on screen until the user dismisses them, and the screen reader must announce them.</p>
<h2>How to write error copy: step by step</h2>
<ol>
<li>List every error the API can return and group them by user action, not by code.</li>
<li>For each group, write copy using the formula: what happened + what was saved + what to do.</li>
<li>Avoid blame: not "You entered the wrong number" but "The number must have 9 digits after +380".</li>
<li>Check copy length in every language: a long translation must not get truncated.</li>
<li>Add the request ID to technical details and make it searchable in logs.</li>
<li>Review the copy together with support: they know what questions customers ask.</li>
</ol>
<h2>How to test errors</h2>
<p>Errors rarely make it into the test plan because "everything works in the demo". We add a dedicated pass:</p>
<ul>
<li>offline on every key screen and network loss in the middle of an operation;</li>
<li>slow network with timeouts (Network Link Conditioner on iOS, network emulation in Android Studio);</li>
<li>double and rapid repeated taps on the submit button;</li>
<li>session expiry while filling in a form;</li>
<li>long localised error messages and maximum system font size;</li>
<li>VoiceOver and TalkBack announcements of errors.</li>
</ul>
<h2>Typical mistakes in error design</h2>
<ul>
<li>One generic "Something went wrong" message for every case.</li>
<li>Clearing the form after a server error: the person retypes everything and often gives up.</li>
<li>An error shown only as a red border with no text — a problem for both accessibility and comprehension.</li>
<li>An endless spinner instead of a timeout and an explanation.</li>
<li>A "Try again" button that repeats the same action with the same cause of failure, for example while still offline.</li>
<li>A jokey tone in critical situations: "Oops! Your money went somewhere" doesn't inspire trust.</li>
</ul>
<h2>Checklist</h2>
<ol>
<li>There is an API error map with copy and actions for each group.</li>
<li>Every message explains what happened, what was saved and what to do.</li>
<li>User input is never lost after an error.</li>
<li>Payments have three states and idempotent requests.</li>
<li>Critical errors don't disappear by themselves and are announced by the screen reader.</li>
<li>Errors are tested offline, on a slow network, with repeated taps and long texts.</li>
<li>Support can find an error by its request ID.</li>
</ol>
<p>Trust grows when a product behaves predictably even when it can't perform the desired action. A good error message is a continuation of the service, not an admission of defeat. A broader set of accessibility checks, including for errors, is in our article on <a href="https://mosmox.com/en/posts/dostupnist-mobilnykh-zastosunkiv-praktychna-perevirka">mobile app accessibility</a>.</p>
<p><strong>Sources:</strong> <a href="https://developer.android.com/topic/performance/appstartup/case-study-gmail-wear">Android Developers: Gmail Wear OS case study</a>; <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">Nielsen Norman Group: 10 Usability Heuristics</a>; <a href="https://www.nngroup.com/articles/error-message-guidelines/">Nielsen Norman Group: Error-Message Guidelines</a>; <a href="https://www.w3.org/WAI/WCAG22/Understanding/error-suggestion.html">W3C: Understanding SC 3.3.3 Error Suggestion</a>; <a href="https://developer.apple.com/design/human-interface-guidelines/alerts">Apple Human Interface Guidelines: Alerts</a>; <a href="https://docs.stripe.com/api/idempotent_requests">Stripe API: Idempotent requests</a>.</p>
<p>Originally published on the Mosmox journal: <a href="https://mosmox.com/en/posts/dizain-povidomlen-pro-pomylky-mobilnyi-zastosunok">How Error Messages Shape Trust in a Mobile App</a></p>
]]></content:encoded></item><item><title><![CDATA[New App Store Age Rating Questions: What to Answer by 12 January Without Losing Your Audience]]></title><description><![CDATA[Since 16 November 2026, the age rating questionnaire in App Store Connect has two new questions: can people share their real-world location with others…]]></description><link>https://mosmox.hashnode.dev/new-app-store-age-rating-questions-what-to-answer-by-12-january-without-losing-your-audience</link><guid isPermaLink="true">https://mosmox.hashnode.dev/new-app-store-age-rating-questions-what-to-answer-by-12-january-without-losing-your-audience</guid><category><![CDATA[iOS]]></category><category><![CDATA[Android]]></category><category><![CDATA[Mobile Development]]></category><category><![CDATA[app store]]></category><dc:creator><![CDATA[Mosmox Studio]]></dc:creator><pubDate>Mon, 16 Nov 2026 16:37:14 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6afb2fef67ead47edfde582c/eae6ab80-154e-415a-a1d2-b55cbfc364d3.webp" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Since 16 November 2026, the age rating questionnaire in App Store Connect has two new questions: can people share their real-world location with others (Shared Location), and does the app include dating or romantic relationships (Dating and Relationships). <strong>Every app must answer them by 12 January 2027</strong>, and the answers are also required with every update or questionnaire change.</p>
<p>On paper it is a couple of checkboxes. In practice, one answer can raise an app to 18+, hide it from child and teen accounts with parental controls, and block a release right before the holidays. Here is what changed, how to audit your features, and how to avoid losing an audience over one careless answer.</p>
<h2>What Apple announced</h2>
<p>According to <a href="https://developer.apple.com/news/?id=yxkh08us">Apple's announcement of 2 November 2026</a>, the age rating section gains two declarations:</p>
<ul>
<li><strong>Shared Location:</strong> sharing real-world location with another person or group;</li>
<li><strong>Dating and Relationships:</strong> features that enable dating or relationship connections between real people, or a virtual companion that engages the user in sexual or romantic content.</li>
</ul>
<p>Apps with dating features receive a <strong>minimum rating of 18+</strong>. Shared Location, Apple says, may not affect the minimum age in some regions. Brazil is the exception: local law requires A16 for location sharing and A18 for dating. If you believe your app deserves a lower rating (Apple's example is location sharing built for parents and children), you can request an official rating from <a href="https://www.gov.br/mj/pt-br/assuntos/seus-direitos/classificacao-1">Brazil's Ministry of Justice (MJSP)</a>. Once verified, that rating is shown on the Brazilian App Store.</p>
<h2>Context: the third stage of a ratings overhaul</h2>
<p>These questions are not a one-off. Apple has been rebuilding its age rating system for more than a year, and each stage added work for app teams:</p>
<table>
<thead>
<tr>
<th>When</th>
<th>What changed</th>
<th>Deadline</th>
</tr>
</thead>
<tbody><tr>
<td>July 2025</td>
<td><a href="https://developer.apple.com/news/?id=ks775ehf">New 13+, 16+ and 18+ ratings</a> alongside 4+ and 9+. New mandatory questions: in-app controls, capabilities, medical and wellness topics, violent themes</td>
<td>31 January 2026</td>
</tr>
<tr>
<td>July 2026</td>
<td><a href="https://developer.apple.com/news/?id=tlur8uvi">Social media questions</a>: a feed or other mechanism that redistributes or amplifies user content. New Social Media descriptor and a Time Allowances category (iOS 27)</td>
<td>September 2026</td>
</tr>
<tr>
<td>November 2026</td>
<td>Shared Location and Dating and Relationships; dating means 18+</td>
<td>12 January 2027</td>
</tr>
</tbody></table>
<p>The takeaway for product teams: the age rating is no longer a formality filled in once at first launch. It is part of the product spec and needs a review whenever a new social, location or AI feature ships.</p>
<h2>Why this matters even for an "ordinary" app</h2>
<p>The new questions most often catch products where the relevant feature appeared as a side effect, not obvious dating services:</p>
<ul>
<li><strong>Delivery and ride-hailing.</strong> The courier or driver sees the customer's location, and customers share their trip with family.</li>
<li><strong>Family and education apps.</strong> Parents see where a child is; students check in to classes by location.</li>
<li><strong>Sports and events.</strong> Group runs, a meeting point on the map, "friends nearby".</li>
<li><strong>Communities and marketplaces.</strong> Direct messages between strangers that easily turn into dating.</li>
<li><strong>AI chatbots.</strong> A "virtual companion" with a romantic scenario is named explicitly in the Dating and Relationships definition, and since 2025 Apple has required teams to account for AI assistants and chatbots in their rating.</li>
</ul>
<p>A wrong assessment hurts either way. Overstate it and the app disappears for some teens and family accounts, and marketing loses reach. Understate it and App Review may reject an update or demand a fix at the worst moment, such as before a holiday release.</p>
<h2>Feature audit: how to answer correctly</h2>
<p>We recommend not filling in the questionnaire from memory. Run a short audit with the product manager and a developer who knows the codebase. Typical cases and how we see them:</p>
<table>
<thead>
<tr>
<th>Feature</th>
<th>Likely declaration</th>
<th>What to do</th>
</tr>
</thead>
<tbody><tr>
<td>User sends their location to a chat or shares a route</td>
<td>Shared Location</td>
<td>Declare it; check whether it can be disabled for minors</td>
</tr>
<tr>
<td>Courier/driver sees the customer’s address during an order</td>
<td>Probably Shared Location</td>
<td>Compare with the definition in Apple’s help; document the decision</td>
</tr>
<tr>
<td>Store map or "nearest venue"</td>
<td>Usually no: location is not passed to another person</td>
<td>Explain in the App Review notes if the feature looks ambiguous</td>
</tr>
<tr>
<td>Direct messages between strangers</td>
<td>Possibly Dating and Relationships, depending on purpose</td>
<td>Check the description, screenshots and marketing: if the product is positioned as dating, the rating will be 18+</td>
</tr>
<tr>
<td>AI companion with an emotional or romantic scenario</td>
<td>Dating and Relationships</td>
<td>Either restrict the scenarios or accept 18+</td>
</tr>
<tr>
<td>Feed of user-generated content</td>
<td>Social Media (since September 2026)</td>
<td>Consider disabling the feed for users under 13</td>
</tr>
</tbody></table>
<p>This table reflects our practice, not Apple's official position. For the final definitions see <a href="https://developer.apple.com/help/app-store-connect/reference/app-information/age-ratings-values-and-definitions">Age ratings values and definitions</a>, and in borderline cases explain your decision briefly in the App Review notes.</p>
<h2>Step-by-step plan before 12 January</h2>
<ol>
<li><strong>List the features</strong> that pass location to other people, let strangers communicate or use generative AI. Cross-check it against your specification; if you don't have one, start with our article <a href="https://mosmox.com/en/posts/tekhnichne-zavdannia-na-mobilnyi-zastosunok">on structuring an app specification</a>.</li>
<li><strong>Open App Information in App Store Connect</strong> and review the current answers and the rating in each region: ratings can differ by country.</li>
<li><strong>Model the impact.</strong> If a "yes" raises the rating, estimate what share of your audience it affects. For family and education products this can be critical.</li>
<li><strong>Decide whether to change the product or the rating.</strong> Sometimes it is simpler to disable a feature for younger users than to raise the rating for the whole app.</li>
<li><strong>Update the questionnaire early</strong>, without waiting for a release. Answers can be changed separately from a build.</li>
<li><strong>Align Google Play.</strong> On Google Play the rating comes from the <a href="https://support.google.com/googleplay/android-developer/answer/9859655">IARC questionnaire</a> in Play Console. Keep the logic consistent across stores so you don't end up 18+ in one and 12+ in the other.</li>
<li><strong>Document the decision</strong> in the repository or wiki: who answered, when and why. It saves time on the next rules change.</li>
</ol>
<h2>Keeping a teen audience: age signals</h2>
<p>If a feature can't be removed, it can be switched off depending on the user's age. Both platforms offer APIs that return an age category without an exact date of birth:</p>
<table>
<thead>
<tr>
<th></th>
<th>Apple: Declared Age Range</th>
<th>Google: Play Age Signals</th>
</tr>
</thead>
<tbody><tr>
<td>Returns</td>
<td>An age range; the minimum age is in lowerBound</td>
<td>An age category: by default 0–12, 13–15, 16–17, 18+</td>
</tr>
<tr>
<td>Setup</td>
<td>Declared Age Range capability in Xcode (entitlement com.apple.developer.declared-age-range)</td>
<td>The age-signals library; custom age thresholds are configured in Play Console</td>
</tr>
<tr>
<td>Limitations</td>
<td>Declared by the user or a parent, partly verified; responses are cached</td>
<td>Beta; data is returned only where the law requires it; may not be used for ads or analytics</td>
</tr>
<tr>
<td>Docs</td>
<td><a href="https://developer.apple.com/documentation/declaredagerange">Declared Age Range</a></td>
<td><a href="https://developer.android.com/google/play/age-signals">Play Age Signals</a></td>
</tr>
</tbody></table>
<p>This is exactly the approach Apple describes for social features: if they are disabled for users under 13, the app is not placed in the Social Media category for that age group. It is reasonable to apply the same pattern to location sharing or direct messages, but check how the questionnaire treats your specific case.</p>
<p>From a UX point of view, an age check is one more step in the first run, and it should not destroy conversion. We covered this in our articles <a href="https://mosmox.com/en/posts/onbordynh-mobilnoho-zastosunku-bez-zayvykh-krokiv">on onboarding without extra steps</a> and <a href="https://mosmox.com/en/posts/pershi-60-sekund-u-mobilnomu-zastosunku">on the first 60 seconds in an app</a>. If your age gate needs a date entry, see our piece <a href="https://mosmox.com/en/posts/mobilni-formy-iak-zmenshyty-pomylky-vvedennia">on mobile forms</a>.</p>
<h2>Common mistakes</h2>
<ul>
<li><strong>Leaving it until release.</strong> The new questions appear exactly when you submit an update. If the questionnaire is incomplete, the release stalls at the worst moment.</li>
<li><strong>Answering only for the main flow.</strong> Location in support chat, messaging in a beta feature, an AI helper in settings: it's all part of the app.</li>
<li><strong>Ignoring marketing.</strong> A description, screenshots and keywords that promise "meet new people" contradict a "no" in the questionnaire.</li>
<li><strong>Different logic in the App Store and Google Play.</strong> It confuses users and invites questions from reviewers.</li>
<li><strong>Relying on an age check without server-side logic.</strong> If a feature is only hidden in the UI but the API still serves the data, there is no protection.</li>
</ul>
<h2>Checklist</h2>
<ul>
<li>List of location, user-to-user communication and AI features is complete.</li>
<li>Current per-region ratings in App Store Connect are reviewed.</li>
<li>Shared Location and Dating and Relationships answered before 12 January 2027.</li>
<li>Social media questions (since September 2026) answered.</li>
<li>For Brazil, an official rating request considered if A16/A18 doesn't fit the product.</li>
<li>Google Play IARC questionnaire aligned with App Store answers.</li>
<li>Declared Age Range / Play Age Signals with server-side checks implemented for age-dependent features.</li>
<li>Store description and screenshots match the declared features.</li>
<li>Decision documented and an owner for the questionnaire assigned.</li>
</ul>
<p>The age rating is now part of the product, not just of publishing. Teams that review it when planning each new feature don't learn about the problem from an App Review email the day before release.</p>
<p><strong>Sources:</strong> <a href="https://developer.apple.com/news/?id=yxkh08us">Apple: Upcoming new age rating content descriptors</a>; <a href="https://developer.apple.com/news/?id=ks775ehf">Apple: Updated age ratings in App Store Connect</a>; <a href="https://developer.apple.com/news/?id=tlur8uvi">Apple: Age rating questionnaire now includes social media questions</a>; <a href="https://developer.apple.com/help/app-store-connect/reference/app-information/age-ratings-values-and-definitions">Apple: Age ratings values and definitions</a>; <a href="https://developer.apple.com/documentation/declaredagerange">Apple: Declared Age Range</a>; <a href="https://developer.android.com/google/play/age-signals">Google: Play Age Signals</a>; <a href="https://support.google.com/googleplay/android-developer/answer/9859655">Google Play: Content ratings</a>; <a href="https://www.gov.br/mj/pt-br/assuntos/seus-direitos/classificacao-1">MJSP: Classificação Indicativa</a>.</p>
<hr />
<p><em>Originally published on the</em> <a href="https://mosmox.com/en/posts/novi-vikovi-reitynhy-app-store-do-12-sichnia"><em>Mosmox journal</em></a><em>. Mosmox is a mobile app studio — we design and build iOS and Android apps.</em></p>
]]></content:encoded></item></channel></rss>