[{"data":1,"prerenderedAt":3525},["ShallowReactive",2],{"\u002Fblog\u002Fapp-store-medical-device-status-declaration-2027\u002F":3,"\u002Fblog\u002Fapp-store-medical-device-status-declaration-2027\u002F-related":499,"\u002Fblog\u002Fapp-store-medical-device-status-declaration-2027\u002F-resources":3509},{"id":4,"title":5,"author":6,"body":10,"category":438,"createdAt":439,"description":440,"disclosure":441,"extension":442,"faq":443,"howTo":441,"lastVerified":441,"location":459,"meta":460,"navigation":466,"ogImage":441,"path":467,"primaryKeyword":468,"readingTime":469,"related":470,"seo":476,"sources":477,"stem":489,"tags":490,"takeaways":491,"updatedAt":439,"url":497,"__hash__":498},"blog\u002Fblog\u002Fapp-store-medical-device-status-declaration-2027.md","App Store Medical Device Status Declaration: 2027 Deadline",{"name":7,"social":8},"Simon Dziak",{"twitter":9},"@SzymonDziak",{"type":11,"value":12,"toc":423},"minimark",[13,21,24,30,35,103,106,114,118,121,131,139,142,146,149,152,155,175,196,200,203,206,252,261,266,284,287,290,294,297,300,303,306,310,313,316,320,382,400,407,411],[14,15,16,20],"p",{},[17,18,19],"strong",{},"If your app is in Health & Fitness or Medical, or you told Apple it has frequent medical or treatment information, and it's available in the EEA, UK or US, you have to declare in App Store Connect whether it's a regulated medical device by \"early 2027\", or you won't be able to submit updates."," Apple gives no exact date, so I'd do it now. It takes a few minutes if the answer is No.",[14,22,23],{},"I checked each one on October 19, 2026. The facts come from Apple's March 26, 2026 news post and the App Store Connect Help page, as shown in the sources. Apple can change a date, so open the linked pages before you plan around it.",[14,25,26,29],{},[17,27,28],{},"Disclosure:"," App369 is my studio. I build and fix Flutter and Firebase apps, and the last section mentions what I sell. Apple doesn't pay me for anything on this page. This is not legal or regulatory advice.",[31,32,34],"h2",{"id":33},"the-dated-timeline","The dated timeline",[36,37,38,54],"table",{},[39,40,41],"thead",{},[42,43,44,48,51],"tr",{},[45,46,47],"th",{},"Date",[45,49,50],{},"What happens",[45,52,53],{},"Source",[55,56,57,75,90],"tbody",{},[42,58,59,63,66],{},[60,61,62],"td",{},"March 26, 2026",[60,64,65],{},"Apple posts the update. The status is required for new apps that meet the criteria, in order to distribute in these regions",[60,67,68],{},[69,70,74],"a",{"href":71,"rel":72},"https:\u002F\u002Fdeveloper.apple.com\u002Fnews\u002F?id=nyqbfz1y",[73],"nofollow","Apple Developer News",[42,76,77,82,85],{},[60,78,79],{},[17,80,81],{},"Early 2027",[60,83,84],{},"Existing apps must have provided a status. Apple gives no exact date",[60,86,87],{},[69,88,74],{"href":71,"rel":89},[73],[42,91,92,95,98],{},[60,93,94],{},"After early 2027, if undeclared",[60,96,97],{},"You'll no longer be able to submit app updates",[60,99,100],{},[69,101,74],{"href":71,"rel":102},[73],[14,104,105],{},"The post says: \"Existing apps distributed in these regions that meet either of the criteria above must provide a status by early 2027.\" It adds: \"However, if you haven't declared your app's status by early 2027, you'll no longer be able to submit app updates.\"",[14,107,108,109,113],{},"The pages I read say nothing about live apps being removed. The stated consequence is blocked updates. That still matters, because a blocked update is also a blocked security fix or iOS compatibility release. For the other dated iOS requirement next year, see ",[69,110,112],{"href":111},"\u002Fblog\u002Fios-27-sdk-requirement-april-2027-xcode-27-flutter\u002F","the iOS 27 SDK requirement",".",[31,115,117],{"id":116},"which-apps-and-which-regions","Which apps and which regions",[14,119,120],{},"Apple's help page says the requirement applies to apps that are available in the EU\u002FEEA, the United Kingdom or the United States, and that also meet either of two criteria:",[122,123,124,128],"ul",{},[125,126,127],"li",{},"The app has a primary or secondary category of Health & Fitness or Medical.",[125,129,130],{},"You indicated that your app contains \"frequent\" Medical or Treatment Information in the age rating questionnaire in App Store Connect.",[14,132,133,134,138],{},"The second criterion is easy to miss. A fitness app in the Health & Fitness category is caught by the first one. An app in another category, say Lifestyle, can be caught by the second if you answered \"frequent\". If you haven't looked at your age rating answers since Apple's update, my guide to the ",[69,135,137],{"href":136},"\u002Fblog\u002Fapp-store-age-rating-questions-update-2026\u002F","age rating questions"," shows where that field lives.",[14,140,141],{},"I'd treat the three regions separately. Apple asks you to indicate whether the app is a regulated medical device \"with respect to each region's regulatory authority\", and the declaration lets you choose the countries or regions where the answer is Yes.",[31,143,145],{"id":144},"what-regulated-medical-device-means-in-apples-help-text","What \"regulated medical device\" means in Apple's help text",[14,147,148],{},"Apple's definition: \"Regulated medical device apps are used for a range of medical purposes, including diagnosis, prevention, monitoring, and treatment of diseases and physiological conditions. They may function on their own or by interfacing with medical device hardware. These apps may require registration or authorization from regulatory bodies such as the U.S. Food and Drug Administration (FDA).\"",[14,150,151],{},"The news post uses similar wording and says such apps \"function on their own or as part of a system\".",[14,153,154],{},"Apple lists indicators that an app is a regulated medical device:",[122,156,157,160,163,166,169,172],{},[125,158,159],{},"Cleared or approved by the US FDA",[125,161,162],{},"Registered on the US FDA medical device database",[125,164,165],{},"Issued a CE mark by an EU-based notified body under the EU MDR or MDD",[125,167,168],{},"Issued a UKCA mark by a UK-based approved body under the UK Medical Device Regulations",[125,170,171],{},"Self-certified under the EU MDR or MDD",[125,173,174],{},"Self-certified under the UK Medical Device Regulations",[14,176,177,178,183,184,189,190,195],{},"For the rules themselves, Apple links to the European Commission's ",[69,179,182],{"href":180,"rel":181},"https:\u002F\u002Fhealth.ec.europa.eu\u002Fmedical-devices-sector_en",[73],"medical devices sector page",", GOV.UK's ",[69,185,188],{"href":186,"rel":187},"https:\u002F\u002Fwww.gov.uk\u002Fguidance\u002Fregulating-medical-devices-in-the-uk",[73],"Regulating medical devices in the UK"," and the ",[69,191,194],{"href":192,"rel":193},"https:\u002F\u002Fwww.fda.gov\u002Fmedical-devices",[73],"FDA's medical devices pages",". Those are the regulators' own entry points. I'm pointing to them and not summarizing them, because I'm not qualified to say how a regulator would classify your app.",[31,197,199],{"id":198},"what-the-declaration-asks","What the declaration asks",[14,201,202],{},"Apple says to select No if your app \"doesn't provide any health or medical features, or access health data to support non-health features\". In the steps, selecting No and clicking Save completes the process.",[14,204,205],{},"If you select Yes, you pick the countries or regions and then fill in, per region:",[36,207,208,218],{},[39,209,210],{},[42,211,212,215],{},[45,213,214],{},"Field",[45,216,217],{},"What Apple says",[55,219,220,228,236,244],{},[42,221,222,225],{},[60,223,224],{},"EU Manufacturer SRN or FDA Owner\u002FOperator Number",[60,226,227],{},"Should align with your EUDAMED listing and\u002For FDA establishment registrations. Not required for the UK",[42,229,230,233],{},[60,231,232],{},"Instructions for use URL",[60,234,235],{},"The user guide or instructions for use for your app, hosted on your website",[42,237,238,241],{},[60,239,240],{},"Use statement",[60,242,243],{},"For the US, your indications for use statement. For the EU\u002FEEA and UK, your intended purpose or intended use statement",[42,245,246,249],{},[60,247,248],{},"Safety information",[60,250,251],{},"Relevant warnings, precautions and contraindications as they appear in your labeling",[14,253,254,255,260],{},"For the US, Apple says the safety information can also include a statement such as \"To report a problem or adverse event to the FDA, visit ",[69,256,259],{"href":257,"rel":258},"http:\u002F\u002Fwww.fda.gov\u002Fsafety\u002Freport-problem-fda",[73],"www.fda.gov\u002Fsafety\u002Freport-problem-fda",".\" You can add localized versions from a dropdown. Contact information is managed in the Business section, under Regulated Medical Devices in Compliance.",[262,263,265],"h3",{"id":264},"where-to-click","Where to click",[267,268,269,272,275,278,281],"ol",{},[125,270,271],{},"In Apps, select the app.",[125,273,274],{},"Under General, click App Information.",[125,276,277],{},"Under App Store Regulations & Permits, click Declare Regulated Medical Device.",[125,279,280],{},"Say whether the app is a regulated medical device in any country or region.",[125,282,283],{},"If Yes, select the countries or regions, complete the fields and click Save.",[14,285,286],{},"The required role is Account Holder or Admin. To change it later, click Edit next to the Regulated Medical Devices section. The status shown per region is Yes, No, or Missing Info, which means you declared Yes but the required information is incomplete.",[14,288,289],{},"My advice: if you run several apps, check each one. The declaration is per app, and an app you forgot is the one that blocks your next update.",[31,291,293],{"id":292},"how-to-answer-if-your-app-is-a-general-wellness-app","How to answer if your app is a general wellness app",[14,295,296],{},"Here I have to be careful. Apple's pages I read don't use the phrase \"general wellness\" and don't say where that line falls. Apple gives you its definition and the indicator list above, and tells you to select No if the app has no health or medical features.",[14,298,299],{},"So for an app like a habit tracker, a step counter or a meditation timer, the question to ask yourself is whether it does anything in Apple's definition: diagnosis, prevention, monitoring or treatment of diseases and physiological conditions. If it clearly doesn't, and you hold none of the clearances, marks or registrations on Apple's list, No is the answer Apple's definition points to. Apple's page doesn't say how a step counter or habit tracker with health features should be classified, so that part is my reading.",[14,301,302],{},"If the app is in a gray area, for example it reads heart rate and flags irregular readings, it suggests what to do about a symptom, or its store text talks about a condition, don't guess. Ask a regulatory adviser who knows medical devices in the regions where you distribute. This is not legal or regulatory advice, and I can't tell you how a regulator would classify your app.",[14,304,305],{},"My advice: whatever you answer, make your store text, in-app copy and the declaration agree. Apple shows the declaration on your product page, so a description that contradicts it would sit right next to it for readers.",[31,307,309],{"id":308},"what-shows-on-the-product-page","What shows on the product page",[14,311,312],{},"Apple's help page says: \"This information will display to customers on your App Store product page.\" That applies to the information you enter when you declare Yes: the SRN or FDA number, the instructions for use URL, the use statement and the safety information, per region.",[14,314,315],{},"The news post also says the App Store will show whether an app is a regulated medical device in those regions. I didn't find a page that shows exactly where each item appears, so I haven't described the layout. After you save, Apple says the information goes live within 24 hours, or once the app is approved and released if it isn't live yet. Check your own product page in each storefront afterward.",[31,317,319],{"id":318},"a-checklist-for-small-health-app-owners-and-flutter-apps","A checklist for small health app owners and Flutter apps",[267,321,322,328,334,340,346,352,358,364,370,376],{},[125,323,324,327],{},[17,325,326],{},"List your apps"," and check each one's primary and secondary category in App Store Connect.",[125,329,330,333],{},[17,331,332],{},"Check the age rating field."," Look at your answer for Medical or Treatment Information. \"Frequent\" puts you in scope even outside the two categories.",[125,335,336,339],{},[17,337,338],{},"Check where you're distributed."," The requirement covers the EEA, UK and US. If you're in none of them, it doesn't apply to that app, per Apple's help text.",[125,341,342,345],{},[17,343,344],{},"Confirm your role."," Only an Account Holder or Admin can declare.",[125,347,348,351],{},[17,349,350],{},"Decide the answer per region"," using Apple's definition and indicator list. Write down why.",[125,353,354,357],{},[17,355,356],{},"Get advice if unclear."," A regulatory adviser, not a developer, decides whether an app is a regulated medical device.",[125,359,360,363],{},[17,361,362],{},"If Yes, prepare the content first:"," SRN or FDA number, a hosted instructions for use page, the use statement and the safety text.",[125,365,366,369],{},[17,367,368],{},"Declare, then verify"," the status reads Yes or No, not Missing Info, and check the product page.",[125,371,372,375],{},[17,373,374],{},"Match your metadata."," Store description, screenshots, in-app onboarding and any health claims should agree with the declaration.",[125,377,378,381],{},[17,379,380],{},"Do it before your next release,"," not during it. A rejected or blocked submission on release day is a bad time to find a missing field.",[14,383,384,385,389,390,394,395,399],{},"For Flutter apps, this is an App Store Connect setting, not a code change. Nothing in ",[386,387,388],"code",{},"pubspec.yaml"," or your Xcode project carries it. What can change is the app itself: if you use HealthKit through a Flutter plugin or add features that interpret readings, that's a product decision to run past your adviser before the build, not after. If you also ship on Android, the ",[69,391,393],{"href":392},"\u002Fblog\u002Fgoogle-fit-api-deprecated-health-connect-2026\u002F","Google Fit to Health Connect guide"," covers the separate Google deadline, and my ",[69,396,398],{"href":397},"\u002Fblog\u002Fmobile-app-development-healthcare-guide\u002F","healthcare app guide"," covers the wider build and privacy side.",[14,401,402,403,113],{},"For every other dated Apple, Google Play and Firebase requirement in 2026 and 2027, see ",[69,404,406],{"href":405},"\u002Fblog\u002Fapp-store-google-play-deadlines-2026-2027\u002F","App Store and Google Play deadlines for 2026 and 2027",[31,408,410],{"id":409},"need-a-hand","Need a hand?",[14,412,413,414,418,419,113],{},"If your Flutter app is stuck on an App Store Connect error, a blocked update or a release pipeline problem, the ",[69,415,417],{"href":416},"\u002Ffixed-price\u002Fflutter-firebase-bug-fix\u002F","App Fix Ticket"," covers it in two fixed-price steps. A $450 Diagnosis gives you the root cause with evidence and a fixed repair quote within 3 business days, credited toward the fix. If you go ahead, the $1,200 Fix takes 5 business days and comes as a pull request. Or ",[69,420,422],{"href":421},"\u002Fcontact\u002F","send me a short description",{"title":424,"searchDepth":425,"depth":425,"links":426},"",2,[427,428,429,430,434,435,436,437],{"id":33,"depth":425,"text":34},{"id":116,"depth":425,"text":117},{"id":144,"depth":425,"text":145},{"id":198,"depth":425,"text":199,"children":431},[432],{"id":264,"depth":433,"text":265},3,{"id":292,"depth":425,"text":293},{"id":308,"depth":425,"text":309},{"id":318,"depth":425,"text":319},{"id":409,"depth":425,"text":410},"AI & Technology","2026-10-19T12:00:00.000Z","Apple wants a regulated medical device status for Health & Fitness and Medical apps in the EEA, UK and US, or you can't submit updates after early 2027. The regions, the quoted deadline, what the declaration asks, how to answer, and a checklist, checked October 19, 2026.",null,"md",[444,447,450,453,456],{"question":445,"answer":446},"Which apps must declare a regulated medical device status?","Apps available in the EU\u002FEEA, the UK or the US that also meet either of two criteria, according to Apple's App Store Connect Help. The criteria are a primary or secondary category of Health & Fitness or Medical, or a \"frequent\" answer in the Medical or Treatment Information field of the age rating questionnaire.",{"question":448,"answer":449},"What is the deadline?","Apple's March 26, 2026 post says existing apps must provide a status by early 2027, and that if you haven't declared by then you will no longer be able to submit app updates. Apple gives no exact date in the pages I read, so declare now and don't wait for one.",{"question":451,"answer":452},"What do I select if my app is not a medical device?","Apple says to select No. In the declaration steps, selecting No and clicking Save completes the process. If your app has health features and you aren't sure whether it counts as a regulated medical device, ask a regulatory adviser first. This is not legal or regulatory advice.",{"question":454,"answer":455},"What do customers see?","If you declare Yes, the EU SRN or FDA number, instructions for use URL, use statement and safety information you enter display to customers on your App Store product page. Apple says the information goes live on the App Store within 24 hours, or once the app is approved and released if it isn't live yet.",{"question":457,"answer":458},"Who can make the declaration in App Store Connect?","Apple's help page says the required role is Account Holder or Admin. You start from the app's App Information page, under App Store Regulations & Permits, and click Declare Regulated Medical Device.","Boynton Beach, FL",{"readingTimeStats":461},{"text":462,"minutes":463,"time":464,"words":465},"9 min read",8.495,509700,1699,true,"\u002Fblog\u002Fapp-store-medical-device-status-declaration-2027","app store regulated medical device status","9 min",[471,472,473,474,475],"app-store-google-play-deadlines-2026-2027","app-store-age-rating-questions-update-2026","mobile-app-development-healthcare-guide","google-fit-api-deprecated-health-connect-2026","ios-27-sdk-requirement-april-2027-xcode-27-flutter",{"title":5,"description":440},[478,480,483,485,487],{"title":479,"url":71},"Apple Developer News, Update on regulated medical device apps in the European Economic Area, United Kingdom, and United States (March 26, 2026)",{"title":481,"url":482},"App Store Connect Help, Declare regulated medical device status","https:\u002F\u002Fdeveloper.apple.com\u002Fhelp\u002Fapp-store-connect\u002Fmanage-app-information\u002Fdeclare-regulated-medical-device-status",{"title":484,"url":180},"European Commission, Medical devices sector (linked by Apple)",{"title":486,"url":186},"GOV.UK, Regulating medical devices in the UK (linked by Apple)",{"title":488,"url":192},"FDA, Medical devices (linked by Apple)","blog\u002Fapp-store-medical-device-status-declaration-2027","app store connect regulated medical device status, declare regulated medical device app store, apple medical device declaration 2027, health and fitness app store requirement, app store medical device eea uk us, flutter health app app store, general wellness app app store connect, app store connect cannot submit app update, fda eu mdr uk mhra app store, app store connect compliance 2027",[492,493,494,495,496],"Apple requires a regulated medical device status for apps distributed in the EEA, the UK or the US whose primary or secondary category is Health & Fitness or Medical, or whose Age Rating answer for Medical or Treatment Information is \"frequent\".","New apps needed it from March 26, 2026. Existing apps must declare by \"early 2027\", and Apple says that if you haven't, \"you'll no longer be able to submit app updates\". Apple gives no exact date.","If your app is not a regulated medical device, you select No, save, and you're done. If you select Yes, Apple asks for an EU SRN or FDA number, an instructions for use URL, a use statement and safety information.","Apple says the information you enter \"will display to customers on your App Store product page\", and that it goes live within 24 hours of saving.","Apple's pages don't define a general wellness app or tell you how to classify one. If classification is unclear, ask a regulatory adviser before you answer. This is not legal or regulatory advice.","https:\u002F\u002Fapp369.com\u002Fblog\u002Fapp-store-medical-device-status-declaration-2027\u002F","ZG-tlopMGtPdCEv7X78D9LDv3ub6Be29fQOa3NtXq2Y",[500,1349,1916,3046],{"id":501,"title":502,"author":503,"body":505,"category":438,"createdAt":1276,"description":1277,"disclosure":441,"extension":442,"faq":1278,"howTo":441,"lastVerified":441,"location":459,"meta":1294,"navigation":466,"ogImage":441,"path":1299,"primaryKeyword":1300,"readingTime":1301,"related":1302,"seo":1306,"sources":1307,"stem":1338,"tags":1339,"takeaways":1340,"updatedAt":1346,"url":1347,"__hash__":1348},"blog\u002Fblog\u002Fapp-store-google-play-deadlines-2026-2027.md","App Store and Google Play Deadlines for 2026 and 2027",{"name":7,"social":504},{"twitter":9},{"type":11,"value":506,"toc":1268},[507,513,516,521,525,1173,1185,1188,1199,1202,1206,1223,1226,1230,1246,1249,1253,1259,1261],[14,508,509,512],{},[17,510,511],{},"The App Store and Google Play requirements that affect mobile app owners in 2026 and 2027 fit in one table: Xcode 26 uploads since April 28, 2026, target API 36 and Play Billing Library 8 since August 31, 2026, 16 KB page size support from February 1, 2027, and five Firebase shutdowns between March 22 and September 30, 2027."," The table below is sorted by date, and every row links to the page where the platform states it.",[14,514,515],{},"I checked each one on October 18, 2026. Rows whose date has passed are marked \"In effect\".",[14,517,518,520],{},[17,519,28],{}," App369 is my studio. I build and fix Android and iOS apps, mostly in Flutter, and the last section mentions what I sell. Apple and Google don't pay me for anything on this page.",[31,522,524],{"id":523},"all-dates-in-order","All dates, in order",[36,526,527,544],{},[39,528,529],{},[42,530,531,533,536,539,541],{},[45,532,47],{},[45,534,535],{},"What changes",[45,537,538],{},"Status",[45,540,53],{},[45,542,543],{},"My guide",[55,545,546,572,595,621,645,667,689,719,744,770,795,821,843,869,891,915,939,960,984,1008,1033,1060,1081,1105,1128,1149],{},[42,547,548,551,557,560,567],{},[60,549,550],{},"January 31, 2026",[60,552,553,556],{},[17,554,555],{},"Apple."," Apple asked developers to answer the updated age rating questions in App Store Connect by this date, to avoid an interruption when submitting app updates. Affects: every app on the App Store.",[60,558,559],{},"In effect",[60,561,562],{},[69,563,566],{"href":564,"rel":565},"https:\u002F\u002Fdeveloper.apple.com\u002Fnews\u002Fupcoming-requirements\u002F",[73],"Apple",[60,568,569],{},[69,570,571],{"href":136},"Age rating questions",[42,573,574,577,582,584,589],{},[60,575,576],{},"April 28, 2026",[60,578,579,581],{},[17,580,555],{}," Uploads to App Store Connect must be built with Xcode 26 or later, using an SDK for iOS 26, iPadOS 26, tvOS 26, visionOS 26 or watchOS 26. Affects: anyone uploading a build, including Flutter apps.",[60,583,559],{},[60,585,586],{},[69,587,566],{"href":564,"rel":588},[73],[60,590,591],{},[69,592,594],{"href":593},"\u002Fblog\u002Fitms-90725-sdk-version-issue-xcode-26-flutter-2026\u002F","ITMS-90725 and Xcode 26",[42,596,597,600,606,608,615],{},[60,598,599],{},"August 31, 2026",[60,601,602,605],{},[17,603,604],{},"Google Play."," New apps and app updates must target Android 16 (API level 36) or higher. Wear OS and Android Automotive OS apps need API 35, and Android XR apps need API 34. Affects: anyone publishing a new app or an update.",[60,607,559],{},[60,609,610],{},[69,611,614],{"href":612,"rel":613},"https:\u002F\u002Fsupport.google.com\u002Fgoogleplay\u002Fandroid-developer\u002Fanswer\u002F11926878",[73],"Play Console Help",[60,616,617],{},[69,618,620],{"href":619},"\u002Fblog\u002Fgoogle-play-target-api-36-android-16-requirement-2026\u002F","Target API 36",[42,622,623,625,630,632,639],{},[60,624,599],{},[60,626,627,629],{},[17,628,604],{}," New apps and updates must use Play Billing Library 8 or later. Version 7 is no longer accepted by default. Affects: apps with in-app purchases or subscriptions.",[60,631,559],{},[60,633,634],{},[69,635,638],{"href":636,"rel":637},"https:\u002F\u002Fdeveloper.android.com\u002Fgoogle\u002Fplay\u002Fbilling\u002Fdeprecation-faq",[73],"Android Developers",[60,640,641],{},[69,642,644],{"href":643},"\u002Fblog\u002Fplay-billing-library-7-deprecated-update-to-8-2026\u002F","Billing Library 8",[42,646,647,650,655,657,663],{},[60,648,649],{},"September 2026",[60,651,652,654],{},[17,653,555],{}," Answers to the new social media questions in the age rating questionnaire are required when submitting new apps or updates, or apps for notarization for alternative distribution. Apple gives the month, not a day. Affects: every app on the App Store.",[60,656,559],{},[60,658,659],{},[69,660,566],{"href":661,"rel":662},"https:\u002F\u002Fdeveloper.apple.com\u002Fnews\u002F?id=tlur8uvi",[73],[60,664,665],{},[69,666,571],{"href":136},[42,668,669,672,677,679,684],{},[60,670,671],{},"September 9, 2026",[60,673,674,676],{},[17,675,555],{}," iOS and iPadOS apps uploaded to App Store Connect must target iOS 13 or later. Affects: anyone uploading an iOS or iPadOS build.",[60,678,559],{},[60,680,681],{},[69,682,566],{"href":564,"rel":683},[73],[60,685,686],{},[69,687,688],{"href":111},"iOS 27 SDK checklist",[42,690,691,694,699,701,713],{},[60,692,693],{},"September 14, 2026",[60,695,696,698],{},[17,697,555],{}," Xcode 27 was released. Flutter's docs say Apple mandates the UIScene life cycle for UIKit apps built with the iOS 27 SDK, and that Flutter apps built with Xcode 27 without it fail to launch. Affects: anyone building with Xcode 27, including Flutter apps with a custom AppDelegate.",[60,700,559],{},[60,702,703,708,709],{},[69,704,707],{"href":705,"rel":706},"https:\u002F\u002Fdocs.flutter.dev\u002Frelease\u002Fbreaking-changes\u002Fuiscenedelegate",[73],"Flutter docs",", ",[69,710,566],{"href":711,"rel":712},"https:\u002F\u002Fdeveloper.apple.com\u002Fnews\u002Freleases\u002F",[73],[60,714,715],{},[69,716,718],{"href":717},"\u002Fblog\u002Fflutter-uiscene-migration-xcode-27-app-wont-launch-2026\u002F","UIScene migration",[42,720,721,724,730,732,738],{},[60,722,723],{},"September 30, 2026",[60,725,726,729],{},[17,727,728],{},"Google Play \u002F Android."," Developer verification protections begin for apps installed from participating stores in Brazil, Indonesia, Singapore and Thailand on certified devices running Android 7 or higher. Affects: anyone distributing Android apps.",[60,731,559],{},[60,733,734],{},[69,735,638],{"href":736,"rel":737},"https:\u002F\u002Fdeveloper.android.com\u002Fdeveloper-verification",[73],[60,739,740],{},[69,741,743],{"href":742},"\u002Fblog\u002Fandroid-developer-verification-requirement-2026\u002F","Developer verification",[42,745,746,749,755,758,765],{},[60,747,748],{},"October 30, 2026",[60,750,751,754],{},[17,752,753],{},"Google APIs."," Google says the legacy Fitbit Web API will be turned off and will no longer function or sync data. Support already ended on September 30, 2026. Affects: apps that read Fitbit data through the Fitbit Web API.",[60,756,757],{},"Upcoming",[60,759,760],{},[69,761,764],{"href":762,"rel":763},"https:\u002F\u002Fdevelopers.google.com\u002Fhealth",[73],"Google Health API",[60,766,767],{},[69,768,769],{"href":392},"Google Fit to Health Connect",[42,771,772,774,780,782,789],{},[60,773,748],{},[60,775,776,779],{},[17,777,778],{},"Supabase."," New tables in the public schema stop getting automatic Data API access in existing projects, so they need an explicit grant. Affects: apps with a Supabase backend.",[60,781,757],{},[60,783,784],{},[69,785,788],{"href":786,"rel":787},"https:\u002F\u002Fsupabase.com\u002Fchangelog\u002F45329-breaking-change-tables-not-exposed-to-data-and-graphql-api-automatically",[73],"Supabase",[60,790,791],{},[69,792,794],{"href":793},"\u002Fblog\u002Fsupabase-permission-denied-new-tables-october-30-2026\u002F","Supabase permission denied",[42,796,797,800,805,807,815],{},[60,798,799],{},"November 1, 2026",[60,801,802,804],{},[17,803,604],{}," End of the extension Google offers for the target API 36 and Billing Library 7 deadlines. Affects: anyone who requested an extension.",[60,806,757],{},[60,808,809,708,812],{},[69,810,614],{"href":612,"rel":811},[73],[69,813,638],{"href":636,"rel":814},[73],[60,816,817,708,819],{},[69,818,620],{"href":619},[69,820,644],{"href":643},[42,822,823,826,831,833,839],{},[60,824,825],{},"End of 2026",[60,827,828,830],{},[17,829,753],{}," The Google Fit APIs, including the REST API, are supported only until the end of 2026. Affects: apps that read fitness data through Google Fit.",[60,832,757],{},[60,834,835],{},[69,836,638],{"href":837,"rel":838},"https:\u002F\u002Fdeveloper.android.com\u002Fhealth-and-fitness\u002Fhealth-connect\u002Fmigration\u002Ffit",[73],[60,840,841],{},[69,842,769],{"href":392},[42,844,845,848,854,856,863],{},[60,846,847],{},"January 1, 2027",[60,849,850,853],{},[17,851,852],{},"Firebase."," New users can no longer start using the FCM InstanceId server APIs and device groups. Firebase says new users can onboard before this date. Affects: new integrations that use those APIs.",[60,855,757],{},[60,857,858],{},[69,859,862],{"href":860,"rel":861},"https:\u002F\u002Ffirebase.google.com\u002Fdocs\u002Fcloud-messaging\u002Ftroubleshooting",[73],"Firebase",[60,864,865],{},[69,866,868],{"href":867},"\u002Fblog\u002Ffcm-legacy-api-shutdown-http-v1-migration-2026\u002F","FCM migration",[42,870,871,873,878,880,885],{},[60,872,81],{},[60,874,875,877],{},[17,876,555],{}," Existing apps in the EEA, UK or US whose category is Health & Fitness or Medical, or that are marked in the age rating questionnaire as containing frequent Medical or Treatment Information, must declare a regulated medical device status in App Store Connect. Without it, you can no longer submit app updates. New apps have needed it since March 26, 2026. Apple gives no exact date. Affects: health, fitness and medical apps.",[60,879,757],{},[60,881,882],{},[69,883,566],{"href":71,"rel":884},[73],[60,886,887],{},[69,888,890],{"href":889},"\u002Fblog\u002Fapp-store-medical-device-status-declaration-2027\u002F","Medical device status",[42,892,893,896,901,903,909],{},[60,894,895],{},"January 27, 2027",[60,897,898,900],{},[17,899,604],{}," Four sensitive-permission changes take effect: the Contacts Permissions policy (use the Android Contact Picker unless the app needs broad access), the location button as the minimum for one-time precise location, no READ_CALL_LOG for phone-call account verification, and no geofencing as a foreground service use case. Google ties the contacts and location rules to apps that target Android 17 (API level 37) or later; its call log and geofencing pages give no target API. A 30-day self extension is available in Play Console. Affects: apps that request READ_CONTACTS, ACCESS_FINE_LOCATION or READ_CALL_LOG, or run geofencing in a foreground service.",[60,902,757],{},[60,904,905],{},[69,906,614],{"href":907,"rel":908},"https:\u002F\u002Fsupport.google.com\u002Fgoogleplay\u002Fandroid-developer\u002Ftable\u002F12921780",[73],[60,910,911],{},[69,912,914],{"href":913},"\u002Fblog\u002Fgoogle-play-contacts-permissions-policy-2027\u002F","Play permission changes",[42,916,917,920,925,927,933],{},[60,918,919],{},"February 1, 2027",[60,921,922,924],{},[17,923,604],{}," Updates that don't support 16 KB memory page sizes can't be released, for apps targeting Android 15 (API level 35) and higher. Affects: apps with native code, which includes Flutter apps.",[60,926,757],{},[60,928,929],{},[69,930,638],{"href":931,"rel":932},"https:\u002F\u002Fdeveloper.android.com\u002Fguide\u002Fpractices\u002Fpage-sizes",[73],[60,934,935],{},[69,936,938],{"href":937},"\u002Fblog\u002Fgoogle-play-16kb-page-size-flutter-android-2026\u002F","16 KB page size",[42,940,941,944,949,951,956],{},[60,942,943],{},"2027 (no month stated)",[60,945,946,948],{},[17,947,728],{}," Developer verification capability expands globally for all apps on certified Android devices. Affects: anyone distributing Android apps.",[60,950,757],{},[60,952,953],{},[69,954,638],{"href":736,"rel":955},[73],[60,957,958],{},[69,959,743],{"href":742},[42,961,962,965,970,972,978],{},[60,963,964],{},"March 22, 2027",[60,966,967,969],{},[17,968,852],{}," Firebase Studio shuts down and remaining data is permanently deleted. Affects: anyone with a Firebase Studio workspace.",[60,971,757],{},[60,973,974],{},[69,975,862],{"href":976,"rel":977},"https:\u002F\u002Ffirebase.google.com\u002Fdocs\u002Fstudio\u002Fmigrating-project",[73],[60,979,980],{},[69,981,983],{"href":982},"\u002Fblog\u002Ffirebase-studio-shutting-down-migrate-project-2027\u002F","Firebase Studio shutdown",[42,985,986,989,994,996,1002],{},[60,987,988],{},"March 31, 2027",[60,990,991,993],{},[17,992,852],{}," Firebase Extensions service shuts down. Installed extensions keep running, but you lose the ability to update, reconfigure or uninstall them through the console or CLI. Affects: apps with installed extensions.",[60,995,757],{},[60,997,998],{},[69,999,862],{"href":1000,"rel":1001},"https:\u002F\u002Ffirebase.google.com\u002Fdocs\u002Fextensions\u002Ffaq-and-troubleshooting",[73],[60,1003,1004],{},[69,1005,1007],{"href":1006},"\u002Fblog\u002Ffirebase-extensions-shutting-down-replace-2027\u002F","Firebase Extensions shutdown",[42,1009,1010,1013,1018,1020,1026],{},[60,1011,1012],{},"April 2027",[60,1014,1015,1017],{},[17,1016,555],{}," Apps uploaded to App Store Connect must be built with the iOS 27 and iPadOS 27 SDK or later (tvOS, visionOS and watchOS 27 SDKs for those platforms). Apple gives the month, not a day. Affects: every iOS and Flutter app that ships an update.",[60,1019,757],{},[60,1021,1022],{},[69,1023,566],{"href":1024,"rel":1025},"https:\u002F\u002Fdeveloper.apple.com\u002Fnews\u002F?id=k1mtkt1k",[73],[60,1027,1028,708,1030],{},[69,1029,688],{"href":111},[69,1031,1032],{"href":717},"UIScene and Xcode 27",[42,1034,1035,1037,1042,1044,1056],{},[60,1036,1012],{},[60,1038,1039,1041],{},[17,1040,555],{}," Apple's news post says any app or game submitted must include screenshots for iPhone Duo. Its screenshot specifications page says they will be required for any app using the iOS 27.1 SDK or later. Apple gives the month, not a day. Affects: App Store submissions.",[60,1043,757],{},[60,1045,1046,708,1051],{},[69,1047,1050],{"href":1048,"rel":1049},"https:\u002F\u002Fdeveloper.apple.com\u002Fnews\u002F?id=kkphp5qo",[73],"Apple news",[69,1052,1055],{"href":1053,"rel":1054},"https:\u002F\u002Fdeveloper.apple.com\u002Fhelp\u002Fapp-store-connect\u002Freference\u002Fapp-information\u002Fscreenshot-specifications",[73],"Apple specs",[60,1057,1058],{},[69,1059,688],{"href":111},[42,1061,1062,1064,1069,1071,1077],{},[60,1063,1012],{},[60,1065,1066,1068],{},[17,1067,555],{}," Apple's submitting page says iOS and iPadOS apps uploaded to App Store Connect must target iOS 15 or later. The upcoming requirements page still lists iOS 13 as the minimum since September 9, 2026. Apple gives the month, not a day. Affects: apps whose deployment target is iOS 13 or 14.",[60,1070,757],{},[60,1072,1073],{},[69,1074,566],{"href":1075,"rel":1076},"https:\u002F\u002Fdeveloper.apple.com\u002Fapp-store\u002Fsubmitting\u002F",[73],[60,1078,1079],{},[69,1080,688],{"href":111},[42,1082,1083,1086,1091,1093,1099],{},[60,1084,1085],{},"June 15, 2027",[60,1087,1088,1090],{},[17,1089,852],{}," Firebase ML custom model hosting shuts down. Affects: apps that host custom models in Firebase ML.",[60,1092,757],{},[60,1094,1095],{},[69,1096,862],{"href":1097,"rel":1098},"https:\u002F\u002Ffirebase.google.com\u002Fdocs\u002Fml\u002Fmigrate-to-cloud-storage",[73],[60,1100,1101],{},[69,1102,1104],{"href":1103},"\u002Fblog\u002Ffirebase-ml-model-hosting-shutting-down-migrate-2027\u002F","Firebase ML model hosting shutdown",[42,1106,1107,1110,1115,1117,1122],{},[60,1108,1109],{},"August 31, 2027",[60,1111,1112,1114],{},[17,1113,604],{}," Billing Library 8 reaches its own deadline. New apps and updates must use Billing Library 9 or later. Extension available until November 1, 2027. Affects: apps with in-app purchases or subscriptions.",[60,1116,757],{},[60,1118,1119],{},[69,1120,638],{"href":636,"rel":1121},[73],[60,1123,1124],{},[69,1125,1127],{"href":1126},"\u002Fblog\u002Fplay-billing-library-9-migration-deadline-2027\u002F","Billing Library 9",[42,1129,1130,1133,1138,1140,1145],{},[60,1131,1132],{},"September 29, 2027",[60,1134,1135,1137],{},[17,1136,852],{}," The FCM InstanceId server APIs and device groups are decommissioned. Affects: servers that manage topics or tokens through the old APIs.",[60,1139,757],{},[60,1141,1142],{},[69,1143,862],{"href":860,"rel":1144},[73],[60,1146,1147],{},[69,1148,868],{"href":867},[42,1150,1151,1154,1159,1161,1167],{},[60,1152,1153],{},"September 30, 2027",[60,1155,1156,1158],{},[17,1157,852],{}," Firebase Test Lab is fully shut down. Affects: CI pipelines that run tests on Test Lab.",[60,1160,757],{},[60,1162,1163],{},[69,1164,862],{"href":1165,"rel":1166},"https:\u002F\u002Ffirebase.google.com\u002Fdocs\u002Ftest-lab",[73],[60,1168,1169],{},[69,1170,1172],{"href":1171},"\u002Fblog\u002Ffirebase-test-lab-shutting-down-alternatives-2027\u002F","Firebase Test Lab shutdown",[14,1174,1175,1176,1180,1181,1184],{},"Two more notes. Apple's privacy manifest rules (May 1, 2024 for required reason APIs and February 12, 2025 for common SDKs, see the ",[69,1177,1179],{"href":1178},"\u002Fblog\u002Fapple-privacy-manifest-itms-91053-itms-91061-flutter-fix-2026\u002F","privacy manifest guide",") and the FCM legacy send shutdown (July 22, 2024, see the ",[69,1182,1183],{"href":867},"FCM migration guide",") already passed before 2026. I keep them in their own guides because they still cause upload and delivery errors.",[31,1186,566],{"id":1187},"apple",[14,1189,1190,1191,708,1193,1195,1196,113],{},"Apple's page names one build rule that matters most: Xcode 26 or later since April 28, 2026. Apple's September 9, 2026 news post adds the next one: starting April 2027, uploads must be built with the iOS 27 and iPadOS 27 SDK or later, which means Xcode 27. Apple's October 5, 2026 post also says that from April 2027 every submission needs iPhone Duo screenshots. The bigger change with Xcode 27 is the UIScene life cycle, which a Flutter app on 3.41 or later with an unmodified AppDelegate gets automatically. A custom AppDelegate needs manual changes. The guides are ",[69,1192,594],{"href":593},[69,1194,1032],{"href":717}," and ",[69,1197,1198],{"href":1178},"privacy manifest errors",[14,1200,1201],{},"My advice: check which Xcode your build machine uses before your next upload, and test a build with Xcode 27 before you need one.",[31,1203,1205],{"id":1204},"google-play-and-android","Google Play and Android",[14,1207,1208,1209,1212,1213,708,1216,708,1218,1195,1220,113],{},"The Play rules come in pairs. Target API 36 and Billing Library 8 both took effect on August 31, 2026 with an extension to November 1, 2026. After that, February 1, 2027 brings the 16 KB page size rule, and on August 31, 2027 Google requires Billing Library 9 or later for new apps and updates. The ",[69,1210,1211],{"href":1126},"Billing Library 9 guide"," covers that move. Separately, Android developer verification started on September 30, 2026 in four countries, with a global expansion in 2027. The guides are ",[69,1214,1215],{"href":619},"target API 36",[69,1217,938],{"href":937},[69,1219,644],{"href":643},[69,1221,1222],{"href":742},"developer verification",[14,1224,1225],{},"My advice: if you are still behind on API 36 or Billing 8, ship that update before November 1, 2026. Then do the 16 KB check before February 1, 2027, since it is the next date that can block a release.",[31,1227,1229],{"id":1228},"firebase-and-google-apis","Firebase and Google APIs",[14,1231,1232,1233,708,1237,708,1240,1242,1243,113],{},"Firebase has five shutdown dates in 2027, plus the January 1 cutoff for new users of the InstanceId APIs. Firestore, Authentication, Cloud Functions and Hosting are not on the list. Google Fit APIs are supported only until the end of 2026, and Google points to Health Connect and the Google Health API. The legacy Fitbit Web API goes first: Google says it will be turned off on October 30, 2026. The guides are ",[69,1234,1236],{"href":1235},"\u002Fblog\u002Ffirebase-deprecations-shutdown-dates-2026\u002F","Firebase shutdown dates",[69,1238,1239],{"href":867},"FCM HTTP v1 migration",[69,1241,769],{"href":392}," and, if you use it, ",[69,1244,1245],{"href":793},"Supabase new table permissions",[14,1247,1248],{},"My advice: open the Firebase console for every project you own and look at Extensions, Machine Learning, Test Lab and Studio. Those are the products with a date attached.",[31,1250,1252],{"id":1251},"how-i-keep-this-page-current","How I keep this page current",[14,1254,1255,1256,113],{},"Every row links to the page where the platform states the date. If a source says only a month or \"later this year\", I write exactly that. When a platform moves a date, I change the row and the updated date at the top of this page. If you spot a date that looks wrong, ",[69,1257,1258],{"href":421},"tell me",[31,1260,410],{"id":409},[14,1262,1263,1264,418,1266,113],{},"If one of these deadlines lands on an app you can't update yourself, the ",[69,1265,417],{"href":416},[69,1267,422],{"href":421},{"title":424,"searchDepth":425,"depth":425,"links":1269},[1270,1271,1272,1273,1274,1275],{"id":523,"depth":425,"text":524},{"id":1187,"depth":425,"text":566},{"id":1204,"depth":425,"text":1205},{"id":1228,"depth":425,"text":1229},{"id":1251,"depth":425,"text":1252},{"id":409,"depth":425,"text":410},"2026-10-18T22:00:00.000Z","One dated table of the App Store, Google Play, Firebase and Google API requirements that affect mobile app owners in 2026 and 2027, with the primary source for each date, checked October 18, 2026.",[1279,1282,1285,1288,1291],{"question":1280,"answer":1281},"What is the next Google Play deadline?","The deadline of November 1, 2026 is the end of the extension window for the target API 36 and Billing Library 7 deadlines. After that, the next one is February 1, 2027, when Google says app updates that don't support 16 KB memory page sizes can't be released.",{"question":1283,"answer":1284},"What Xcode version does the App Store require?","Apple's upcoming requirements page says that since April 28, 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later using an SDK for iOS 26, iPadOS 26, tvOS 26, visionOS 26 or watchOS 26. Apple's September 9, 2026 news post adds the next one: starting April 2027, iOS and iPadOS apps must be built with the iOS 27 and iPadOS 27 SDK or later. Apple gives the month, not a day.",{"question":1286,"answer":1287},"Do these deadlines apply to apps already published?","It depends on the rule. Google says existing apps must target API 35 or higher to stay available to new users on newer Android versions, and existing apps keep working on version 7 of Play Billing until you ship an update. Most upload-side rules, such as the Xcode SDK minimum, apply when you submit a new build.",{"question":1289,"answer":1290},"Which deadlines affect a Flutter app?","Nearly all of the Apple and Google Play rows do, because a Flutter app is a normal iOS and Android app underneath. The Firebase rows apply only if you use that Firebase product. The Supabase row applies only if you use Supabase.",{"question":1292,"answer":1293},"How will I know if a date changes?","Each row links to the page where the platform states the date, and I list the date I checked it. Dates can move, so check the linked page before you plan around one. I update this page when a platform changes a date.",{"readingTimeStats":1295},{"text":462,"minutes":1296,"time":1297,"words":1298},8.92,535200,1784,"\u002Fblog\u002Fapp-store-google-play-deadlines-2026-2027","app store deadlines 2026","6 min",[1303,1304,1305],"google-play-target-api-36-android-16-requirement-2026","itms-90725-sdk-version-issue-xcode-26-flutter-2026","firebase-deprecations-shutdown-dates-2026",{"title":502,"description":1277},[1308,1310,1312,1314,1316,1318,1320,1322,1324,1326,1328,1330,1332,1334,1336],{"title":1309,"url":762},"Google for Developers, Google Health API (Fitbit Web API dates)",{"title":1311,"url":564},"Apple Developer, Upcoming requirements",{"title":1313,"url":711},"Apple Developer, Releases",{"title":1315,"url":705},"Flutter docs, Migrate to UIScene life cycle",{"title":1317,"url":612},"Play Console Help, Target API level requirements for Google Play apps",{"title":1319,"url":636},"Android Developers, Play Billing Library deprecation FAQ",{"title":1321,"url":931},"Android Developers, Support 16 KB page sizes",{"title":1323,"url":736},"Android Developers, Android developer verification",{"title":1325,"url":837},"Android Developers, Migrate from the Google Fit APIs",{"title":1327,"url":860},"Firebase, FCM troubleshooting (InstanceId and device groups deprecation)",{"title":1329,"url":976},"Firebase, Migrate from Firebase Studio",{"title":1331,"url":1000},"Firebase, Extensions FAQ and troubleshooting",{"title":1333,"url":1097},"Firebase, Migrate Firebase ML model hosting to Cloud Storage",{"title":1335,"url":1165},"Firebase, Test Lab",{"title":1337,"url":786},"Supabase changelog, Tables not exposed to the Data API automatically","blog\u002Fapp-store-google-play-deadlines-2026-2027","app store deadlines 2026, google play deadlines 2026, app store requirements 2027, google play requirements 2027, target api 36 deadline, play billing library 8 deadline, 16 kb page size deadline, xcode 26 requirement, firebase shutdown dates, mobile app compliance calendar",[1341,1342,1343,1344,1345],"Most 2026 deadlines have already hit. Since April 28, 2026 iOS uploads need Xcode 26 or later, and since August 31, 2026 Google Play needs new apps and updates to target API 36 and use Play Billing Library 8.","Google lets you request an extension for both Play deadlines until November 1, 2026. That is the last date to ship an update if you are still behind.","The next hard date for Android is February 1, 2027. Google says updates that don't support 16 KB memory page sizes can't be released after that.","On iOS, apps built with Xcode 27 must use the UIScene life cycle or they fail to launch. Xcode 27 was released on September 14, 2026.","Firebase has five shutdowns between March 22 and September 30, 2027. Core services such as Firestore and Authentication are not on the list.","2026-10-19T09:00:00.000Z","https:\u002F\u002Fapp369.com\u002Fblog\u002Fapp-store-google-play-deadlines-2026-2027\u002F","7iLEy6X2NFre6xDWHiYbB0u9V57CZXRUPhPb7TWJM4w",{"id":1350,"title":1351,"author":1352,"body":1354,"category":438,"createdAt":1847,"description":1848,"disclosure":441,"extension":442,"faq":1849,"howTo":441,"lastVerified":441,"location":459,"meta":1865,"navigation":466,"ogImage":441,"path":1871,"primaryKeyword":1872,"readingTime":1873,"related":1874,"seo":1878,"sources":1879,"stem":1906,"tags":1907,"takeaways":1908,"updatedAt":1847,"url":1914,"__hash__":1915},"blog\u002Fblog\u002Fapp-store-age-rating-questions-update-2026.md","Apple Age Rating Questions Update: What to Answer",{"name":7,"social":1353},{"twitter":9},{"type":11,"value":1355,"toc":1836},[1356,1362,1365,1370,1372,1472,1475,1479,1482,1520,1523,1526,1530,1533,1538,1552,1557,1589,1594,1608,1613,1636,1639,1643,1646,1666,1669,1672,1675,1679,1682,1704,1707,1710,1714,1717,1762,1765,1768,1772,1775,1778,1781,1785,1823,1827,1829],[14,1357,1358,1361],{},[17,1359,1360],{},"Apple's updated age rating system adds 13+, 16+ and 18+ to the existing 4+ and 9+ ratings, and Apple asked developers to answer the new questions for every app by January 31, 2026."," Apple's own pages warn of \"an interruption when submitting your app updates\", and Apple's reminder email, as a developer posted it on the Apple Developer Forums, said you wouldn't be able to submit app updates in App Store Connect. If you haven't answered yet, do it before your next build goes up.",[14,1363,1364],{},"The facts below come from Apple Developer News, App Store Connect Help and the App Review Guidelines, as shown in the sources. I checked each one on October 18, 2026. Apple can change a rule, so open the linked page before you plan around it.",[14,1366,1367,1369],{},[17,1368,28],{}," App369 is my studio. I build and fix Flutter and Firebase apps, and the last section mentions what I sell. Apple doesn't pay me for anything on this page.",[31,1371,34],{"id":33},[36,1373,1374,1385],{},[39,1375,1376],{},[42,1377,1378,1380,1383],{},[45,1379,47],{},[45,1381,1382],{},"What happened",[45,1384,53],{},[55,1386,1387,1402,1417,1431,1445,1458],{},[42,1388,1389,1392,1395],{},[60,1390,1391],{},"July 24, 2025",[60,1393,1394],{},"Apple announced the updated ratings and the new required questions, with a January 31, 2026 response date",[60,1396,1397],{},[69,1398,1401],{"href":1399,"rel":1400},"https:\u002F\u002Fdeveloper.apple.com\u002Fnews\u002F?id=ks775ehf",[73],"Apple News",[42,1403,1404,1407,1410],{},[60,1405,1406],{},"January 1, 2026",[60,1408,1409],{},"Texas SB2420 takes effect. Apple's reminder says an age rating change for apps distributed in Texas would be a significant change",[60,1411,1412],{},[69,1413,1416],{"href":1414,"rel":1415},"https:\u002F\u002Fdeveloper.apple.com\u002Fforums\u002Fthread\u002F810295",[73],"Forums, reminder email",[42,1418,1419,1423,1426],{},[60,1420,1421],{},[17,1422,550],{},[60,1424,1425],{},"Response date for the updated questions. Without answers you can't submit app updates",[60,1427,1428],{},[69,1429,1416],{"href":1414,"rel":1430},[73],[42,1432,1433,1436,1439],{},[60,1434,1435],{},"June 8, 2026",[60,1437,1438],{},"Apple announced Time Allowances and said the questionnaire would add social media questions",[60,1440,1441],{},[69,1442,1401],{"href":1443,"rel":1444},"https:\u002F\u002Fdeveloper.apple.com\u002Fnews\u002F?id=0d2gpmml",[73],[42,1446,1447,1450,1453],{},[60,1448,1449],{},"July 9, 2026",[60,1451,1452],{},"Social media capability questions added to the questionnaire",[60,1454,1455],{},[69,1456,1401],{"href":661,"rel":1457},[73],[42,1459,1460,1464,1467],{},[60,1461,1462],{},[17,1463,649],{},[60,1465,1466],{},"Responses to the social media question required to submit new apps or updates",[60,1468,1469],{},[69,1470,1401],{"href":661,"rel":1471},[73],[14,1473,1474],{},"Apple's Upcoming Requirements page also says ratings for all apps and games on the App Store were automatically updated to the new system. They show on devices running iOS 26, iPadOS 26, macOS Tahoe 26, tvOS 26, visionOS 26 and watchOS 26 or later.",[31,1476,1478],{"id":1477},"the-new-tiers","The new tiers",[14,1480,1481],{},"The default tiers on Apple's definitions page are 4+, 9+, 13+, 16+ and 18+, plus Unrated. A few examples of what sits at each level, taken from that page:",[122,1483,1484,1490,1496,1502,1508,1514],{},[125,1485,1486,1489],{},[17,1487,1488],{},"4+:"," for example parental controls, age assurance, user-generated content, messaging and chat, advertising and infrequent contests.",[125,1491,1492,1495],{},[17,1493,1494],{},"9+:"," for example infrequent horror themes, health and wellness topics, infrequent cartoon or fantasy violence and loot boxes.",[125,1497,1498,1501],{},[17,1499,1500],{},"13+:"," for example social media, frequent profanity, infrequent medical or treatment information and infrequent realistic violence.",[125,1503,1504,1507],{},[17,1505,1506],{},"16+:"," unrestricted web access, frequent medical or treatment information and frequent mature or suggestive themes.",[125,1509,1510,1513],{},[17,1511,1512],{},"18+:"," for example gambling, frequent realistic violence and frequent sexual content or nudity.",[125,1515,1516,1519],{},[17,1517,1518],{},"Unrated:"," graphic sexual content or prolonged graphic or sadistic realistic violence. Apple's help page says an Unrated app can't be published on the App Store.",[14,1521,1522],{},"Ratings are assigned per country or region. Apple has since made region-specific changes. From June 18, 2026 the 15+ rating is no longer available in Australia, and Vietnam apps get a region-specific rating of 00+, 12+, 16+ or 18+. Apple's definitions page also says that in Australia, apps with social media capabilities or loot boxes display 16+. I'm not covering Brazil or Korea in detail, so read Apple's posts if you sell there. For Korea, Apple's August 12, 2026 post says two descriptors move from All to 12+ starting October 2026.",[14,1524,1525],{},"My advice: don't guess a tier from the old system. Answer the questions and let Apple's calculation show you the result.",[31,1527,1529],{"id":1528},"what-the-new-questions-cover","What the new questions cover",[14,1531,1532],{},"Apple's July 2025 post says the new required questions cover in-app controls, capabilities, medical or wellness topics and violent themes. Apple's definitions page lists these categories, with the definitions I quote or paraphrase below.",[14,1534,1535],{},[17,1536,1537],{},"In-app controls",[122,1539,1540,1546],{},[125,1541,1542,1545],{},[17,1543,1544],{},"Parental controls:"," settings or tools that let parents monitor, manage or restrict a child's access, such as content filtering, usage limits or purchase restrictions.",[125,1547,1548,1551],{},[17,1549,1550],{},"Age assurance:"," a mechanism to confirm someone's age meets the requirement for content or services. Apple's examples include the Declared Age Range API, age estimation and age verification by government-issued ID.",[14,1553,1554],{},[17,1555,1556],{},"Capabilities",[122,1558,1559,1565,1571,1577,1583],{},[125,1560,1561,1564],{},[17,1562,1563],{},"Unrestricted web access:"," users can navigate to any webpage in the app or freely browse. Apple says this may include embedded browser functionality.",[125,1566,1567,1570],{},[17,1568,1569],{},"User-generated content:"," broad distribution of content users create, such as videos, photos, text or audio.",[125,1572,1573,1576],{},[17,1574,1575],{},"Messaging and chat:"," users can directly communicate through features in the app, including text, voice or video chat, direct or group messaging, or public posting.",[125,1578,1579,1582],{},[17,1580,1581],{},"Advertising:"," paid promotion of products or services in the app, including banner, video, playable, rich media and native ads.",[125,1584,1585,1588],{},[17,1586,1587],{},"Social media:"," added July 9, 2026. Apple defines it as the ability to redistribute, amplify or interact with user-generated content through a social feed or similar discovery method.",[14,1590,1591],{},[17,1592,1593],{},"Medical or wellness",[122,1595,1596,1602],{},[125,1597,1598,1601],{},[17,1599,1600],{},"Medical or treatment information:"," diagnoses or guidance on managing medical conditions, such as medication guidance or emergency care.",[125,1603,1604,1607],{},[17,1605,1606],{},"Health or wellness topics:"," self-care or lifestyle recommendations, such as calorie tracking, dieting advice or exercise recommendations.",[14,1609,1610],{},[17,1611,1612],{},"Violence",[122,1614,1615,1621,1627],{},[125,1616,1617,1620],{},[17,1618,1619],{},"Cartoon or fantasy violence"," is exaggerated or fantastical and easily distinguished from real life.",[125,1622,1623,1626],{},[17,1624,1625],{},"Realistic violence"," is aggressive physical conflict or harm involving humans in lifelike situations.",[125,1628,1629,1195,1632,1635],{},[17,1630,1631],{},"Guns or other weapons",[17,1633,1634],{},"prolonged graphic or sadistic realistic violence"," are listed as separate items.",[14,1637,1638],{},"The same page also covers mature themes, sexuality or nudity, and chance-based activities such as gambling, simulated gambling, contests and loot boxes. For these, you choose a frequency, either Infrequent or Frequent. I didn't find a definition of those two words on Apple's page, so pick the answer that honestly matches how often the content appears in the shipped app.",[31,1640,1642],{"id":1641},"what-happens-if-you-didnt-answer","What happens if you didn't answer",[14,1644,1645],{},"The sources word this in three ways, and I'll keep them separate.",[267,1647,1648,1654,1660],{},[125,1649,1650,1653],{},[17,1651,1652],{},"Apple's Upcoming Requirements page:"," provide responses by January 31, 2026 \"to avoid an interruption when submitting your app updates in App Store Connect.\" It doesn't describe the interruption.",[125,1655,1656,1659],{},[17,1657,1658],{},"Apple's reminder email,"," as a developer reproduced it on the Apple Developer Forums in December 2025: \"If you don't answer these questions by January 31, 2026, you won't be able to submit app updates in App Store Connect.\"",[125,1661,1662,1665],{},[17,1663,1664],{},"Apple's July 9, 2026 post:"," from September 2026, responses to the social media questions are required when submitting new apps or updates, or when submitting apps for notarization for alternative distribution.",[14,1667,1668],{},"So the stated consequence is a blocked submission of updates. The pages I read don't say a live app is removed, and I found no Apple statement on what happens to an app that stays unanswered and never submits again. I would not assume either way.",[14,1670,1671],{},"I also can't give you a verified account of how App Store Connect behaves today, because I didn't test it on a live account. Open each app's App Information page to see its status.",[14,1673,1674],{},"My advice: don't discover this on release day. A blocked update during a bug fix is the worst time.",[31,1676,1678],{"id":1677},"how-to-answer-step-by-step","How to answer, step by step",[14,1680,1681],{},"Apple's help page gives the path:",[267,1683,1684,1687,1689,1692,1695,1698,1701],{},[125,1685,1686],{},"In App Store Connect, open the app.",[125,1688,274],{},[125,1690,1691],{},"Below Age Ratings, click Set Up Age Ratings.",[125,1693,1694],{},"Review the list of in-app controls and capabilities, select the ones your app includes, then click Next.",[125,1696,1697],{},"Work through each section, answering the questions and choosing a frequency for each content description.",[125,1699,1700],{},"Under Age Categories and Override, choose Not Applicable unless you need Made for Kids or a higher rating.",[125,1702,1703],{},"Click Save. You return to App Information, where you can see global and region-specific ratings.",[14,1705,1706],{},"To change it later, click Edit at the top of App Information. The required role is Account Holder, Admin, App Manager or Marketing.",[14,1708,1709],{},"Two limits are worth knowing. Apple's help page says you can't change the Made for Kids selection once App Review approves the app. And an override can only raise a rating, since the page describes it as increasing the rating above the one Apple assigned.",[31,1711,1713],{"id":1712},"how-to-answer-honestly-for-a-flutter-app","How to answer honestly for a Flutter app",[14,1715,1716],{},"Guideline 2.3.6 says to \"answer the age rating questions in App Store Connect honestly so that your app aligns properly with parental controls.\" It adds that a mis-rated app could surprise customers or trigger an inquiry from government regulators. In practice, I'd check these before I answer:",[122,1718,1719,1729,1735,1741,1747,1753],{},[125,1720,1721,1724,1725,1728],{},[17,1722,1723],{},"Web views."," A ",[386,1726,1727],{},"webview_flutter"," screen that loads only your own pages is different from a browser that can open any URL. Apple's definition of unrestricted web access is users navigating to any page or freely browsing.",[125,1730,1731,1734],{},[17,1732,1733],{},"Ads."," If you use an ad SDK, the app has advertising. Check the SDK, not just your own screens.",[125,1736,1737,1740],{},[17,1738,1739],{},"Chat and comments."," A support chat with your team is not the same as users messaging each other. Apple's definition is users communicating with one another.",[125,1742,1743,1746],{},[17,1744,1745],{},"Uploads."," If users post photos or text that other users can see, that is user-generated content.",[125,1748,1749,1752],{},[17,1750,1751],{},"Health content."," A water tracker and a medication guide are different answers. Calorie tracking and exercise recommendations are wellness examples on Apple's page. Medication guidance is a medical example.",[125,1754,1755,1758,1759,1761],{},[17,1756,1757],{},"Third-party packages."," A Flutter plugin can add a capability you never wrote. Skim your ",[386,1760,388],{}," before you answer.",[14,1763,1764],{},"If you have a minimum age in your EULA, Apple's help page says you must override to a rating that meets it.",[14,1766,1767],{},"My advice: print the list above, check your app against it once, and save your answers in your release notes so the next developer doesn't have to guess.",[31,1769,1771],{"id":1770},"social-media-and-the-texas-note","Social media and the Texas note",[14,1773,1774],{},"Apple says an app with social media capabilities gets a Social Media content descriptor and, per the June 8 post, a minimum age rating of 13+. If those capabilities are disabled for anyone under 13, the app isn't in the Social Media Time Allowance category for those users. That option requires the Declared Age Range API at a minimum to check users' age ranges, and your overall answers may then produce a rating lower than 13+.",[14,1776,1777],{},"Most small business apps have no feed, so this question will usually be a plain no. If you have a community feed with likes, comments and shares, read Apple's definition carefully.",[14,1779,1780],{},"The reminder email also said Texas SB2420 took effect January 1, 2026, and that changing an age rating for apps distributed in Texas would be a significant change that may trigger a consent process. If you serve Texas, treat a rating change as more than a form edit. I'm not a lawyer, and I haven't tested the consent flow.",[31,1782,1784],{"id":1783},"a-short-checklist","A short checklist",[267,1786,1787,1793,1799,1805,1811,1817],{},[125,1788,1789,1792],{},[17,1790,1791],{},"List every app"," under your account, including the old ones you rarely touch.",[125,1794,1795,1798],{},[17,1796,1797],{},"Open App Information"," for each and check whether the age rating setup is complete.",[125,1800,1801,1804],{},[17,1802,1803],{},"Answer from the shipped build,"," including SDKs, web views and ads.",[125,1806,1807,1810],{},[17,1808,1809],{},"Check the calculated rating"," for each region you sell in.",[125,1812,1813,1816],{},[17,1814,1815],{},"Override upward"," if your EULA requires a higher minimum age.",[125,1818,1819,1822],{},[17,1820,1821],{},"Re-answer after big features."," Adding chat, a feed or a browser changes your answers.",[14,1824,402,1825,113],{},[69,1826,406],{"href":405},[31,1828,410],{"id":409},[14,1830,1831,1832,418,1834,113],{},"If an update is stuck on age rating questions, or an iOS build won't go through App Store Connect, the ",[69,1833,417],{"href":416},[69,1835,422],{"href":421},{"title":424,"searchDepth":425,"depth":425,"links":1837},[1838,1839,1840,1841,1842,1843,1844,1845,1846],{"id":33,"depth":425,"text":34},{"id":1477,"depth":425,"text":1478},{"id":1528,"depth":425,"text":1529},{"id":1641,"depth":425,"text":1642},{"id":1677,"depth":425,"text":1678},{"id":1712,"depth":425,"text":1713},{"id":1770,"depth":425,"text":1771},{"id":1783,"depth":425,"text":1784},{"id":409,"depth":425,"text":410},"2026-10-19T03:10:00.000Z","Apple's updated App Store age ratings add 13+, 16+ and 18+ and new questions on in-app controls, capabilities, medical or wellness topics and violent themes. The dated timeline, what happens if you didn't answer, and how to answer, checked October 18, 2026.",[1850,1853,1856,1859,1862],{"question":1851,"answer":1852},"What are the new App Store age ratings?","The updated system adds 13+, 16+ and 18+ to the existing 4+ and 9+ ratings. Apple's values and definitions page also lists an Unrated value, which can't be published on the App Store. Ratings are assigned per country or region and can vary with local standards.",{"question":1854,"answer":1855},"What happens if I did not answer the updated age rating questions by January 31, 2026?","Apple's reminder email, as a developer posted it on the Apple Developer Forums, said that if you don't answer the questions by January 31, 2026, you won't be able to submit app updates in App Store Connect. Apple's Upcoming Requirements page words it as an interruption when submitting your app updates. The pages I read do not say live apps are removed.",{"question":1857,"answer":1858},"Where do I answer the age rating questions?","In App Store Connect, open the app, go to General, then App Information, and click Set Up Age Ratings under Age Ratings. To change answers later, click Edit at the top of App Information. The roles that can do this are Account Holder, Admin, App Manager and Marketing.",{"question":1860,"answer":1861},"Which new questions did Apple add?","Apple's July 2025 post lists four areas, in-app controls, capabilities, medical or wellness topics and violent themes. Apple's definitions page groups them as in-app controls (parental controls, age assurance), capabilities (unrestricted web access, user-generated content, social media, messaging and chat, advertising) and medical or wellness. Social media was added on July 9, 2026.",{"question":1863,"answer":1864},"Can I set a higher age rating than Apple calculates?","Yes. Under Age Categories and Override, choose Override to Higher Age Rating. Apple's help page says the App Store will display your specified rating while the content descriptions still reflect your answers. If your EULA has a minimum age above the calculated rating, you must override to a rating that meets it.",{"readingTimeStats":1866},{"text":1867,"minutes":1868,"time":1869,"words":1870},"10 min read",9.01,540600,1802,"\u002Fblog\u002Fapp-store-age-rating-questions-update-2026","app store age rating questions","8 min",[471,1875,1876,1877],"apple-privacy-manifest-itms-91053-itms-91061-flutter-fix-2026","itms-90683-missing-purpose-string-info-plist-flutter-2026","flutter-ios-build-failed-after-upgrade-2026",{"title":1351,"description":1848},[1880,1882,1885,1887,1890,1893,1895,1897,1900,1903],{"title":1881,"url":1399},"Apple Developer News, Updated age ratings in App Store Connect (July 24, 2025)",{"title":1883,"url":1884},"Apple Developer, Upcoming Requirements, Age Rating Updates","https:\u002F\u002Fdeveloper.apple.com\u002Fnews\u002Fupcoming-requirements\u002F?id=07242025a",{"title":1886,"url":1414},"Apple Developer Forums, Final reminder: Answer the updated age ratings questions (reminder email text)",{"title":1888,"url":1889},"App Store Connect Help, Set an app age rating","https:\u002F\u002Fdeveloper.apple.com\u002Fhelp\u002Fapp-store-connect\u002Fmanage-app-information\u002Fset-an-app-age-rating\u002F",{"title":1891,"url":1892},"App Store Connect Help, Age ratings values and definitions","https:\u002F\u002Fdeveloper.apple.com\u002Fhelp\u002Fapp-store-connect\u002Freference\u002Fapp-information\u002Fage-ratings-values-and-definitions",{"title":1894,"url":661},"Apple Developer News, Age rating questionnaire now includes social media questions (July 9, 2026)",{"title":1896,"url":1443},"Apple Developer News, Introducing Time Allowances (June 8, 2026)",{"title":1898,"url":1899},"Apple Developer News, Upcoming changes to age ratings in Australia and Vietnam (May 21, 2026)","https:\u002F\u002Fdeveloper.apple.com\u002Fnews\u002F?id=yrrb45pw",{"title":1901,"url":1902},"Apple Developer News, Updates to age ratings for the Republic of Korea (August 12, 2026)","https:\u002F\u002Fdeveloper.apple.com\u002Fnews\u002F?id=oj3r9pvw",{"title":1904,"url":1905},"Apple Developer, App Review Guidelines","https:\u002F\u002Fdeveloper.apple.com\u002Fapp-store\u002Freview\u002Fguidelines\u002F","blog\u002Fapp-store-age-rating-questions-update-2026","app store age rating questions, app store connect age ratings, apple age rating 13+ 16+ 18+, age rating questionnaire, app store connect cannot submit update age rating, flutter app store age rating, declared age range api, social media age rating questions, apple age assurance, app store age rating 2026",[1909,1910,1911,1912,1913],"Apple's updated age rating system adds 13+, 16+ and 18+ to the existing 4+ and 9+ ratings. Apple announced it on July 24, 2025.","Apple asked developers to answer the new questions for each app by January 31, 2026. Apple's pages warn of an interruption when submitting updates. A reminder email, as posted on the Apple Developer Forums, said you won't be able to submit app updates without answers.","The new questions cover in-app controls, capabilities, medical or wellness topics, and violent themes. Apple added social media capability questions on July 9, 2026, and said responses would be required from September 2026.","Answer from what the shipped app actually does, including SDKs, web views and ads. App Review Guideline 2.3.6 says to answer honestly, and a mis-rated app can trigger an inquiry from government regulators.","You can set a higher rating than Apple calculates with Override to Higher Age Rating, and you must if your EULA has a higher minimum age. You can't set a lower one.","https:\u002F\u002Fapp369.com\u002Fblog\u002Fapp-store-age-rating-questions-update-2026\u002F","O_j_pqgfCnTRwJo_4ks7HJzx50ZdBRCIEQTIcXHFeHM",{"id":1917,"title":1918,"author":1919,"body":1922,"category":3029,"createdAt":3030,"description":3031,"disclosure":441,"extension":442,"faq":441,"howTo":441,"lastVerified":441,"location":459,"meta":3032,"navigation":466,"ogImage":441,"path":3038,"primaryKeyword":441,"readingTime":3039,"related":441,"seo":3040,"sources":441,"stem":3041,"tags":3042,"takeaways":441,"updatedAt":3043,"url":3044,"__hash__":3045},"blog\u002Fblog\u002Fmobile-app-development-healthcare-guide.md","Healthcare App Development Guide (2026)",{"name":7,"social":1920},{"twitter":1921},"@app369dev",{"type":11,"value":1923,"toc":2987},[1924,1930,1933,1937,1940,1944,1947,1952,1975,1981,1985,1988,1992,2015,2020,2024,2027,2031,2054,2059,2063,2066,2070,2093,2098,2102,2105,2109,2132,2137,2144,2148,2151,2155,2158,2175,2179,2184,2198,2203,2223,2228,2242,2247,2261,2266,2280,2284,2287,2319,2325,2329,2332,2336,2359,2363,2386,2390,2393,2419,2423,2443,2447,2470,2477,2481,2484,2488,2491,2523,2530,2534,2537,2569,2574,2594,2598,2601,2645,2649,2652,2684,2692,2696,2699,2703,2786,2790,2822,2826,2852,2856,2860,2867,2871,2884,2888,2903,2907,2914,2918,2927,2931,2950,2954,2965,2969,2972],[14,1925,1926,1929],{},[17,1927,1928],{},"Healthcare app development requires HIPAA compliance, end-to-end encryption, HL7 FHIR data interoperability standards, and specialized security architecture from the ground up."," The mobile health (mHealth) market keeps growing quickly, and the growth is driven by increasing telehealth adoption, remote patient monitoring, and the demand for better patient engagement tools.",[14,1931,1932],{},"Building a healthcare app is fundamentally different from building a standard consumer or business app. Regulatory requirements, data sensitivity, and integration complexity add layers of technical and legal considerations that impact every decision from architecture to deployment. This guide covers what you need to know to build a compliant, secure, and effective healthcare app in 2026.",[31,1934,1936],{"id":1935},"types-of-healthcare-apps","Types of Healthcare Apps",[14,1938,1939],{},"The healthcare app market spans a wide range of applications, each with unique requirements, user bases, and regulatory considerations. Understanding which category your app falls into helps define its scope and compliance needs.",[262,1941,1943],{"id":1942},"telehealth-and-virtual-care-apps","Telehealth and Virtual Care Apps",[14,1945,1946],{},"Telehealth exploded during the COVID-19 pandemic and has stayed far above pre-pandemic levels. These apps connect patients with healthcare providers through video calls, messaging, and remote consultations.",[14,1948,1949],{},[17,1950,1951],{},"Key features:",[122,1953,1954,1957,1960,1963,1966,1969,1972],{},[125,1955,1956],{},"HIPAA-compliant video conferencing (using WebRTC with encryption)",[125,1958,1959],{},"Secure messaging between patients and providers",[125,1961,1962],{},"Appointment scheduling and calendar integration",[125,1964,1965],{},"Digital prescriptions (e-prescribing)",[125,1967,1968],{},"Insurance verification and billing integration",[125,1970,1971],{},"Waiting room functionality with queue management",[125,1973,1974],{},"Session notes and documentation tools",[14,1976,1977,1980],{},[17,1978,1979],{},"Examples:"," Teladoc, Amwell, MDLive, Doctor on Demand",[262,1982,1984],{"id":1983},"patient-portal-and-engagement-apps","Patient Portal and Engagement Apps",[14,1986,1987],{},"Patient portals give patients access to their health information and the ability to interact with their healthcare provider outside of appointments.",[14,1989,1990],{},[17,1991,1951],{},[122,1993,1994,1997,2000,2003,2006,2009,2012],{},[125,1995,1996],{},"Access to medical records, lab results, and imaging",[125,1998,1999],{},"Appointment scheduling and reminders",[125,2001,2002],{},"Prescription refill requests",[125,2004,2005],{},"Secure messaging with care team",[125,2007,2008],{},"Bill pay and insurance information",[125,2010,2011],{},"Health education resources",[125,2013,2014],{},"Family and caregiver access management",[14,2016,2017,2019],{},[17,2018,1979],{}," MyChart (Epic), Patient Portal (Cerner), Athena Patient",[262,2021,2023],{"id":2022},"fitness-and-wellness-apps","Fitness and Wellness Apps",[14,2025,2026],{},"Fitness and wellness apps focus on prevention, healthy living, and general wellness. While not all wellness apps require HIPAA compliance, those that collect health data and share it with healthcare providers must comply.",[14,2028,2029],{},[17,2030,1951],{},[122,2032,2033,2036,2039,2042,2045,2048,2051],{},[125,2034,2035],{},"Activity tracking (steps, calories, distance, heart rate)",[125,2037,2038],{},"Workout programs and guided exercises",[125,2040,2041],{},"Nutrition tracking and meal planning",[125,2043,2044],{},"Sleep monitoring and analysis",[125,2046,2047],{},"Mental health tools (meditation, mood tracking, journaling)",[125,2049,2050],{},"Wearable device integration (Apple Watch, Fitbit, Garmin)",[125,2052,2053],{},"Social features and community challenges",[14,2055,2056,2058],{},[17,2057,1979],{}," MyFitnessPal, Calm, Headspace, Noom",[262,2060,2062],{"id":2061},"electronic-health-record-ehr-and-clinical-apps","Electronic Health Record (EHR) and Clinical Apps",[14,2064,2065],{},"These apps are used by healthcare professionals to manage patient data, document clinical encounters, and coordinate care. They require the highest level of security and compliance.",[14,2067,2068],{},[17,2069,1951],{},[122,2071,2072,2075,2078,2081,2084,2087,2090],{},[125,2073,2074],{},"Patient demographics and medical history management",[125,2076,2077],{},"Clinical documentation (SOAP notes, procedure notes)",[125,2079,2080],{},"Order entry (lab orders, radiology, prescriptions)",[125,2082,2083],{},"Clinical decision support alerts",[125,2085,2086],{},"Care coordination and referral management",[125,2088,2089],{},"Coding and billing integration (ICD-10, CPT)",[125,2091,2092],{},"Interoperability with other EHR systems via HL7 FHIR",[14,2094,2095,2097],{},[17,2096,1979],{}," Epic Haiku, Cerner PowerChart Touch, AthenaOne Mobile",[262,2099,2101],{"id":2100},"remote-patient-monitoring-rpm-apps","Remote Patient Monitoring (RPM) Apps",[14,2103,2104],{},"RPM apps collect patient health data outside of traditional clinical settings and transmit it to healthcare providers for monitoring and intervention.",[14,2106,2107],{},[17,2108,1951],{},[122,2110,2111,2114,2117,2120,2123,2126,2129],{},[125,2112,2113],{},"Real-time vital sign monitoring (blood pressure, glucose, SpO2, heart rate)",[125,2115,2116],{},"Bluetooth\u002FBLE device connectivity for medical devices",[125,2118,2119],{},"Alert thresholds and automated notifications to providers",[125,2121,2122],{},"Patient-reported outcomes and symptom tracking",[125,2124,2125],{},"Trend analysis and data visualization",[125,2127,2128],{},"Integration with EHR systems",[125,2130,2131],{},"CMS reimbursement code support (CPT 99453, 99454, 99457, 99458)",[14,2133,2134,2136],{},[17,2135,1979],{}," Biobeat, Vivify Health, ResMed, Dexcom",[14,2138,2139,2140,113],{},"Explore more about healthcare and other industry-specific solutions on my ",[69,2141,2143],{"href":2142},"\u002Findustries\u002F","Industries page",[31,2145,2147],{"id":2146},"hipaa-compliance-requirements","HIPAA Compliance Requirements",[14,2149,2150],{},"HIPAA (Health Insurance Portability and Accountability Act) compliance is not optional for healthcare apps that handle Protected Health Information (PHI). Violations can result in substantial civil penalties, set by tier and adjusted for inflation each year by HHS.",[262,2152,2154],{"id":2153},"what-is-protected-health-information-phi","What is Protected Health Information (PHI)?",[14,2156,2157],{},"PHI is any individually identifiable health information that is created, received, maintained, or transmitted by a covered entity or business associate. This includes:",[122,2159,2160,2163,2166,2169,2172],{},[125,2161,2162],{},"Patient names, addresses, dates of birth, Social Security numbers",[125,2164,2165],{},"Medical records, lab results, diagnoses, and treatment information",[125,2167,2168],{},"Insurance and billing information",[125,2170,2171],{},"Biometric data (fingerprints, voiceprints, facial recognition data)",[125,2173,2174],{},"Any data that could be used to identify a patient in a healthcare context",[262,2176,2178],{"id":2177},"technical-safeguards-required-by-hipaa","Technical Safeguards Required by HIPAA",[14,2180,2181],{},[17,2182,2183],{},"1. Access Controls",[122,2185,2186,2189,2192,2195],{},[125,2187,2188],{},"Role-based access control (RBAC) ensuring users only access data relevant to their role",[125,2190,2191],{},"Unique user identification for every person who accesses PHI",[125,2193,2194],{},"Automatic session timeout after a period of inactivity (typically 15 minutes)",[125,2196,2197],{},"Emergency access procedures for break-the-glass scenarios",[14,2199,2200],{},[17,2201,2202],{},"2. Data Encryption",[122,2204,2205,2211,2217],{},[125,2206,2207,2210],{},[17,2208,2209],{},"Encryption in transit:"," All data transmitted between the app, servers, and third-party services must use TLS 1.2 or higher. HTTPS is mandatory for all API endpoints.",[125,2212,2213,2216],{},[17,2214,2215],{},"Encryption at rest:"," All PHI stored on servers, databases, and devices must be encrypted using AES-256 or equivalent. This includes database fields, file storage, and backups.",[125,2218,2219,2222],{},[17,2220,2221],{},"End-to-end encryption:"," For messaging features, implement E2E encryption so that even server administrators cannot read message contents.",[14,2224,2225],{},[17,2226,2227],{},"3. Audit Controls",[122,2229,2230,2233,2236,2239],{},[125,2231,2232],{},"Comprehensive audit logging of all access to PHI (who accessed what, when, and from where)",[125,2234,2235],{},"Tamper-proof audit logs that cannot be modified or deleted",[125,2237,2238],{},"Regular audit log review procedures (automated alerts for suspicious activity)",[125,2240,2241],{},"Audit log retention for a minimum of 6 years",[14,2243,2244],{},[17,2245,2246],{},"4. Integrity Controls",[122,2248,2249,2252,2255,2258],{},[125,2250,2251],{},"Data validation to prevent corruption or unauthorized modification",[125,2253,2254],{},"Digital signatures for clinical documents",[125,2256,2257],{},"Version control for medical records with complete change history",[125,2259,2260],{},"Database integrity checks and backup verification",[14,2262,2263],{},[17,2264,2265],{},"5. Authentication and Transmission Security",[122,2267,2268,2271,2274,2277],{},[125,2269,2270],{},"Multi-factor authentication (MFA) for all users accessing PHI",[125,2272,2273],{},"Biometric authentication support (Face ID, Touch ID, fingerprint)",[125,2275,2276],{},"Certificate pinning to prevent man-in-the-middle attacks",[125,2278,2279],{},"Secure API authentication (OAuth 2.0 with PKCE for mobile)",[262,2281,2283],{"id":2282},"administrative-and-organizational-requirements","Administrative and Organizational Requirements",[14,2285,2286],{},"Beyond technical safeguards, HIPAA requires:",[122,2288,2289,2295,2301,2307,2313],{},[125,2290,2291,2294],{},[17,2292,2293],{},"Business Associate Agreement (BAA):"," Written agreements with every vendor, cloud provider, and service that has access to PHI. This includes your hosting provider, analytics services, and crash reporting tools.",[125,2296,2297,2300],{},[17,2298,2299],{},"Risk assessment:"," Regular security risk assessments to identify and address vulnerabilities.",[125,2302,2303,2306],{},[17,2304,2305],{},"Breach notification procedures:"," A documented plan for notifying affected individuals, HHS, and media (if applicable) within 60 days of discovering a breach.",[125,2308,2309,2312],{},[17,2310,2311],{},"Employee training:"," All team members who handle PHI must receive HIPAA training.",[125,2314,2315,2318],{},[17,2316,2317],{},"Policies and procedures:"," Written privacy and security policies that are regularly reviewed and updated.",[14,2320,2321,2324],{},[17,2322,2323],{},"Critical note:"," Using Firebase for a healthcare app requires Google Cloud's HIPAA BAA, which is available for Firebase Authentication, Firestore, Cloud Functions, Cloud Storage, and other covered services. Google provides a HIPAA implementation guide specifically for Firebase.",[31,2326,2328],{"id":2327},"key-features-for-healthcare-apps","Key Features for Healthcare Apps",[14,2330,2331],{},"Regardless of the type of healthcare app you are building, certain features are essential for delivering a secure, usable, and effective product.",[262,2333,2335],{"id":2334},"appointment-booking-and-management","Appointment Booking and Management",[122,2337,2338,2341,2344,2347,2350,2353,2356],{},[125,2339,2340],{},"Real-time provider availability with calendar sync",[125,2342,2343],{},"Multi-location support for healthcare systems",[125,2345,2346],{},"Automated appointment reminders (push notifications, SMS, email)",[125,2348,2349],{},"Cancellation and rescheduling with policy enforcement",[125,2351,2352],{},"Waitlist management for cancelled appointment slots",[125,2354,2355],{},"Insurance eligibility verification before booking",[125,2357,2358],{},"Telehealth vs in-person appointment type selection",[262,2360,2362],{"id":2361},"secure-messaging","Secure Messaging",[122,2364,2365,2368,2371,2374,2377,2380,2383],{},[125,2366,2367],{},"HIPAA-compliant end-to-end encrypted messaging",[125,2369,2370],{},"Support for text, images, documents, and voice messages",[125,2372,2373],{},"Read receipts and delivery confirmation",[125,2375,2376],{},"Message expiration and auto-deletion options",[125,2378,2379],{},"File attachment scanning for malware",[125,2381,2382],{},"Group messaging for care teams",[125,2384,2385],{},"Priority flagging for urgent messages",[262,2387,2389],{"id":2388},"ehr-integration","EHR Integration",[14,2391,2392],{},"Integrating with existing Electronic Health Record systems is often the most complex and time-consuming aspect of healthcare app development.",[122,2394,2395,2401,2407,2413],{},[125,2396,2397,2400],{},[17,2398,2399],{},"HL7 FHIR R4:"," The modern standard for healthcare data interoperability. FHIR uses RESTful APIs and JSON\u002FXML data formats, making it significantly easier to implement than legacy HL7 v2 interfaces.",[125,2402,2403,2406],{},[17,2404,2405],{},"SMART on FHIR:"," An open standard for app integration with EHR systems. Supports OAuth 2.0 for authorization and provides a consistent API for accessing patient data across different EHR vendors.",[125,2408,2409,2412],{},[17,2410,2411],{},"Direct integration with major EHRs:"," Epic, Cerner, Allscripts, and athenahealth all provide app marketplace programs and APIs for third-party integration.",[125,2414,2415,2418],{},[17,2416,2417],{},"Data mapping and transformation:"," Healthcare data comes in various formats and coding systems (ICD-10, SNOMED CT, LOINC, RxNorm). Your app must correctly map and translate between these systems.",[262,2420,2422],{"id":2421},"prescription-management","Prescription Management",[122,2424,2425,2428,2431,2434,2437,2440],{},[125,2426,2427],{},"E-prescribing integration with pharmacy networks (Surescripts)",[125,2429,2430],{},"Drug interaction checking and allergy alerts",[125,2432,2433],{},"Prescription refill requests and status tracking",[125,2435,2436],{},"Medication adherence tracking and reminders",[125,2438,2439],{},"Controlled substance prescribing (EPCS) with DEA compliance",[125,2441,2442],{},"Prescription cost transparency and pharmacy comparison",[262,2444,2446],{"id":2445},"payment-and-insurance-processing","Payment and Insurance Processing",[122,2448,2449,2452,2455,2458,2461,2464,2467],{},[125,2450,2451],{},"Insurance eligibility verification in real time",[125,2453,2454],{},"Claims submission and tracking",[125,2456,2457],{},"Patient copay and deductible calculation",[125,2459,2460],{},"Credit card and HSA\u002FFSA payment processing",[125,2462,2463],{},"Superbill generation for out-of-network claims",[125,2465,2466],{},"Payment plan management",[125,2468,2469],{},"Integration with practice management systems",[14,2471,2472,2473,113],{},"Learn about how I build custom healthcare features through my ",[69,2474,2476],{"href":2475},"\u002Fservice\u002Fmobile-apps\u002F","Mobile App Development services",[31,2478,2480],{"id":2479},"technology-stack-for-healthcare-apps","Technology Stack for Healthcare Apps",[14,2482,2483],{},"Choosing the right technology stack for a healthcare app requires balancing development efficiency, security, compliance, and long-term maintainability.",[262,2485,2487],{"id":2486},"frontend-flutter-for-cross-platform-healthcare-apps","Frontend: Flutter for Cross-Platform Healthcare Apps",[14,2489,2490],{},"Flutter is an excellent choice for healthcare app development because:",[122,2492,2493,2499,2505,2511,2517],{},[125,2494,2495,2498],{},[17,2496,2497],{},"Single codebase for iOS and Android"," usually reduces development time and cost compared to two native apps",[125,2500,2501,2504],{},[17,2502,2503],{},"Native performance"," ensures smooth UI interactions, which is critical for clinical workflows",[125,2506,2507,2510],{},[17,2508,2509],{},"Custom widget system"," allows building complex healthcare-specific UI components (vital sign charts, medical imaging viewers, clinical forms)",[125,2512,2513,2516],{},[17,2514,2515],{},"Offline support"," through local databases (Hive, Isar, SQLite) for use in low-connectivity environments",[125,2518,2519,2522],{},[17,2520,2521],{},"Strong encryption libraries"," available through Dart packages",[14,2524,2525,2526,113],{},"Learn more about my ",[69,2527,2529],{"href":2528},"\u002Fservice\u002Fflutter-development\u002F","Flutter Development services",[262,2531,2533],{"id":2532},"backend-firebase-with-hipaa-baa","Backend: Firebase with HIPAA BAA",[14,2535,2536],{},"Firebase, when configured with a Google Cloud HIPAA BAA, provides a powerful and cost-effective backend for healthcare apps:",[122,2538,2539,2545,2551,2557,2563],{},[125,2540,2541,2544],{},[17,2542,2543],{},"Firestore:"," HIPAA-eligible NoSQL database with real-time sync and offline support",[125,2546,2547,2550],{},[17,2548,2549],{},"Firebase Authentication:"," Secure user authentication with MFA support",[125,2552,2553,2556],{},[17,2554,2555],{},"Cloud Functions:"," Serverless compute for business logic, HL7 FHIR processing, and integrations",[125,2558,2559,2562],{},[17,2560,2561],{},"Cloud Storage:"," HIPAA-eligible file storage for medical documents, images, and recordings",[125,2564,2565,2568],{},[17,2566,2567],{},"Firebase Cloud Messaging:"," Push notifications (note: notification content must not contain PHI)",[14,2570,2571],{},[17,2572,2573],{},"Alternative backends for complex healthcare requirements:",[122,2575,2576,2582,2588],{},[125,2577,2578,2581],{},[17,2579,2580],{},"AWS with HIPAA BAA:"," Amazon offers a comprehensive HIPAA-eligible service catalog including EC2, RDS, S3, Lambda, and more. Best for large-scale enterprise healthcare applications.",[125,2583,2584,2587],{},[17,2585,2586],{},"Azure with HIPAA BAA:"," Microsoft Azure provides Azure API for FHIR, Azure Health Data Services, and HIPAA-eligible infrastructure. Strong choice for organizations already in the Microsoft ecosystem.",[125,2589,2590,2593],{},[17,2591,2592],{},"Custom backend (Node.js, Python, Go):"," For maximum control over security, performance, and compliance. Requires more upfront investment but offers complete flexibility.",[262,2595,2597],{"id":2596},"security-layer","Security Layer",[14,2599,2600],{},"Healthcare apps require a dedicated security layer that goes beyond standard application security:",[122,2602,2603,2609,2615,2621,2627,2633,2639],{},[125,2604,2605,2608],{},[17,2606,2607],{},"Application-level encryption:"," AES-256 encryption for all PHI stored on devices",[125,2610,2611,2614],{},[17,2612,2613],{},"Network security:"," TLS 1.3, certificate pinning, VPN for admin access",[125,2616,2617,2620],{},[17,2618,2619],{},"API security:"," OAuth 2.0 with PKCE, JWT with short expiration, API rate limiting",[125,2622,2623,2626],{},[17,2624,2625],{},"Data loss prevention (DLP):"," Prevent unauthorized export, screenshots, or copying of PHI",[125,2628,2629,2632],{},[17,2630,2631],{},"Mobile device management (MDM):"," Remote wipe capability for lost or stolen devices",[125,2634,2635,2638],{},[17,2636,2637],{},"Penetration testing:"," Annual third-party security assessments",[125,2640,2641,2644],{},[17,2642,2643],{},"Vulnerability scanning:"," Automated scanning with tools like OWASP ZAP, Snyk, or Checkmarx",[262,2646,2648],{"id":2647},"ai-and-machine-learning-in-healthcare-apps","AI and Machine Learning in Healthcare Apps",[14,2650,2651],{},"AI is transforming healthcare applications, and integrating AI capabilities can significantly enhance your app's value:",[122,2653,2654,2660,2666,2672,2678],{},[125,2655,2656,2659],{},[17,2657,2658],{},"Clinical decision support:"," AI-powered alerts and recommendations based on patient data",[125,2661,2662,2665],{},[17,2663,2664],{},"Natural language processing (NLP):"," Automated clinical documentation from voice dictation",[125,2667,2668,2671],{},[17,2669,2670],{},"Image analysis:"," Computer vision for dermatology screening, radiology assistance, wound assessment",[125,2673,2674,2677],{},[17,2675,2676],{},"Predictive analytics:"," Risk scoring for readmission, deterioration, or disease progression",[125,2679,2680,2683],{},[17,2681,2682],{},"Chatbots and virtual assistants:"," Symptom checkers, triage tools, and patient FAQ bots",[14,2685,2686,2687,2691],{},"Explore my ",[69,2688,2690],{"href":2689},"\u002Fservice\u002Fai-integration\u002F","AI Integration services"," to learn how I implement AI in healthcare apps.",[31,2693,2695],{"id":2694},"healthcare-app-development-costs","Healthcare App Development Costs",[14,2697,2698],{},"Healthcare apps cost more than standard business apps due to compliance requirements, security infrastructure, and integration complexity. Here is what to expect:",[262,2700,2702],{"id":2701},"cost-ranges-by-app-type","Cost Ranges by App Type",[36,2704,2705,2718],{},[39,2706,2707],{},[42,2708,2709,2712,2715],{},[45,2710,2711],{},"App Type",[45,2713,2714],{},"Cost Range",[45,2716,2717],{},"Timeline",[55,2719,2720,2731,2742,2753,2764,2775],{},[42,2721,2722,2725,2728],{},[60,2723,2724],{},"Patient Portal (Basic)",[60,2726,2727],{},"$60,000 - $120,000",[60,2729,2730],{},"4-6 months",[42,2732,2733,2736,2739],{},[60,2734,2735],{},"Telehealth Platform",[60,2737,2738],{},"$100,000 - $250,000",[60,2740,2741],{},"6-10 months",[42,2743,2744,2747,2750],{},[60,2745,2746],{},"Remote Patient Monitoring",[60,2748,2749],{},"$80,000 - $200,000",[60,2751,2752],{},"5-8 months",[42,2754,2755,2758,2761],{},[60,2756,2757],{},"EHR\u002FClinical App",[60,2759,2760],{},"$150,000 - $400,000+",[60,2762,2763],{},"8-14 months",[42,2765,2766,2769,2772],{},[60,2767,2768],{},"Fitness\u002FWellness App",[60,2770,2771],{},"$40,000 - $120,000",[60,2773,2774],{},"3-6 months",[42,2776,2777,2780,2783],{},[60,2778,2779],{},"Comprehensive Health Platform",[60,2781,2782],{},"$250,000 - $600,000+",[60,2784,2785],{},"10-18 months",[262,2787,2789],{"id":2788},"what-drives-healthcare-app-costs-higher","What Drives Healthcare App Costs Higher",[122,2791,2792,2798,2804,2810,2816],{},[125,2793,2794,2797],{},[17,2795,2796],{},"HIPAA compliance infrastructure:"," Adds $20,000-$60,000 to development costs for proper encryption, audit logging, access controls, and security testing.",[125,2799,2800,2803],{},[17,2801,2802],{},"EHR integration:"," HL7 FHIR integration costs $15,000-$40,000+ per system, depending on the EHR vendor and data complexity.",[125,2805,2806,2809],{},[17,2807,2808],{},"Security testing and audits:"," Professional penetration testing and HIPAA security risk assessments cost $10,000-$30,000.",[125,2811,2812,2815],{},[17,2813,2814],{},"Compliance documentation:"," Creating the required policies, procedures, and BAAs costs $5,000-$15,000.",[125,2817,2818,2821],{},[17,2819,2820],{},"Ongoing compliance maintenance:"," Annual HIPAA compliance activities cost $10,000-$25,000\u002Fyear.",[262,2823,2825],{"id":2824},"cost-saving-strategies-for-healthcare-apps","Cost-Saving Strategies for Healthcare Apps",[267,2827,2828,2834,2840,2846],{},[125,2829,2830,2833],{},[17,2831,2832],{},"Start with an MVP:"," Build the minimum viable set of HIPAA-compliant features and expand based on user feedback. Even a healthcare MVP must be fully compliant, but you can limit the feature set.",[125,2835,2836,2839],{},[17,2837,2838],{},"Use HIPAA-eligible cloud services:"," Firebase and AWS offer pre-configured HIPAA-eligible services that reduce the effort of building compliant infrastructure from scratch.",[125,2841,2842,2845],{},[17,2843,2844],{},"Leverage FHIR-based APIs:"," Using standardized FHIR APIs reduces integration costs compared to custom point-to-point integrations with each EHR system.",[125,2847,2848,2851],{},[17,2849,2850],{},"Build on Flutter for cross-platform:"," A single codebase for iOS and Android reduces development and testing costs compared to two native apps, even with healthcare-specific requirements.",[31,2853,2855],{"id":2854},"frequently-asked-questions","Frequently Asked Questions",[262,2857,2859],{"id":2858},"do-all-healthcare-apps-need-to-be-hipaa-compliant","Do all healthcare apps need to be HIPAA compliant?",[14,2861,2862,2863,2866],{},"Not all healthcare apps require HIPAA compliance, but ",[17,2864,2865],{},"any app that collects, stores, transmits, or processes Protected Health Information (PHI) on behalf of a covered entity or business associate must comply with HIPAA",". General wellness and fitness apps that do not interact with healthcare providers or insurance companies may be exempt. However, the line is increasingly blurry. If your app collects health data and there is any possibility it could be shared with a healthcare provider, it is safest to build with HIPAA compliance from the start. Retrofitting an existing app for HIPAA compliance is significantly more expensive than building it in from day one.",[262,2868,2870],{"id":2869},"how-long-does-it-take-to-build-a-hipaa-compliant-healthcare-app","How long does it take to build a HIPAA-compliant healthcare app?",[14,2872,2873,2874,2876,2877,2879,2880,2883],{},"A basic HIPAA-compliant healthcare app (patient portal, appointment scheduling) takes ",[17,2875,2730],{},". A telehealth platform with video conferencing, messaging, and EHR integration takes ",[17,2878,2741],{},". A comprehensive clinical application with full EHR integration takes ",[17,2881,2882],{},"8-14+ months",". The HIPAA compliance components add meaningful time compared to non-healthcare apps of similar complexity, primarily due to security implementation, encryption, audit logging, and compliance testing.",[262,2885,2887],{"id":2886},"what-cloud-providers-offer-hipaa-compliant-hosting","What cloud providers offer HIPAA-compliant hosting?",[14,2889,2890,2891,2894,2895,2898,2899,2902],{},"The major cloud providers all offer HIPAA-eligible services: ",[17,2892,2893],{},"Google Cloud Platform"," offers a HIPAA BAA that covers a published list of services (check it carefully, because not every Firebase product is covered). ",[17,2896,2897],{},"Amazon Web Services (AWS)"," offers a large catalog of HIPAA-eligible services. ",[17,2900,2901],{},"Microsoft Azure"," provides HIPAA BAA coverage and specialized healthcare services like Azure API for FHIR. When using any cloud provider, you must sign a BAA, configure services according to their HIPAA implementation guides, and implement additional security controls at the application level.",[262,2904,2906],{"id":2905},"can-i-use-third-party-apis-and-services-in-a-hipaa-compliant-app","Can I use third-party APIs and services in a HIPAA-compliant app?",[14,2908,2909,2910,2913],{},"Yes, but ",[17,2911,2912],{},"every third-party service that has access to PHI must sign a Business Associate Agreement (BAA)",". This includes your cloud provider, analytics tools, crash reporting services, email services, SMS providers, and any other vendor that touches PHI. Some popular tools do not offer BAAs (e.g., standard Google Analytics, many marketing automation platforms), so you need to either use HIPAA-eligible alternatives or ensure no PHI flows through those services. I always recommend creating a data flow diagram early in the project to identify every touchpoint where PHI is involved.",[262,2915,2917],{"id":2916},"what-are-the-penalties-for-hipaa-violations-in-mobile-apps","What are the penalties for HIPAA violations in mobile apps?",[14,2919,2920,2921,2926],{},"HIPAA civil penalties are structured in four tiers, from violations the organization did not know about up to willful neglect that was not corrected, with per-violation amounts and annual caps that HHS adjusts for inflation every year. Beyond financial penalties, breaches can result in criminal prosecution, mandatory corrective action plans, ongoing monitoring by HHS, and severe reputational damage. The ",[69,2922,2925],{"href":2923,"rel":2924},"https:\u002F\u002Focrportal.hhs.gov\u002Focr\u002Fbreach\u002Fbreach_report.jsf",[73],"HHS Breach Portal"," lists every reported breach affecting 500 or more individuals, and it grows every year.",[262,2928,2930],{"id":2929},"how-do-i-integrate-my-healthcare-app-with-existing-ehr-systems-like-epic-or-cerner","How do I integrate my healthcare app with existing EHR systems like Epic or Cerner?",[14,2932,2933,2934,2937,2938,2941,2942,2945,2946,2949],{},"EHR integration typically follows one of these paths: ",[17,2935,2936],{},"SMART on FHIR"," is the recommended approach for new integrations. It provides standardized APIs, OAuth 2.0 authentication, and works across multiple EHR vendors. ",[17,2939,2940],{},"Vendor-specific marketplaces"," like the Epic App Orchard or Oracle Health (Cerner) Marketplace provide certification programs and APIs for deeper integration. ",[17,2943,2944],{},"HL7 v2 interfaces"," are legacy integration methods still used by many health systems for ADT messages, lab results, and orders. ",[17,2947,2948],{},"Custom API integration"," may be needed when EHR vendors do not offer standard interfaces for specific data types. Budget $15,000-$40,000+ per EHR integration and plan for 2-4 months of development and testing per vendor.",[262,2951,2953],{"id":2952},"is-flutter-suitable-for-building-hipaa-compliant-healthcare-apps","Is Flutter suitable for building HIPAA-compliant healthcare apps?",[14,2955,2956,2957,2960,2961,2964],{},"Yes, ",[17,2958,2959],{},"Flutter is well-suited for HIPAA-compliant healthcare apps",". Flutter provides native compilation (no JavaScript bridge), which makes it easier to implement application-level encryption and secure data storage. The Dart ecosystem includes packages for AES encryption, secure storage (flutter_secure_storage), biometric authentication, and certificate pinning. Additionally, Flutter's single codebase approach ensures consistent security implementation across iOS and Android, reducing the risk of platform-specific security gaps. Several major healthcare organizations have built production HIPAA-compliant apps using Flutter. Visit my ",[69,2962,2963],{"href":2528},"Flutter Development page"," to learn more.",[31,2966,2968],{"id":2967},"next-steps","Next Steps",[14,2970,2971],{},"Building a healthcare app is a significant undertaking that requires specialized expertise in compliance, security, and healthcare workflows. The right development partner makes the difference between a compliant, effective healthcare product and a liability.",[14,2973,2974,2977,2978,2981,2982,2986],{},[17,2975,2976],{},"Ready to build your healthcare app?"," ",[69,2979,2980],{"href":421},"Contact App369"," about your project, or ",[69,2983,2985],{"href":2984},"\u002Fservice\u002Fconsultations\u002F","book a consultation"," ($100 per 15 minutes, paid upfront). I will assess your compliance requirements, recommend a technical architecture, and provide a detailed project estimate. I design for HIPAA requirements from the architecture stage.",{"title":424,"searchDepth":425,"depth":425,"links":2988},[2989,2996,3001,3008,3014,3019,3028],{"id":1935,"depth":425,"text":1936,"children":2990},[2991,2992,2993,2994,2995],{"id":1942,"depth":433,"text":1943},{"id":1983,"depth":433,"text":1984},{"id":2022,"depth":433,"text":2023},{"id":2061,"depth":433,"text":2062},{"id":2100,"depth":433,"text":2101},{"id":2146,"depth":425,"text":2147,"children":2997},[2998,2999,3000],{"id":2153,"depth":433,"text":2154},{"id":2177,"depth":433,"text":2178},{"id":2282,"depth":433,"text":2283},{"id":2327,"depth":425,"text":2328,"children":3002},[3003,3004,3005,3006,3007],{"id":2334,"depth":433,"text":2335},{"id":2361,"depth":433,"text":2362},{"id":2388,"depth":433,"text":2389},{"id":2421,"depth":433,"text":2422},{"id":2445,"depth":433,"text":2446},{"id":2479,"depth":425,"text":2480,"children":3009},[3010,3011,3012,3013],{"id":2486,"depth":433,"text":2487},{"id":2532,"depth":433,"text":2533},{"id":2596,"depth":433,"text":2597},{"id":2647,"depth":433,"text":2648},{"id":2694,"depth":425,"text":2695,"children":3015},[3016,3017,3018],{"id":2701,"depth":433,"text":2702},{"id":2788,"depth":433,"text":2789},{"id":2824,"depth":433,"text":2825},{"id":2854,"depth":425,"text":2855,"children":3020},[3021,3022,3023,3024,3025,3026,3027],{"id":2858,"depth":433,"text":2859},{"id":2869,"depth":433,"text":2870},{"id":2886,"depth":433,"text":2887},{"id":2905,"depth":433,"text":2906},{"id":2916,"depth":433,"text":2917},{"id":2929,"depth":433,"text":2930},{"id":2952,"depth":433,"text":2953},{"id":2967,"depth":425,"text":2968},"Industry Guides","2026-02-17T10:00:00.000Z","Build HIPAA-compliant healthcare apps with proper security and HL7 FHIR integration. Covers compliance, architecture, costs, and best practices for 2026.",{"readingTimeStats":3033},{"text":3034,"minutes":3035,"time":3036,"words":3037},"13 min read",12.94,776400,2588,"\u002Fblog\u002Fmobile-app-development-healthcare-guide","13 min",{"title":1918,"description":3031},"blog\u002Fmobile-app-development-healthcare-guide","healthcare app development, HIPAA compliance, medical app, telehealth, health tech, patient engagement","2026-10-12T12:00:00.000Z","https:\u002F\u002Fapp369.com\u002Fblog\u002Fmobile-app-development-healthcare-guide\u002F","fBGCBwlOl9jiINBBcgDglhZo_3D9MmYZFQvUW9Viymo",{"id":3047,"title":3048,"author":3049,"body":3051,"category":438,"createdAt":3450,"description":3451,"disclosure":441,"extension":442,"faq":3452,"howTo":441,"lastVerified":441,"location":459,"meta":3471,"navigation":466,"ogImage":441,"path":3477,"primaryKeyword":3478,"readingTime":3479,"related":3480,"seo":3483,"sources":3484,"stem":3499,"tags":3500,"takeaways":3501,"updatedAt":3450,"url":3507,"__hash__":3508},"blog\u002Fblog\u002Fgoogle-fit-api-deprecated-health-connect-2026.md","Google Fit API Deprecated: Moving to Health Connect in 2026",{"name":7,"social":3050},{"twitter":9},{"type":11,"value":3052,"toc":3440},[3053,3059,3062,3067,3071,3145,3148,3152,3155,3189,3193,3196,3251,3254,3338,3345,3349,3352,3355,3359,3362,3421,3425,3427],[14,3054,3055,3058],{},[17,3056,3057],{},"The Google Fit APIs are on their way out: Google says they, including the REST API, will only be supported until the end of 2026, and no new developers have been able to sign up since May 1, 2024."," Google recommends Health Connect for step tracking and mobile-first Android apps, and the Google Health API for cloud-based integrations. Which one you need depends on which Fit APIs your app calls, and some features, such as Goals, have no replacement at all.",[14,3060,3061],{},"If you landed here from an old link to the Google Fit docs or a Fit tutorial, this is what changed and where each piece goes. The dates and mappings come from Google's Fit and Health documentation and the Android Fit migration guide, as listed in the sources. I checked each page on October 18, 2026.",[14,3063,3064,3066],{},[17,3065,28],{}," App369 is my studio. I build and fix mobile apps, including Flutter apps on Android and iOS, and the last section mentions what I sell. Google doesn't pay me for anything on this page.",[31,3068,3070],{"id":3069},"what-happened-to-google-fit-and-when","What happened to Google Fit, and when",[36,3072,3073,3083],{},[39,3074,3075],{},[42,3076,3077,3079,3081],{},[45,3078,47],{},[45,3080,1382],{},[45,3082,53],{},[55,3084,3085,3100,3112,3128],{},[42,3086,3087,3090,3093],{},[60,3088,3089],{},"May 1, 2024",[60,3091,3092],{},"Developers can no longer sign up to use the Google Fit APIs",[60,3094,3095],{},[69,3096,3099],{"href":3097,"rel":3098},"https:\u002F\u002Fdevelopers.google.com\u002Ffit",[73],"Google Fit",[42,3101,3102,3104,3107],{},[60,3103,723],{},[60,3105,3106],{},"Google says support for the legacy Fitbit Web API ends. It keeps operating, without bug fixes or API support",[60,3108,3109],{},[69,3110,764],{"href":762,"rel":3111},[73],[42,3113,3114,3118,3123],{},[60,3115,3116],{},[17,3117,748],{},[60,3119,3120],{},[17,3121,3122],{},"Google says the Fitbit Web API will be turned off and will no longer function or sync data",[60,3124,3125],{},[69,3126,764],{"href":762,"rel":3127},[73],[42,3129,3130,3134,3139],{},[60,3131,3132],{},[17,3133,825],{},[60,3135,3136],{},[17,3137,3138],{},"Google says the Google Fit APIs, including the REST API, are supported until then",[60,3140,3141],{},[69,3142,3144],{"href":837,"rel":3143},[73],"Fit migration guide",[14,3146,3147],{},"Google hasn't published an exact turn-off date for the Fit APIs. The migration guide says Google will keep its section on existing Fit app integrations updated with when to deprecate them.",[262,3149,3151],{"id":3150},"what-the-old-addresses-do-today","What the old addresses do today",[14,3153,3154],{},"Checked on October 18, 2026:",[122,3156,3157,3163,3172,3178],{},[125,3158,3159,3162],{},[17,3160,3161],{},"developers.google.com\u002Ffit"," still loads, with a banner saying the Fit APIs will be deprecated in 2026 and new sign-ups closed on May 1, 2024. The Android and REST getting-started pages still load too.",[125,3164,3165,3168,3169,113],{},[17,3166,3167],{},"developers.google.com\u002Ffit\u002Fmigration"," returned ",[17,3170,3171],{},"404",[125,3173,3174,3175,3177],{},"The old Health Connect migration guide address redirects to the new ",[17,3176,3144],{}," on developer.android.com.",[125,3179,3180,3181,3184,3185,3188],{},"A request to the Fit REST API at ",[17,3182,3183],{},"googleapis.com\u002Ffitness\u002Fv1"," without sign-in returned ",[17,3186,3187],{},"401",", so the API still answers for now.",[31,3190,3192],{"id":3191},"which-replacement-fits-your-app","Which replacement fits your app",[14,3194,3195],{},"Google's migration guide picks the path by app type:",[36,3197,3198,3211],{},[39,3199,3200],{},[42,3201,3202,3205,3208],{},[45,3203,3204],{},"Your app",[45,3206,3207],{},"Google's recommended path",[45,3209,3210],{},"Why, per Google",[55,3212,3213,3226,3238],{},[42,3214,3215,3218,3223],{},[60,3216,3217],{},"Step tracking app",[60,3219,3220],{},[17,3221,3222],{},"Health Connect",[60,3224,3225],{},"Mobile-centric reading of aggregated step data from several sources",[42,3227,3228,3231,3235],{},[60,3229,3230],{},"Fitness tracker companion app",[60,3232,3233],{},[17,3234,764],{},[60,3236,3237],{},"A web-centric platform with OAuth for user integration",[42,3239,3240,3243,3248],{},[60,3241,3242],{},"Health and fitness platform",[60,3244,3245],{},[17,3246,3247],{},"Both",[60,3249,3250],{},"The Google Health API for Fitbit and Google device data, Health Connect for on-device aggregated data",[14,3252,3253],{},"And by which Fit API you call today:",[36,3255,3256,3269],{},[39,3257,3258],{},[42,3259,3260,3263,3266],{},[45,3261,3262],{},"Fit API you use",[45,3264,3265],{},"Phone",[45,3267,3268],{},"Wear OS",[55,3270,3271,3281,3292,3303,3314,3328],{},[42,3272,3273,3276,3278],{},[60,3274,3275],{},"History API",[60,3277,764],{},[60,3279,3280],{},"Not applicable: use Health Connect from the phone app, not the watch",[42,3282,3283,3286,3289],{},[60,3284,3285],{},"Recording API (steps)",[60,3287,3288],{},"Health Connect. The total includes mobile steps on Android 14 or higher",[60,3290,3291],{},"Health Services",[42,3293,3294,3297,3300],{},[60,3295,3296],{},"Sensor API (real-time data)",[60,3298,3299],{},"Android Sensors framework or the Fused Location Provider API",[60,3301,3302],{},"Health Services (PassiveMonitoringClient, MeasureClient, ExerciseClient), or SensorManager and the Fused Location Provider",[42,3304,3305,3308,3311],{},[60,3306,3307],{},"Session API",[60,3309,3310],{},"Read and write sessions through the Google Health API; track start and stop inside your app",[60,3312,3313],{},"Start and stop with Health Services (ExerciseClient); read and write through Health Connect in the phone app",[42,3315,3316,3319,3324],{},[60,3317,3318],{},"Goals API",[60,3320,3321],{},[17,3322,3323],{},"No replacement",[60,3325,3326],{},[17,3327,3323],{},[42,3329,3330,3333,3336],{},[60,3331,3332],{},"BLE API",[60,3334,3335],{},"Android Bluetooth APIs directly",[60,3337,3335],{},[14,3339,3340,3341,3344],{},"Source: ",[69,3342,3144],{"href":837,"rel":3343},[73],", last updated September 10, 2026. For inserting a workout or sleep session, the guide says to use Health Connect from the phone app with an ExerciseSessionRecord or SleepSessionRecord.",[262,3346,3348],{"id":3347},"health-connect-is-not-a-drop-in-swap","Health Connect is not a drop-in swap",[14,3350,3351],{},"The migration guide compares the two. The Fit API for Android is registered in Google Cloud Console, is cloud-centric and uses OAuth 2.0 with OAuth scopes. Health Connect is registered through your Play Store project and a health apps declaration, stores data on the device, needs no OAuth, and uses Android manifest permissions. My read: that means changes to your sign-in flow, your permission screens and your Play Console declaration, not just the API calls.",[14,3353,3354],{},"The Google Health API is the other way round: Google describes it as the next generation of the Fitbit Web API, with OAuth 2.0 access to data from Fitbit, Pixel Watch and other devices and apps. If your backend pulled Fit history through the REST API, this is the closer fit.",[31,3356,3358],{"id":3357},"what-to-do-now","What to do now",[14,3360,3361],{},"This section is my advice, not Google's.",[267,3363,3364,3379,3391,3397,3403,3409,3415],{},[125,3365,3366,3369,3370,708,3373,708,3376,3378],{},[17,3367,3368],{},"List every Fit call."," Search the app and backend for ",[386,3371,3372],{},"com.google.android.gms.fitness",[386,3374,3375],{},"Fitness.get",[386,3377,3183],{}," and any Fit OAuth scopes. Note which of the APIs in the table above each one uses.",[125,3380,3381,3384,3385,3390],{},[17,3382,3383],{},"Check your Flutter package, and any other health library you use."," The Flutter ",[69,3386,3389],{"href":3387,"rel":3388},"https:\u002F\u002Fpub.dev\u002Fpackages\u002Fhealth",[73],"health package"," says it removed Google Fit support in version 11.0.0 and now uses Health Connect on Android. If your app pins an older version, the upgrade and the Health Connect move are the same job.",[125,3392,3393,3396],{},[17,3394,3395],{},"Pick the path per feature, not per app."," A step counter can move to Health Connect while a synced workout history moves to the Google Health API. Use the two tables above.",[125,3398,3399,3402],{},[17,3400,3401],{},"Plan the permission change."," Health Connect asks users for on-device permissions instead of a Google sign-in. Write the new permission screen copy, and fill in the health apps declaration in Play Console before you submit the update.",[125,3404,3405,3408],{},[17,3406,3407],{},"Rebuild goals yourself."," Google lists no replacement for the Goals API, so store goals in your own app or backend and compare them with the data you read.",[125,3410,3411,3414],{},[17,3412,3413],{},"Keep existing users working while you switch."," Google's guide says that if your app has a way for users to connect to Google Fit, or is on the Works with Google Fit list, you can keep that integration for current users, and that Google will update the guide with when to deprecate it. Google recommends offering Health Connect or the Google Health API as a new option, and not asking users to disconnect from Google Fit.",[125,3416,3417,3420],{},[17,3418,3419],{},"If you also use the Fitbit Web API, do that first."," Google's date for turning it off, October 30, 2026, comes before the end of 2026.",[14,3422,402,3423,113],{},[69,3424,406],{"href":405},[31,3426,410],{"id":409},[14,3428,3429,3430,3432,3433,3437,3438,113],{},"If your app reads steps, workouts or sleep through Google Fit and you need it moved to Health Connect or the Google Health API, the ",[69,3431,417],{"href":416}," covers it in two fixed-price steps. A $450 Diagnosis gives you the root cause with evidence and a fixed repair quote within 3 business days, credited toward the fix. If you go ahead, the $1,200 Fix takes 5 business days. If the app was built with an AI tool and you're not sure what it calls, the ",[69,3434,3436],{"href":3435},"\u002Ffixed-price\u002Fai-app-rescue\u002F","AI-Built App Rescue"," starts with a $450 Launch Check in 3 business days. Or ",[69,3439,422],{"href":421},{"title":424,"searchDepth":425,"depth":425,"links":3441},[3442,3445,3448,3449],{"id":3069,"depth":425,"text":3070,"children":3443},[3444],{"id":3150,"depth":433,"text":3151},{"id":3191,"depth":425,"text":3192,"children":3446},[3447],{"id":3347,"depth":433,"text":3348},{"id":3357,"depth":425,"text":3358},{"id":409,"depth":425,"text":410},"2026-10-18T19:00:00.000Z","Google stopped new Google Fit API sign-ups on May 1, 2024 and says the Fit APIs, including the REST API, are supported only until the end of 2026. Which replacement fits your app (Health Connect, the Google Health API or Health Services), the Fitbit Web API dates, and what to do first, from Google's docs checked October 18, 2026.",[3453,3456,3459,3462,3465,3468],{"question":3454,"answer":3455},"Is the Google Fit API being shut down?","Google says the Google Fit APIs, including the REST API, will be deprecated in 2026 and will only be supported until the end of 2026. New developers have not been able to sign up since May 1, 2024. On October 18, 2026, an unauthenticated request to the Fit REST API returned 401, so it was still responding. My advice is to plan your move before the end of the year.",{"question":3457,"answer":3458},"What replaces the Google Fit API?","Google recommends Health Connect for step tracking and mobile-first Android apps, and the Google Health API for cloud-based integrations such as fitness tracker companion apps. For a health and fitness platform, Google says to use the Google Health API for Fitbit and Google device data and Health Connect for on-device aggregated data. Fit on Wear OS moves to Health Services.",{"question":3460,"answer":3461},"What is the Google Health API?","Google describes it as the next generation of the Fitbit Web API. It gives OAuth 2.0 access to health and fitness data from Fitbit, Pixel Watch and other third-party devices and apps, and Google's Fit migration guide names it as the replacement for the Fit History and Session APIs.",{"question":3463,"answer":3464},"Is there a replacement for the Google Fit Goals API?","No. Google's migration guide says no replacement API is available for the Goals API, on phone or Wear OS. If your app shows goals, my advice is to store and track them in your own app or backend.",{"question":3466,"answer":3467},"Does the Flutter health package still support Google Fit?","No. The health package on pub.dev says it removed Google Fit support in version 11.0.0. It reads and writes Apple Health on iOS and Health Connect on Android, so a Flutter app on an older version needs to upgrade and move its Android code to Health Connect.",{"question":3469,"answer":3470},"When does the Fitbit Web API stop working?","Google says support for the legacy Fitbit Web API ended on September 30, 2026, and that on October 30, 2026 it will be turned off and stop syncing data. Google says to migrate to the Google Health API to keep access.",{"readingTimeStats":3472},{"text":3473,"minutes":3474,"time":3475,"words":3476},"6 min read",5.435,326100,1087,"\u002Fblog\u002Fgoogle-fit-api-deprecated-health-connect-2026","google fit api deprecated","7 min",[3481,3482,1305],"google-sign-in-android-deprecated-credential-manager-2026","google-places-api-legacy-legacyapinotactivatedmaperror-2026",{"title":3048,"description":3451},[3485,3487,3489,3492,3494,3497],{"title":3486,"url":3097},"Google for Developers, Google Fit",{"title":3488,"url":837},"Android Developers, Fit migration guide (last updated September 10, 2026)",{"title":3490,"url":3491},"Android Developers, Health Connect","https:\u002F\u002Fdeveloper.android.com\u002Fhealth-and-fitness\u002Fhealth-connect",{"title":3493,"url":762},"Google for Developers, Google Health API",{"title":3495,"url":3496},"Android Developers, Health Services on Wear OS","https:\u002F\u002Fdeveloper.android.com\u002Fhealth-and-fitness\u002Fguides\u002Fhealth-services",{"title":3498,"url":3387},"pub.dev, health package","blog\u002Fgoogle-fit-api-deprecated-health-connect-2026","google fit api deprecated, google fit shutdown, google fit rest api deprecated, health connect migration, google health api, fitbit web api shutdown, google fit alternative, flutter health package google fit, health services wear os, google fit end of 2026",[3502,3503,3504,3505,3506],"Since May 1, 2024, developers cannot sign up to use the Google Fit APIs. Google's migration guide says the Fit APIs, including the REST API, will only be supported until the end of 2026.","Google recommends Health Connect for step tracking and mobile-first Android apps, and the Google Health API for cloud-based integrations. Fit on Wear OS moves to Health Services.","The Fit History and Session APIs map to the Google Health API, and the Recording API's step counts to Health Connect. Google lists no replacement for the Goals API, and BLE apps should use the Android Bluetooth APIs directly.","Health Connect works differently: no OAuth, on-device data, Android manifest permissions and a health apps declaration in Play Console. Google's comparison shows different registration, sign-in and permission models, so in my view expect code changes, not just a library swap.","Google says the legacy Fitbit Web API lost support on September 30, 2026 and will be turned off on October 30, 2026. Its replacement is also the Google Health API.","https:\u002F\u002Fapp369.com\u002Fblog\u002Fgoogle-fit-api-deprecated-health-connect-2026\u002F","Yo8d8rPmlIwyECe8w4qO3el3YD_zPm9-bYr7hmRkfeU",[3510,3512,3516,3517,3521,3522],{"keyword":5,"url":497,"title":5,"relevance":3511},78,{"keyword":3513,"url":3514,"title":3513,"relevance":3515},"iOS 27 SDK Required April 2027: Xcode 27 Checklist","https:\u002F\u002Fapp369.com\u002Fblog\u002Fios-27-sdk-requirement-april-2027-xcode-27-flutter\u002F",8,{"keyword":1351,"url":1914,"title":1351,"relevance":3515},{"keyword":3518,"url":3519,"title":3518,"relevance":3520},"Flutter Android Build Fails After AGP 9: The Fix","https:\u002F\u002Fapp369.com\u002Fblog\u002Fflutter-android-gradle-plugin-9-build-failed-fix-2026\u002F",7,{"keyword":3048,"url":3507,"title":3048,"relevance":3520},{"keyword":3523,"url":3524,"title":3523,"relevance":3520},"Flutter iOS Build Failed After an Upgrade? Fix CocoaPods and Xcode Errors (2026)","https:\u002F\u002Fapp369.com\u002Fblog\u002Fflutter-ios-build-failed-after-upgrade-2026\u002F",1792391278284]