Replies / add another platform (iOS too)

How to say no to "add another platform (iOS too)"

"Can we have it on iOS too, not just Android?"

Another platform is not a checkbox. It is a second build, a second set of tests and a second round of store reviews.

Get the replies Lock your scope in Scopease, free

Why this is scope creep

Each platform has its own quirks, devices and approval rules.
Even with cross platform tools, testing, builds and releases roughly double.
Long term it also means two things to maintain and support.

Copy-paste replies

Fill the [brackets] and send. Pick the tone that fits the client.

Firm

Hi [Name], the project is scoped for [Android] only. [iOS] would be a separate phase with its own estimate. I'd recommend we launch on [Android] first and add [iOS] once it's working well.

Friendly

Makes sense to want both! Launching one first is usually smarter though: you learn what users actually do, and the second platform gets the fixes for free. Want me to scope [iOS] as phase 2?

Yes, for a fee

Hi [Name], sure. Change order for [iOS]: build, device testing, App Store setup and submission, [price], adds [X] weeks. Ongoing support for both platforms would be [price] per month after launch.

The "yes, for a fee" reply works best when the scope was written down first. In Scopease the client approves the scope through one private link, every extra ask becomes a priced change order they approve or decline, and the invoice builds itself from approved work. Free for your first project.

Start free Have us set it up for you ($79)

Questions

Is "Can we have it on iOS too, not just Android?" scope creep?

Yes, if it was not in the agreed scope. Each platform has its own quirks, devices and approval rules. The fix is not a fight, it is a clear reply that points to the scope and offers a priced option.

How do I price adding a second platform?

Estimate the build, testing on real devices, store setup and review, plus the extra maintenance. Even with shared code it is rarely a small add-on.

Should I launch on one platform first?

Often yes. It gets the product in front of users sooner and keeps the budget under control. Put the second platform in a priced phase 2.

Free tools that help you say no

Change order generator: turn the paid reply into a proper change order
Client red flag checker: spot these asks in a brief before you quote
Scope creep calculator: see what saying yes for free cost you this year
Scope of work templates: write the scope so the next no is easy
All free tools