Skip to content

Our process

How a project runs.

Every AppCodera project follows the same eight stages. Each one ends with something you can review, and work moves on only when you have approved it.

Eight stages

From requirements to support.

The gold text under each stage shows where your review or approval is needed.

  1. 01

    Discovery and requirements

    We learn about your business, users, existing systems and constraints, and write down the requirements.

    You confirm the requirements.

  2. 02

    Scope and planning

    We define what the first release includes, split the work into phases and milestones, and prepare a proposal with cost and dependencies.

    You approve the proposal and scope.

  3. 03

    UX/UI design

    User flows, wireframes and visual designs for the key screens, with a clickable prototype where it helps decisions.

    You approve the designs before development.

  4. 04

    Architecture and technical planning

    Platforms, data model, integrations, hosting and security are decided and documented.

    You confirm hosting, accounts and third-party services.

  5. 05

    Development

    We build in milestones, sharing working versions so you can test features as they are completed.

    You review each milestone.

  6. 06

    Quality assurance

    Functional testing across the agreed devices and browsers, fixes, and a check against the approved scope.

    You carry out acceptance testing.

  7. 07

    Deployment

    Release to your servers or app stores, configuration of domains and services, and hand-over of access and documentation.

    You sign off the release.

  8. 08

    Maintenance and support

    Fixes, updates and new features after launch, under a separate support arrangement if you choose one.

    Support terms are agreed in writing.

Ground rules

How we keep projects predictable.

  • Nothing starts without a written proposal

    Scope, phases, cost, dependencies and what we need from you are agreed in writing before work begins.

  • Timelines follow discovery

    We give a timeline once the requirements are clear. We don't promise delivery dates before the work has been assessed.

  • Changes are agreed, not assumed

    New requests during a project are written up as change requests, with their effect on cost and timeline, for your approval.

  • You test before you sign off

    Each release goes through your acceptance testing. Defects found are fixed before hand-over.

We Build What's Next.

Tell us what you want to build.

Share your idea, brief or existing product. We will reply by email with questions, a suggested approach and the next steps towards a proposal, and arrange an online meeting when it helps.