Why the questions matter more than the résumé
Most problems with freelance projects are not about skill. They come from unclear expectations: the owner imagined one thing, the developer built another, and nobody wrote down who owns what. A few direct questions before work starts can prevent most of that. This is general guidance, not legal advice. For anything involving significant money or rights, consider having a qualified professional review the agreement.
Be clear on what you want first
You cannot evaluate a proposal if you have not defined the job. Before contacting anyone, write a short description of the problem the app solves, who it is for, and the few things the first version must do. Simple user stories work well for this, since they describe features from the person’s point of view. A rough sketch on paper helps too; the habit of making paper wireframes lets a developer see your intent at a glance.
If you are still testing whether people want the idea, work through app idea validation first. Paying for development before you know anyone needs the app is a common and costly mistake.
Questions about scope
- What exactly is included in your estimate? Ask for a list of screens or features, not just a total.
- What is not included? Common gaps are design work, testing on several devices, store submission, and backend setup.
- How do you handle changes? Some change is normal. Ask how a new request is priced and how it affects the schedule.
- Can the work be split into stages? Smaller milestones let you review progress and stop if things go poorly, rather than waiting for one big delivery.
- What assumptions are you making? Developers often assume things about devices, languages or services that you may not share.
Questions about ownership
Ownership is the area most often left vague, so raise it early and get the answers in writing.
- Who will own the finished code and design? Do not assume it is you automatically; it depends on the agreement.
- Whose name will the store accounts be under? Ideally the developer account for publishing is yours, so you control the app’s listing and can change developers later. The process is outlined in app store publishing.
- Who holds the accounts for hosting, databases and other services? Again, they should generally be in your name, with the developer given access.
- Will you use third-party code or libraries, and under what licenses? Reputable developers should be able to list these.
- Will I receive the source code and documentation? Ask what format and when.
Questions about communication
- How will we stay in touch, and how often? A weekly check-in with something to look at is a common rhythm.
- What is your usual response time, and which time zone do you work in? Neither answer is wrong, but mismatches cause frustration.
- How will I see progress? Working builds you can try beat verbal reports.
- What happens if you become unavailable? A reasonable freelancer will have thought about handover, and you should keep copies of the code regularly. Developers who use version control make this much easier, since the full history is in one place.
Questions about quality and testing
- How do you test the app? Ask about real devices, older phones and different screen sizes. The practices in guides to app testing tools and older device testing give you a sense of what a thorough answer looks like.
- Who is responsible for fixing bugs found after delivery, and for how long? Get a defined period in writing.
- How will you handle privacy and security? A good answer includes collecting only needed data, secure storage and care with app permissions. If the developer cannot explain it simply, consider that a warning sign.
Questions about money
- Is the price fixed or hourly? Fixed prices give certainty but depend on a well-defined scope. Hourly arrangements give flexibility but need regular budget checks.
- What is the payment schedule? Payments tied to completed milestones are typically safer for both sides than paying everything upfront.
- What other costs should I expect? Store fees, hosting, and third-party services can add up, which ties back to setting an app budget that includes running costs.
Questions about after launch
An app is not finished when it ships. Phones change and users report problems.
- Do you offer maintenance, and what does it cover? Operating system updates can affect an app, which is why keeping an app compatible with new releases deserves a plan.
- How would a handover to someone else work? Ask what documentation you will receive.
- Who handles user support? If it is you, you may still need the developer to investigate crash reports.
Checking the person
Ask to see past work, and if possible try the apps yourself. Contact a past client if they are willing to talk. Notice whether the person asks you good questions about your users; a developer who only quotes a price without asking what the app is for may not be thinking about your needs. Be wary of anyone who promises guaranteed results such as particular download numbers or revenue, since nobody can honestly promise those.
Put it in writing
Whatever you decide, record the scope, schedule, payments, ownership and ending terms in a written agreement both sides sign. Clear paperwork protects the freelancer as much as you. A good working relationship usually starts with direct, polite questions and honest answers, and you will learn a lot from how the person responds to them.