An app is a longer-lived commitment than most software projects. It outlives the build and needs active maintenance against OS updates for as long as it's live. That makes the hiring decision higher-stakes than most engagements, and the standard agency pitch (portfolio, logos, a demo reel) tells you almost nothing about the three things that actually determine whether this goes well.
Ownership: accounts and code, from day one
Set up your own Apple Developer and Google Play Console accounts before the agency starts, and have the app published under those accounts, not the agency's. The same applies to the codebase and any backend infrastructure. This isn't a trust issue specifically; it's that untangling ownership after the fact (transferring a published app between developer accounts, recovering a codebase from an agency's private repo) is genuinely painful and sometimes contentious, and it's entirely avoidable by setting it up right at the start.
Maintenance: get a specific answer, not a vibe
Ask directly: when iOS or Android ships an update that breaks something in the app, who fixes it, on what timeline, and under what commercial arrangement? A serious agency has a retainer structure or a clear hourly on-call rate ready to describe. A vague "we'll sort it out" means there's no actual plan, and you'll discover that the first time a major OS release breaks a core flow with no one contractually on the hook to fix it.
Platform fit: discovery before recommendation
| Kryeo | Framework-first pitch | |
|---|---|---|
| Order of operations | Understand features, data, and platform needs first | Pitch React Native or Flutter before hearing the brief |
| Platform decision basis | Named capability requirements (hardware, offline, push) | 'This is just what we build everything in' |
| Willingness to recommend native | Will say so when the brief actually needs it | Cross-platform regardless of fit, because it's cheaper to deliver |
A good agency's framework recommendation should be traceable to something specific in your brief, see React Native vs. Flutter vs. native for the actual decision factors, not a default they apply to every client.
About to hire for an app build?
Send us your feature list and current stack. We'll tell you the platform we'd recommend and why, plus exactly how ownership and maintenance work on our engagements.
Get a second opinion →The short version
Ownership set up correctly from day one, a specific and committed answer on post-launch maintenance, and a platform recommendation that traces back to your actual feature list, not a default pitch. Any agency that's straightforward on all three, regardless of portfolio size, is worth a real conversation. See how we run this on our own engagements in how a Kryeo engagement actually runs, and the cost shape to expect going in at how much custom mobile app development costs.