All articles

Local or remote app developer? Planning the working relationship

When an Okanagan app project benefits from in-person work, when remote collaboration works well, and how to organise reviews and handover.

A nearby developer can join a workshop or visit your workplace. A remote team may have experience that is a closer match for the product. The useful question is which parts of the work benefit from being together, and how the rest will be coordinated.

We work from Kelowna and Vancouver with clients locally and elsewhere in Canada and the US. This guide focuses on collaboration. For team types, see freelancer, agency or studio; for proposals, use the app quote checklist.

When an in-person session earns its time

Meet on site when the environment is part of the problem. A tool used by a crew, a product connected to physical access or a workflow shared across a front desk and back office can be easier to understand by observing it.

Modern Cue Club connects membership software and table booking with a planned door-access integration. That kind of project raises questions about the physical arrival experience alongside the screens. The venue and access work remain in development; a local visit is a way to investigate assumptions, not a substitute for testing them.

A workshop can also help when several people have different accounts of the same process. Have them walk through one real example and agree who makes each decision.

When remote collaboration works well

Remote work is practical when the important flows can be demonstrated, the right people are available for decisions and progress is visible between meetings.

For a product such as RetireMint, working through an assessment and reviewing its results together gives more specific feedback than discussing a screenshot in isolation. The same is true whether the review happens across a table or on a call.

Ask for a representative working preview early. Try the whole task yourself, then describe where the experience differs from what you expected.

Agree on a review routine

Decide these points before the build begins:

  • Decision owner: who can approve a change when stakeholders disagree?
  • Review format: working build, prototype or a specific document, depending on the milestone.
  • Feedback location: one place where the team can see decisions and unresolved questions.
  • Availability: overlapping hours, expected response times and coverage for absences.
  • Review window: how long your team has to test a milestone before the schedule moves on.

A weekly meeting may be useful, but the important part is what you can review and decide. Status updates should name what works, what is uncertain and what needs your input.

Write feedback around a task

“Make the dashboard better” is difficult to act on. “I need to see which invoices need attention before I call a client” gives the team a task to investigate.

Include the starting point, what you tried, what happened and what you expected. Use a screenshot or short recording when it helps. Separate a bug in agreed behaviour from an idea for a later release so both get an appropriate response.

Plan continuity, wherever the team is based

Location does not guarantee a good handover. Agree how code, designs, accounts, setup instructions and release knowledge will be available to your business. Ask who handles urgent issues and what happens if a key person is unavailable.

For existing software, establish who has authority to change each system. For new software, decide who owns the recurring supplier accounts and receives their billing and service notices.

Choose experience and a workable process

Shortlist people who can explain comparable work, then test the working relationship with a concrete scoping conversation. Notice whether they ask about your users, constraints and daily operations, and whether their proposed process fits your availability.

Our Kelowna app-development page describes our local work and approach. If you have a workflow to improve, send us a short description. We can decide together which parts need a workshop and which can move forward in working previews.

Written by westcode.io, an independent studio in Kelowna and Vancouver. Updated October 22, 2026.

Apps & products3 min read

App development in Kelowna: freelancer, agency or studio?

Choose a delivery team for your app by responsibilities, specialist needs and capacity. A practical comparison of freelancers, agencies and studios.

Apps & products3 min read

Comparing app-development quotes: a checklist for Kelowna businesses

Compare app proposals on scope, integrations, testing, ownership, running costs and support before choosing a developer.

Apps & products3 min read

Planning a mobile app in Kelowna: from idea to first release

A practical first-release plan for an app: users, workflows, admin tools, milestones and launch, with examples from Westcode projects.