Milestone plan for a mobile app dream in Shenzhen

Milestones keep money and progress together. Backers fund the whole mobile app dream, but money is released one milestone at a time, only after you show proof.

A mobile app budget must connect screen designs to working features, device testing and a maintainable release. Show usable builds at each stage rather than treating downloads as proof.

Example milestone plan

An example plan for a mobile app dream with a goal of CN¥200,000. Backers fund the whole goal, but each milestone's money stays held until you post the proof and Backers release it.

  1. Milestone 1

    CN¥30,000 · 15%

    Validate the core flow

    Post an interactive screen prototype, a prioritised feature list and anonymised notes from guided usability sessions.

  2. Milestone 2

    CN¥80,000 · 40%

    Build the main features

    Share a recorded walkthrough of a working app build, completed feature checks and a summary of remaining development tasks.

  3. Milestone 3

    CN¥50,000 · 25%

    Test across devices

    Upload a device test matrix, anonymised crash reports and before-and-after evidence for the main issues resolved.

  4. Milestone 4

    CN¥40,000 · 20%

    Prepare the release build

    Post release build screenshots, setup documentation and a maintenance checklist with credentials and private data removed.

  1. 01

    Make every step provable

    A milestone only works if a Backer can look at your proof and agree it is done. 'Buy equipment' is weak; 'equipment bought, receipt and photo posted' is strong.

  2. 02

    Order by risk

    Put the cheapest, fastest step first. Each released milestone proves you deliver and funds the next. Leave the biggest amount for the step where most of the work is already done.

  3. 03

    Keep the amounts honest

    Milestones must add up exactly to your goal. Price each step from real quotes, include tools and services, and split any step that is too big to prove in one go.

Risks to plan for

  • R1

    Feature scope keeps growing

    Extra features can absorb development time before the core flow works. Lock the first build scope in the prototype milestone and keep optional ideas outside its budget.

  • R2

    Device-specific failures

    A build that works on one phone may fail on another screen or operating system. Budget for a defined device test matrix and reserve time for fixes before release preparation.

  • R3

    External service changes

    An app may depend on services with changing limits or interfaces. Identify those dependencies early and include integration checks and a fallback plan in the release work.

Budget example

A typical cost split for a mobile app dream in Shenzhen, shown in CNY. Backers are charged the equivalent in US dollars.

Example goal

CN¥200,000

  • App design and developmentCN¥130,000 · 65%
  • Hosting and service integrationsCN¥20,000 · 10%
  • Device testing and quality checksCN¥30,000 · 15%
  • Release and maintenance reserveCN¥20,000 · 10%

What you receive

Backers give
CN¥200,000
Platform fee (15%)
−CN¥30,000
You receive
CN¥170,000

How Backers are protected

14-day review per milestone

When proof is posted, each Backer has 14 days to release their share or ask for more. Money not released in time goes back to the Backer.

15% fee, deducted — never added

Backers pay exactly what they choose. The 15% fee comes out of each backing: CN¥1,000 gives the Dreamer CN¥850. The fee is kept if money is returned.

Gifts, not shares

Backings are gifts. No shares, equity, interest or repayment, and Dreamers keep full ownership. Nothing on cohero is an investment or a loan.

Questions and answers

Do I need a finished app before creating a funding dream?

You can start with a clearly scoped prototype and development plan. Show which screens are interactive, which features still need code and how later milestones will provide working builds and device test evidence.

Can I share app progress without exposing user data?

Record a demonstration using invented accounts and sample content. Remove credentials from logs and screenshots, and use anonymised issue summaries so Backers can review the build without seeing real user records.

How many milestones should a mobile app dream have?

Three to six works for most dreams. Fewer gives Backers little to review; more than seven makes each step feel small. The example plan on this page uses four.

Ready when you are

Sign in or create an account to publish a dream or back the ones you believe in.

Sign in / Create account

More mobile app guides

Mobile app dreams in other cities

Other tech dreams