Frequently asked

Working together

What does it cost to build an app?

We quote per project after a scoping conversation, because the honest answer depends entirely on what the app has to do. The things that move the number most are: how many distinct screens there are, whether it needs accounts and a server behind it, whether it has to integrate with anything external (payments, HealthKit, hardware, an existing API), and how much of the design is starting from a blank page.

We would rather help you scope a smaller first version you can actually ship than quote a figure for something neither of us has thought through yet. That scoping conversation is free.

Do you work with people who aren't technical?

Often, yes. You don't need to know what SwiftUI is or how the App Store works — that's the part we're bringing. What genuinely helps is that you know your users and can tell us when something we've built doesn't match how they actually behave.

Can you take over an app someone else built?

Yes, and it's a good chunk of what studios like ours do. We start with a paid code review — usually a few days — before committing to ongoing work. Inherited codebases vary enormously, and it isn't fair to either of us to quote a maintenance arrangement before we know what's actually in there. If the review finds that a rewrite would cost less than maintaining what exists, we'll tell you that plainly, even though it's the more expensive answer.

How long does it take?

A focused first version is usually measured in weeks. Anything with user accounts, a backend, or several external integrations moves into months. We'll give you a range at scoping and update it as we learn — a schedule that never changes is usually one nobody is checking.

Who owns the code?

You do. We settle it in writing before work starts: the application code, the designs, and the App Store listing assets are yours. We keep the right to reuse generic building blocks — the kind of utility code that ends up in every project — but nothing specific to your product.

The App Store

Do I need my own Apple Developer account?

If the app belongs to your business, we'd encourage it. The app is published under your organization, the App Store lists your company as the seller, and you keep control of the listing, the reviews, and the revenue regardless of what happens to our working relationship. We can publish under Kahcozi's account instead if you'd rather not deal with the enrollment, but it does mean the app lives under our name.

How long does App Review take?

Apple states that on average 90% of submissions are reviewed in less than 24 hours. In practice the first submission from a brand‑new developer account often takes longer, and every rejection restarts the clock. We build against the App Store Review Guidelines from the beginning rather than treating them as a final hurdle, which is the main thing that keeps that number low.

What happens if Apple rejects the app?

It's more common than people expect and usually fixable in a day or two. Most rejections come down to a privacy disclosure that doesn't match the binary, a missing account‑deletion path, unclear subscription terms, or a reviewer not finding a feature. We handle the correspondence with App Review and tell you what changed and why.

Privacy, platforms, and afterwards

Do your apps collect data about me?

As little as they can while still working. No advertising SDKs, no behavioural tracking, no selling of personal information; what you create stays on your device or in your own iCloud. There's a diagram of exactly where data does and doesn't go on the Privacy Policy page.

Do you build for Android as well?

No. We build for iOS and iPadOS only, and we'd rather say so plainly than take the work and subcontract it. The trade‑off is deliberate: staying on one platform is what lets us keep up with what changes there every year. If you need both platforms, we're only the right fit for half the job.

What happens after the app launches?

Every app we ship gets a published support channel and a maintenance path. In practice that means watching crash reports after a release, fixing what surfaces, and doing the yearly work of keeping the app healthy through new iOS versions and new hardware. We'll agree what that looks like before launch rather than after.

How quickly do you reply?

Within two business days, to any message, at [email protected]. We're a small studio on US Pacific time. If a week passes without an answer, please send it again — it means your message didn't reach us.