DEV Community: Zoopcoder

iOS's 20-second launch watchdog, and the App Store screenshot rule that changed in 2026

Zoopcoder — Mon, 21 Sep 2026 16:27:42 +0000

Two small, unrelated-looking questions came up this week: why did my iOS app just close on launch with no error, and how many screenshots does the App Store actually require in 2026. Both have exact, sourced answers that are more specific than most advice floating around.

The iOS "crash" that isn't a crash

If an iOS app takes too long to draw its first screen after launch, iOS doesn't wait — it kills the process outright. Apple calls this a watchdog termination, and its own documentation ("Addressing watchdog terminations") shows a real logged example: a scene-create watchdog transgression that hit the wall at 19.97 seconds. That lines up with what Apple's own DTS engineers say on the developer forums — the launch-time budget is commonly ~20 seconds in practice.

To a user this looks exactly like a crash: the app opens, then instantly closes. But the fix has nothing to do with a broken line of code — it's almost always a slow synchronous task on the main thread during launch (an oversized asset load, a blocking network call, heavy view-hierarchy construction). The crash log often won't even show the offending code, because watchdog terminations happen at the edges of the app lifecycle rather than inside one stack frame — you have to profile the launch path directly to find it.

We fix one reproducible iOS bug or crash (watchdog timeouts included) for a fixed ₹1,499, from your Xcode source, signed TestFlight build back in 2-3 working days: https://zoopcoder.com/services/ios-app-bug-fix.php — Android equivalent is ₹1,299: https://zoopcoder.com/services/android-app-bug-fix.php (the two platforms get diagnosed separately since Apple's toolchain has no equivalent of Android APK decompilation).

The App Store screenshot rules got simpler, not stricter

Worth updating your mental model here: App Store Connect's current screenshot spec (straight from Apple's own reference page) is 1 to 10 screenshots per localisation, and for iPhone you now only need one size — the 6.9-inch display (1,290×2,796px is the standard option) — which Apple automatically scales down to every smaller iPhone. The old "upload a separate set per device size" requirement is gone, unless you skip the 6.9-inch size entirely (then the 6.5-inch set becomes a required fallback).

Google Play's requirements haven't changed: a 512×512 icon, a 1,024×500 feature graphic, and a minimum of 2 screenshots. Policy on both stores forbids screenshots that misrepresent the app — they have to be your real screens.

We design a full captioned screenshot set (up to 6), feature graphic and icon for a fixed ₹1,499, in 2-3 working days: https://zoopcoder.com/services/app-store-screenshots-graphics.php

Disclosure: I'm with ZoopCoder (zoopcoder.com), an India-based dev shop that sells the above as fixed-price services — sharing this because both facts are more specific than most of what's out there, and useful whether or not you ever use us.

Sources: Apple Developer Documentation ("Addressing watchdog terminations"), Apple Developer Forums (DTS staff on the ~20s launch timeout), App Store Connect Help ("Screenshot specifications"), Google Play Console Help.

Gmail's 0.30% Spam Threshold and Android's 5-Second ANR Timeout: Two Numbers That Quietly Cost Indian Founders Money

Zoopcoder — Mon, 21 Sep 2026 09:24:15 +0000

Two numbers nobody tells you about until something breaks

Most "my emails go to spam" and "my app keeps crashing" complaints trace back to one specific, documented number. Here are two of them, sourced directly from Google's own docs.

1. Gmail's authentication rules have a hard threshold: 0.30%

Since 1 February 2024, Gmail requires every sender â€” not just bulk senders â€” to have SPF or DKIM set up on their sending domain (source). If you send more than 5,000 messages a day to Gmail addresses, the bar is higher: you need SPF and DKIM and DMARC together, plus a spam-complaint rate that stays under 0.30% as reported in Google Postmaster Tools.

