Custom Mobile Development: Do Outsource Vendors Really Handle Domain Registration, ICP Filing, and Server Hosting?

In custom mobile development contracts, non-code environmental items such as domain names, ICP filing, and servers typically do not fall within the default development scope. Under 2026 project delivery practices, whether these items are handled by the outsourcing vendor directly affects the launch schedule and final costs. A safe approach is to verify ownership, timelines, and costs item by item before signing, rather than waiting until development is nearly complete to ask, "Who buys the server?"

Which "Non-Code" Items Can Block Your Launch

A common scenario in projects is that everything goes smoothly in feature development, but eventually gets stuck because domain ICP filing is not approved, server configuration is incorrect, or the developer account is not yet registered. Although these items do not involve writing code, they all have fixed processing cycles and often require the client's personal cooperation.

• Domain: requires purchase and real-name verification;
• Server: requires selecting a cloud vendor, operating system, and network configuration;
• ICP filing: mandatory for domestic servers, typically taking 5–15 working days (experience range);
• iOS developer account: individual/company verification takes 1–5 working days (experience range) and requires qualification materials;
• Push certificates (APNs/vendor): usually valid for one year and require regular renewal;
• Third-party services: payment, maps, and login SDKs all require independent application for API keys.

These items are easy to overlook because they don't produce "pages," yet they determine whether the app can be installed and accessed. In many projects, responsibility is divided based on "whether code is written," but the bottlenecks before launch often occur in these non-code areas.

Why These Items Affect Launch Time

ICP filing is a typical example. As long as the server is in China, filing is unavoidable. Some projects only start filing at the final stage of development, resulting in three weeks of development and two weeks of filing, pushing the entire launch back. Conversely, if filing is initiated immediately after requirements confirmation, it can typically be processed in parallel, reducing wait time to almost zero.

Additionally, the differences between test and production environments are often ignored. Running well on a developer's computer does not guarantee smooth operation on a cloud server. File permissions, environment variables, and database encoding on Linux servers may all be inconsistent. According to project delivery practices, at least 1–3 working days (experience range) should be reserved for deployment and joint debugging before launch.

In projects delivered by Xiyue Company, clients often get stuck because they want to use their own company's server, but the account and keys are not ready. We usually mark server preparation as a "client cooperation task" in the schedule and remind them in advance, because once the server delivery is late, the entire integration testing is postponed, and the resulting standby cost is often billed as additional working hours.

Push certificates and third-party keys also have their own waiting periods: an Apple developer account registration may be approved on the same day, but company qualification review may take 1–5 days; payment merchant account review commonly takes 3–7 working days (experience range). If these waiting periods are not initiated early, they all become pending items on the pre-launch checklist.

How to Determine Whether the Outsourcing Vendor Handles It? A Three-Step Verification Method

Instead of guessing, use the three-step verification method before signing to lock down responsibility boundaries. This method comes from years of project delivery practices: first check scope, then schedule, and finally discuss costs.

1. Step 1: Create an "environment checklist." List domain names, ICP filing, servers, developer accounts, push notifications, third-party keys, etc., in an attachment, clearly indicating whether the responsible party is "vendor handles all," "client provides," or "mutual cooperation."
2. Step 2: Mark the "not later than start date" for each environmental item in the project schedule. For example, if ICP filing requires 5–15 working days, the start date should typically be no later than the first working day after requirements are frozen.
3. Step 3: List costs on a separate line. In the outsourcing quote, whether it includes the first-year server fee, domain registration fee, and deployment hours must be specified numerically.

The logic behind these three steps is: ownership determines responsibility, timeline determines scheduling, and cost determines budget. Each step cannot just rely on a phrase like "includes server"; it must specify duration and configuration. What qualifies as acceptable? If you send this checklist to the vendor and they can reply on the same day with specific timelines and costs for each item, it's usually a more reliable sign for the upcoming cooperation.

Full Outsourcing vs. Client-Provided Infrastructure: How to Choose

