App design

Native iOS, macOS and web apps, from discovery to the App Store.

We design and build the app, submit it, and hand over the source and the account access. You own all of it.

Line drawing: a laptop and a phone on a timber desk, showing the same app screen.
A line drawing stands in for a photograph: the same screen on a laptop and a phone.

What you get

Five things, in order

Each one is a file or an account you keep.

  • Discovery notes and a one-page scope: what the app does, for whom, and what it does not do.
  • A clickable prototype, to test the idea with real users before you pay for a build.
  • Design files and a component list, so the next person can extend it.
  • The build, TestFlight and App Store submission, under your developer account.
  • Source code in your repository and a hand-over note that explains how to run and release it.

How we work

Three habits, the same for every job

  1. Step 1: Scope in writing

    A short call, then a one-page scope: what we will deliver, what we will not, the price and the date.

  2. Step 2: Work you can see

    Drafts, test builds or the plan as it forms. Questions go to one address and get answered.

  3. Step 3: Hand over everything

    Files, source, access and a written summary. Nothing you would need later stays with us.

Who does the work

Operations experience behind every job

Coop Security is run by Jacob, whose background is managed cloud operations: a private cloud of 40 customers and about 350 virtual machines, Microsoft public-cloud services delivered to resellers and their customers, and security reporting on Azure tenants as a service.

The same discipline carries into the apps: the server side, the deployment and the hand-over note are part of the build. The map service on this site is an example, built as a static site, a small API and a documented interface a native app can drive.

Certified on AWS (Solutions Architect Associate, 2022; AI specialty, 2026) and Azure (Administrator Associate, 2024). Based in Canberra; work is done remotely or on site in the ACT and surrounding NSW.

Background and history: LinkedIn · code: GitHub.

Engagement sizes

Three ways to engage

Each is priced in the scope, with the date beside it.

  1. Prototype

    Two to four weeks. Discovery notes, a clickable prototype and a short report on what users did with it.

  2. Small app

    Scoped per project. Design, build, submission and hand-over for one app with a clear job.

  3. Ongoing

    Monthly. Releases, fixes and the account housekeeping after launch, with a written note each month.

Every price is written into the one-page scope before work starts, GST stated. We say no when we are full.

Questions

Before you ask

Anything else: [email protected]

How long does it take?

A prototype takes two to four weeks. A small app is scoped per project: the scope gives the date, and the date does not move without a written change.

What do you need from us?

Someone who can answer questions within a day or two, a developer account in your name (we help you set it up), and whatever already exists: sketches, a spreadsheet, the old app.

Nothing else has to be ready before the first call.

What is not included?

Marketing, app-store optimisation, ongoing content and any feature outside the written scope. Those are quoted separately if you want them.

Who does the work?

The person named above, who also answers your questions. Nothing is subcontracted without telling you first.

What happens at hand-over?

You get the source in your repository, the design files, the account access and a note that explains how to run, test and release the app. We walk through it with you once.

Tell us what you need

We reply within [two working days] with questions or a one-page scope.