The part that trips up small businesses in India: a domain can only have one valid SPF record. Add a second TXT record for a new mail tool (a CRM, a marketing platform, a website contact form) and you don't get two working SPF records â€” you get zero, silently. That's usually the real reason "my invoices are going to client spam folders" starts happening right after onboarding a new tool.

DMARC has a second wrinkle worth knowing: a record published at your root domain automatically covers every subdomain, unless you publish a separate sp= tag. Most businesses only need the one record.

We fix this end to end â€” audit, merged SPF, DKIM per sender, a DMARC record with safe reporting, verified with real header checks â€” for a fixed â‚¹1,499, 24-48 hours: zoopcoder.com/services/email-deliverability-spf-dkim-dmarc

2. Android's ANR timeout is exactly 5 seconds

An ANR ("Application Not Responding") is not the same thing as a crash. A crash ends the app. An ANR is Android deciding your app's main thread has frozen while the process is still alive â€” and for the most common trigger (the app not responding to a touch or key press), that decision is made after exactly 5 seconds (source). Other triggers (a foreground service not calling startForeground in time, a broadcast receiver that doesn't finish) have their own short timeouts.

Play Console groups both crashes and ANRs into clusters under Android vitals, and a cluster usually names the exact class and line â€” which is why a crash or ANR with a stack trace is often a same-day fix, while "it hangs sometimes" has to be reproduced first.

We fix one reproducible bug or crash in your existing Android app â€” code diff plus a signed build back in your hands â€” for a fixed â‚¹1,299 per issue, 2-3 working days: zoopcoder.com/services/android-app-bug-fix

Disclosure: I work with ZoopCoder, an India-based dev shop, and both links above are our own fixed-price services. The numbers (0.30%, 5,000/day, exactly 5 seconds) are sourced straight from Google's own documentation, linked above â€” not our own claims.

Core Web Vitals INP explained, and what GA4 + Search Console setup should cost in India

Zoopcoder — Mon, 21 Sep 2026 05:33:49 +0000

Two things worth knowing if you run a small business website in India.

1. Core Web Vitals quietly changed in 2024, and a lot of speed advice online still describes the old rules

For years "page speed" meant one number: Largest Contentful Paint (LCP) — how long the biggest visible thing takes to load. Good is still under 2.5 seconds.

But on 12 March 2024, Google's Core Web Vitals retired First Input Delay and replaced it with Interaction to Next Paint (INP) — a metric that measures how fast your page responds after it has already loaded, every time someone taps a button or opens a menu, not just on the very first click. Google's official thresholds:

Good: 200ms or less
Needs improvement: 200–500ms
Poor: over 500ms

All three Core Web Vitals (LCP, INP, CLS) are assessed separately for mobile and desktop, at the 75th percentile of real visits — your site has to pass for your unluckiest quarter of visitors, not your average one. A homepage that looks fast in a lab test in a city can still fail INP for someone on a cheaper phone or a weaker connection, because the usual culprits — a WhatsApp widget, a Facebook Pixel, a chat plugin, a Tag Manager container with fifteen tags — all add JavaScript that runs on every interaction, not just on first load.

We run a fixed ₹2,999 website speed optimization pass — before/after PageSpeed reports, image compression, caching, minification, lazy loading, and INP/CLS fixes where the cause is fixable (plugin bloat, render-blocking scripts) rather than the hosting itself. Details here.

2. A GA4 + Search Console setup shouldn't cost more than the tools you're setting up

Both are entirely free from Google — no subscription, ever. What you're paying for is the setup work: creating the property, installing the tag correctly (not a duplicate, and not a dead Universal Analytics leftover — UA stopped collecting data in July 2023 and plenty of small sites still carry its tag doing nothing), configuring key events, verifying Search Console, and linking the two so both reports agree.

Real Indian pricing for this varies with scope. Some providers bundle a full Google Tag Manager container with custom triggers into the same package for around ₹5,000. If you don't need custom tag management — you just need tracking that actually works — that's paying for scope you won't use. We charge a fixed ₹1,499 for GA4 + Search Console, verified and linked, properties stay in your own Google account. Details here.