Neither option is inherently better or worse; it mainly depends on whether your team has someone who can manage servers.

• Option A: Full outsourcing by the developer. Suitable for teams without technical staff. Typically, domain, server, filing, and deployment are bundled together, and the cost is 2000–5000 RMB higher (experience range). The advantage is that you can directly contact the vendor to solve any problem.
• Option B: Client-provided infrastructure. Suitable for companies with an operations or technically savvy person. This saves the service fee, but you must handle the filing period, server failures, and key configuration yourself. A single misconfiguration can delay the entire schedule.

When comparing, focus on "account ownership." Regardless of the option chosen, it's recommended to register the domain and server accounts under the client's name. Otherwise, switching development teams will make it very difficult to migrate the domain and server. This is a frequently overlooked trust point in project delivery.

Another common misconception is that "full outsourcing" means all accounts are managed by the developer. In reality, full outsourcing usually just means the developer performs operations on your behalf; real-name verification and entity review still require the client's business license or ID information. These procedures cannot be skipped and should not be given to an uncontactable individual.

Accept According to This Environment Checklist

Beyond functional acceptance, environment-related acceptance items should also be checked off one by one. Based on common 2026 practices, at least the following should be confirmed once.

• HTTPS certificate is deployed, with no mixed HTTP content;
• Server has an automatic backup strategy, with daily database backups;
• Test and production environments are separated, with no residual test accounts;
• Push certificates are included in the codebase and can send push notifications successfully;
• Error logs can be viewed remotely rather than only by the outsourcing vendor on-site;
• Domain resolution is under the client's account with admin console access.

What qualifies as acceptable? Every item above must be demonstrated on the spot. Especially push notifications and HTTPS—sending a test message and performing an HTTPS check during the joint debugging session is more practical than reading documentation. According to experience ranges, finishing this type of environment cleanup generally takes 0.5–1.5 days. If the outsourcing quote does not mention this, it can easily become "extra working hours" during acceptance.

Applicable Scenarios and Boundaries

The methods in this article are suitable for common custom mobile projects with a budget under 100,000 RMB and a development team of 2–5 people, especially for clients who are developing an app for the first time. If your company already has an operations team or a group compliance department, environmental items may already be managed internally, and there is no need to discuss "full outsourcing vs. client-provided" as an outsourcing decision.

Furthermore, if the project involves significant hardware interaction or large-scale backend modifications, the environmental complexity increases significantly, and the cost and workload ranges mentioned above must be re-evaluated. Do not cut corners on environment acceptance to save money, because the cost of a revoked certificate or server downtime after launch usually far exceeds the deployment fee you might save.

Frequently Asked Questions

How long does domain ICP filing take? Can it be expedited?

The routine filing period is 5–15 working days (experience range); some provinces or local bureaus may take longer. There is no official expediting channel. Preparing materials in advance and double-checking the business license and ID photos can avoid repeated rejections.

How much does a server cost per year? What if the outsourcing quote doesn't mention it?

A lightweight application server typically costs between 500 and 2000 RMB per year (experience range), depending on the configuration. If the quote doesn't mention it, proactively ask whether server costs and deployment hours are included.

If I use an overseas server, do I still need ICP filing?

Overseas servers indeed do not require domestic ICP filing, but access speed for domestic users may be slower. Additionally, some app reviews or payment interfaces require domestic filing. You cannot simply rely on overseas servers as a shortcut.

If the outsourcing contract doesn't mention servers and filing, can I add them later?

Yes, but this is usually quoted as an additional requirement. It's recommended that before signing, you ask the vendor to include an attachment specifying the "environment preparer" and the "deployment acceptance standard," to avoid disputes later.

Before signing, send the environment checklist to your potential development partner and ask them to mark ownership and timelines for each item. You can usually receive feedback within half a day. If the vendor is unwilling to fill out this checklist, their cooperation during the launch phase may be limited. Remember: the true end point of custom mobile development is when the product can run stably in a production environment, not the moment source code is delivered.