Disclosure: I work at ZoopCoder, an Indian web/app development shop — these are our own fixed-price services, numbers as listed on our site today.

Landing Pages, Google Ads Quality Score, and the Free Business Email Catch Nobody Reads

Zoopcoder — Fri, 18 Sep 2026 16:25:40 +0000

Two small, unrelated questions came up this week while working on paid-traffic landing pages and setting up business email for clients. Writing down what we found because both facts are more useful than the usual marketing copy lets on.

1. Why sending Google Ads traffic to your homepage hurts your Quality Score

Google's own documentation is explicit about this: Quality Score for every keyword is calculated from three components — expected click-through rate, ad relevance, and landing page experience. (Source: Google Ads Help, About Quality Score)

A homepage usually links to five other pages and has three or four competing calls to action, because it was built for browsing, not converting. A landing page has one offer and one action. That is the actual mechanical reason a focused landing page tends to score better on "landing page experience" than a homepage does for the same ad, and a lower Quality Score means you pay more per click for the same position.

We build these at ZoopCoder for a fixed Rs 4,999 (3-5 working days) — landing page design details here. Full disclosure: we sell this, which is exactly why I looked up the actual Google documentation before writing about it instead of repeating "landing pages convert better" as received wisdom.

2. The "free business email" plan almost nobody reads the fine print on

Zoho Mail has a genuine Forever Free plan: up to 5 mailboxes on one domain, 5 GB storage per user. Real, no catch on price. But — source: Zoho Mail Pricing — IMAP/POP access is not included on the free plan. That means you can only read that mail through Zoho's own webmail or mobile app: not Outlook, not the Gmail app, not a CRM, not a helpdesk tool.

For a one-person business checking mail on a phone, that might be completely fine. For anyone who wants that email inside an existing mail client or connected to a CRM, it is not, and it is the single most common reason people try the free plan, get stuck, and assume "business email setup" is more complicated than it actually is.

We set up Google Workspace or Zoho Mail (a paid plan, with full IMAP/POP) on your own domain, done properly with SPF and DKIM so mail does not land in spam, for a fixed Rs 999 — details here.

Disclosure: I work on ZoopCoder's service pages, so both links above go to services we sell. The Google and Zoho facts are pulled straight from Google's and Zoho's own published pages, linked above — check them yourself before taking my word for it.

What a 5-Page Business Website and a Technical SEO Audit Actually Cost in India (2026)

Zoopcoder — Fri, 18 Sep 2026 09:23:57 +0000

A 5-page business website and a technical SEO audit are two of the most-asked-about, least-transparently-priced things in Indian web work. Real 2026 numbers, and what they should actually cost.

What a 5-page business website costs in India

India pricing surveys in 2026 put a basic template-based 5-page site at ₹10,000–₹30,000, and a custom-designed 5–15 page build at ₹15,000–₹80,000. The spread is wide because "website" covers everything from a theme with your logo dropped in to a fully custom design with copywriting and photography.

For most local and service businesses — clinics, shops, consultants, coaching centres — five pages (Home, About, Services, Gallery, Contact) is genuinely enough. Industry guidance on page count settles around 5–10 core pages for a small business site: fewer than five tends to look incomplete, and more than 20 without a real content plan creates a maintenance problem more than it creates value.

I work at ZoopCoder, and we sell exactly that fixed scope for ₹9,999, delivered in 7–10 working days — WordPress build (so you can edit it yourself later), a working contact form, WhatsApp/call buttons, and the basic on-page SEO (titles, metas, sitemap) that a lot of budget template builds skip. It's a fixed, no-scoping-call price for a fixed scope, not a "starting from" figure: https://zoopcoder.com/services/business-website-5-pages.php

What a technical SEO audit costs, and the budget-freelancer trap

A standalone technical SEO audit from an Indian agency typically runs ₹15,000–₹75,000. There's also a cheaper freelancer tier at ₹3,000–₹5,000 — but at the ₹800–₹2,000/hour freelancers usually charge, that budget often buys one to a few hours of work. Enough to run a crawl and export it. Not enough to actually read the output and prioritise fixes.

Two facts worth knowing before you pay anyone for this:

Core Web Vitals are graded at the 75th percentile of real visitors, not a single lab test. The "good" thresholds are LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1 — meaning 75% of actual visits to a page need to clear all three for the page to pass. Anything between "good" and "poor" (LCP over 4s, INP over 500ms, CLS over 0.25) is rated "needs improvement."

"Crawled – currently not indexed" has no fixed recovery timeline. Google re-evaluates a page when its signals change — better content, more internal links, more overall site authority — so after a real fix, validation typically shows movement within about two weeks, but full recovery on a low-authority site can take a lot longer. Common causes: thin or duplicate content, weak internal linking to the page, and a sitemap cluttered with low-value URLs like tag archives and paginated pages.

ZoopCoder's technical SEO audit is a fixed ₹2,999 for the full checklist — crawl (up to 500 URLs), Search Console indexing review, Core Web Vitals, redirects, canonicals, sitemap, robots.txt, structured data — with a written, prioritised fix list, not an hourly estimate: https://zoopcoder.com/services/technical-seo-audit.php

Disclosure: I work at ZoopCoder. The numbers above (₹9,999 and ₹2,999) are our own current published prices, and the market-range figures are from 2026 India web-development and SEO-audit pricing research, not invented for this post.

What a WordPress website and a logo actually cost in India (2026 numbers)

Zoopcoder — Fri, 18 Sep 2026 05:23:37 +0000

I build websites and small fixed-price services for Indian small businesses at ZoopCoder (disclosure: I work there — this isn't a customer testimonial). Two questions that come up on almost every website project — "how much should a WordPress site cost" and "how much should a logo cost" — mostly get vague freelancer-quote answers online, so here are real numbers with sources.

WordPress: the software is free, the build isn't

WordPress itself costs ₹0. It's free, open-source software distributed under the GPL, and as of September 2026 it runs on 40.2% of all websites (source: w3techs.com/technologies/details/cm-wordpress). That number is genuinely useful in practice: whichever developer builds your site, the next one you hire can maintain it too — you're not locked to one person's stack.

What you actually pay for is:

the build, setup and customisation (a developer's time)
your own domain + hosting — roughly ₹3,000–₹8,000/year for a small business site
any premium theme/plugin licences you choose to add later (optional)

ZoopCoder's fixed price for a WordPress build — installation, a brand-customised free theme, up to 4 pages, an SEO plugin configured, security hardening, automatic backups, and a handover session — is ₹7,999, delivered in 5-7 working days: https://zoopcoder.com/services/wordpress-website.php

Logo design: a global marketplace price vs a fixed local price

For comparison, 99designs — one of the largest logo marketplaces — lists custom logo design "starting from $249" (checked 2026-09-18), for one freelance designer working through their multi-day contest process. That's roughly ₹24,000 at today's exchange rate.

ZoopCoder's fixed price for a logo — 3 original concepts, 2 revision rounds, vector SVG/PDF masters plus PNG exports, full rights transferred — is ₹1,499, delivered in 3-4 working days: https://zoopcoder.com/services/logo-design.php

One thing worth flagging separately: a lot of "free" logo makers only give you a flattened PNG/JPG on the free tier, not the SVG/PDF vector masters. A vector file is what lets a printer blow your logo up to signboard size, or a shop-board maker resize it, without it going blurry — worth checking before you commit to a "free" logo tool.

The honest summary

Item	Price	Source
WordPress core software	Free (GPL)	wordpress.org, w3techs.com
WordPress build + setup, fixed scope	₹7,999	zoopcoder.com
Logo design, global marketplace starting price	$249 (~₹24,000)	99designs.com
Logo design, fixed scope, local	₹1,499	zoopcoder.com

Happy to answer questions on either in the comments.

Google Play app suspended, or an Apple rejection — what actually fixes each one

Zoopcoder — Thu, 17 Sep 2026 22:24:10 +0000

Two different app store problems get lumped together constantly, and the fix for one does nothing for the other. Here's what handling both at ZoopCoder (I work there — disclosing that up front) has actually looked like.

Google Play: rejection vs. suspension are not the same problem

A rejection blocks one submission or update. You can fix it and resubmit yourself, and Google's own instructions are explicit that you don't need to wait for a reply — you can "correct the issue and send the changes for review... without contacting or waiting for a reply from the policy support team." The part almost everyone misses on a repeat rejection: the corrected build has to go onto every track — production, open, closed and internal testing — with the non-compliant bundle deactivated on each. Leave one violating bundle live on a test track and, per Google, "your attempt to resubmit your app will fail, and live versions of your app bundle(s) may be removed from Google Play."

A suspension is worse: the app is pulled from the Play Store and it counts against your developer account. Google allows exactly one appeal per app removal, suspension, or other enforcement action — so it has to be right the first time, built on a genuine, evidenced fix, not just a promise to do better. One more detail that trips people up: Google states it answers appeals only in Chinese, English, Japanese or Korean. Re-uploading the same app under a new name instead of appealing is a fast way to get the whole account terminated.

We run these as two separate fixed-price services because they're genuinely different jobs: Play Store rejection fix, ₹2,999 per rejection, 2-4 working days, and suspended app appeal, ₹3,999, 2-4 working days to file.

Apple App Store: the rejection email almost always names the guideline

Apple's App Review cites a specific guideline number in its rejection message, most often around metadata, App Privacy nutrition labels, screenshots that don't match the app, or a specific crash. Three things worth knowing if you're stuck here:

Apple states that 90% of App Store submissions are reviewed in less than 24 hours — so a slow resubmission review is more often a deeper check (a crash, a Guideline 4.2 concern) than a stuck queue.
If the citation is Guideline 4.2 — Minimum Functionality, and your app is a straight website wrapper, no code change fixes it if an agency is submitting on the client's behalf. Apple's guidelines say plainly: "Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app's content." The app has to go up from the business's own Apple Developer account, or gain real functionality beyond the website.
An "Invalid Binary" rejection is a technical build failure (wrong bundle ID, missing entitlement, unsupported architecture) caught before a human even looks at the app — usually the fastest of the bunch to fix.

We fix these for a fixed ₹2,999, with one resubmission included if the same issue comes back, in 3-5 working days.

None of this comes with a guarantee — Play and App Review decisions are Google's and Apple's alone, and anyone promising otherwise isn't being straight with you. What actually moves the needle is reading the notice literally, fixing the specific thing it names, and not skipping the part (every track deactivated, right language, right account) that causes the second rejection.

Google Play Data Safety form: closed testing does not exempt you

Zoopcoder — Thu, 17 Sep 2026 16:24:28 +0000

Google Play's Data Safety form: "closed testing" doesn't exempt you (a rule most developers miss)

Every few weeks a developer asks me some version of: "It's just an internal test build, do I really need to fill out the Data Safety form?" The answer, straight from Google Play's own Console help, is yes — no exceptions:

"All developers that have an app published on Google Play must complete the Data safety form, including apps on closed, open, or production testing tracks."

That line trips up more first-time Android developers than almost anything else in the submission process. People assume compliance paperwork is a production-launch problem. It isn't. The moment your APK/AAB sits on any track — even a closed test with five invited users — the form is required.

Why the form exists, and why "mismatch" is the real killer

Google's review compares three things against each other: what your app actually does, what your privacy policy says, and what your Data Safety form declares. When any two of those disagree, that's a mismatch, and mismatches are consistently one of the most common causes of rejection or removal.

The part almost nobody accounts for: your SDKs collect data too, even if your own code doesn't.

AdMob collects device identifiers for ad targeting.
Firebase Analytics and Crashlytics collect crash reports and usage data.
Most auth SDKs collect at minimum an email or phone number.

If your form only reflects what you wrote, and not what the third-party libraries in your app are quietly doing, you have a mismatch — and Google is explicit about what happens next. From the same help documentation:

"When Google becomes aware of a discrepancy between your app behavior and your declaration, we may take appropriate action, including enforcement action."

And critically:

"You alone are responsible for making complete and accurate declarations in your app's store listing on Google Play."

Not your agency, not a free policy generator, not whoever built your app for you — the developer account holder carries the responsibility, full stop.

A short, honest checklist

Audit before you write anything. Open your app's dependencies and actually check what each SDK collects — don't guess from memory.
Match the privacy policy to the form, word for word on data types. If the form says you collect approximate location, the policy needs to say so too.
Fill the form even for closed/internal tracks. It's required at every track, not just production.
Add an account-deletion path if users can create accounts. Google requires this separately, and reviewers check for it.
Don't rely on a free generic policy generator alone — most miss SDK-specific disclosures entirely, which is exactly the gap that creates a mismatch.

This is genuinely fiddly to get right by hand, which is why we (ZoopCoder, a small India-based dev shop — disclosure, I'm the founder) built it into a fixed-price service: we inspect the actual app, list every SDK it uses, write a privacy policy that matches, and fill the Data Safety form to match both. It's ₹999, 1-2 working days: Privacy Policy + Data Safety Form service.

It's not legal advice — it's practical store-compliance work grounded in what the SDKs in your app actually do.

Google Business Profile verification: the 4 methods Google actually assigns

Zoopcoder — Thu, 17 Sep 2026 16:22:59 +0000

Google Business Profile verification: the 4 methods Google actually assigns (and what's free vs paid)

A surprising number of small business owners in India still believe they can choose how to verify their Google Business Profile — postcard, phone call, whatever's fastest. You can't. Google's own help documentation is blunt about it: verification methods are "automatically determined by Google and can't be changed."

I run ZoopCoder, a small dev shop in India, and we set up or fix Google Business Profiles for clients regularly (disclosure: we charge ₹1,499 for the setup work — not for verification itself, which is always free). Here's what I've learned from actually watching Google's verification flow across dozens of profiles this year.

The four methods

Google's current verification methods, per their support pages, are:

Mail (postcard) — a physical postcard with a code, mailed to your business address. Most codes arrive within 14 days.
Phone or text — an SMS or call with a verification code, for businesses Google trusts enough to skip the postcard.
Email — a code sent to a business email address already associated with the listing.
Live video call / video recording — you record or join a video showing your signage, premises and proof you run the business. This method is increasingly common for new listings and service-area businesses. Google's stated review window here is up to 5 business days.

In rare cases Google verifies instantly, with no waiting at all. Which method you get depends on your business category, location, and how much public information already exists about you — not on anything you request.

The thing nobody tells first-time owners

Verification is completely free. Google doesn't charge for it under any method. If someone tells you they can "pay to skip the postcard" or "guarantee video verification," that's not how Google's system works — the method is assigned automatically, and no amount of money changes it.

What people do pay for (us included) is the setup work around it: picking the right primary and secondary categories, writing a description that doesn't get flagged, getting photos uploaded correctly, and — this is the unglamorous part — walking through whichever verification method Google hands you so it doesn't get rejected for a preventable mistake (blurry signage in a video, a mismatched address, etc.).

What actually moves the map pack needle

Separately from verification: ranking in the local 3-pack depends on relevance, distance and prominence — Google says so directly, and no agency (including mine) can promise a position. A complete, accurate, well-categorised profile helps relevance. It does not override distance to the searcher or your prominence (review count, links, citations) elsewhere.

Practical checklist if you're setting one up yourself

Match your business name, address and phone exactly across your website, Google listing and any other directories — mismatches slow down or fail verification.
Pick the most specific primary category available, not the broadest one.
If Google assigns video verification, film your actual signage and workspace — staged or generic footage gets rejected more often.
Never buy or write fake reviews. It violates Google's policy and can get a profile suspended entirely.
Service-area businesses (no walk-in storefront) can hide their address and list service areas instead — you don't need a shopfront to have a profile.

If you'd rather have someone handle the categories, description, photos and verification walkthrough end to end, that's the exact service we run: Google Business Profile Setup at ZoopCoder — ₹1,499, 2-3 working days, no fake reviews, no ranking guarantees (because nobody can honestly make one).

Disclosure: I'm the founder of ZoopCoder. This is genuinely how the verification flow works, based on running it repeatedly for clients this year, not marketing copy.

Converting a Website Into an iPhone App: What Apple Guidelines 4.2 and 4.2.6 Actually Require in 2026

Zoopcoder — Wed, 16 Sep 2026 22:27:57 +0000

Converting a website into an iPhone app sounds like a weekend project until you hit Apple's review guidelines - and then it either gets rejected or nobody tells you what to budget for. Two Apple rules and one India-specific enrollment quirk decide whether it survives, and none of them are obvious from a free "website to app" converter's marketing page.

Guideline 4.2 is the one that kills most conversions

Apple's own App Store Review Guidelines (developer.apple.com/app-store/review/guidelines/) are explicit:

"Your app should include features, content, and UI that elevate it beyond a repackaged website."

That's Guideline 4.2, Minimum Functionality. A WebView wrapped in a shell with no native features is exactly what it describes, and it is the single most common rejection reason for website-to-app conversions.

Guideline 4.2.6 is the one nobody mentions

This is the quieter rule, and it matters even more if you're using a converter service:

"Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app's content. These services should not submit apps on behalf of their clients."

In plain terms: if a vendor builds your app-from-website and submits it from THEIR Apple Developer account, Apple can reject it on principle - however good the app is. The app has to go up from the account of the business that owns the website's content. This is why any agency doing this work properly builds inside the client's own Apple Developer account and hands over the Xcode project, rather than publishing from their own account.

Xcode 26 is now mandatory

Per developer.apple.com/news/upcoming-requirements/: since April 28, 2026, "Apps uploaded to App Store Connect must be built with Xcode 26 or later using an SDK for iOS 26." An older converter export built on a stale Xcode version will not even upload.

The India enrollment quirk

developer.apple.com/support/enrollment/ carries a footnote almost nobody quotes: "Enrollment in India is only available through the Apple Developer app." Most countries can enroll via a web form; in India, the only path is the Apple Developer app on an iPhone or iPad. Budget for that step separately if you're starting from zero.

The fee is recurring, and that changes the math

The Apple Developer Program is 99 USD/year, not a one-time cost - unlike Google Play's US$25 one-time registration fee (support.google.com/googleplay/android-developer/answer/6112435). If the membership lapses, the app is delisted. Any cost comparison between "publish on Android" and "publish on iOS" needs to account for this being a recurring line item, not a sunk cost.

What this actually costs when someone else builds it

For anyone weighing "build it myself" vs "pay someone", we do this conversion at a fixed ₹9,999, 5-7 working days, delivered as a signed iOS build sitting in your own App Store Connect account (not ours) - full writeup with the scope and what's NOT included (the $99/year Apple fee, TestFlight review time) is at https://zoopcoder.com/services/website-to-ios-app.php

Disclosure: I work with ZoopCoder, an Indian dev shop; the numbers above are sourced from Apple and Google's own documentation, and the price above is what we actually charge.