Independent app development studio

Apps, made properly.

appl.dev plans, designs, and builds native and web applications — from the first sketch to the release build, and the maintenance that comes after it.

Platforms
iOS, iPadOS, macOS, Web
Based in
Oregon, USA
Availability
Booking projects for early 2027

Services

Take one, or take the whole path from idea to store.

Product scoping
Turn an idea into a written scope: who the users are, the core flows, what ships first and what waits. You get a document you can hand to any developer.
Interface design
Wireframes and finished screens that follow each platform's own conventions — including the empty, loading, error, and offline states most designs forget.
Native apps
Swift and SwiftUI for iPhone, iPad, and Mac. Platform frameworks first; third-party code only when it clearly earns its place.
Web applications
Fast, accessible web apps built on standard HTML, CSS, and TypeScript, deployed to the host you choose and documented so your team can run them.
Maintenance
OS updates, dependency upgrades, crash triage, and performance work for apps that are already live — including apps someone else built.

Process

Five steps. Each one ends with something you can see, install, or keep.

  1. Define

    Agree on the problem, the users, and what "done" means.

    You keep: a written scope

  2. Prototype

    A clickable prototype, tested with real people before any production code.

    You keep: the prototype

  3. Build

    Short iterations. At the end of each, a build you can install and judge.

    You keep: every build

  4. Ship

    Store submission, release notes, and a launch checklist that is actually checked.

    You keep: the release

  5. Maintain

    Updates for new OS versions, fixes, and small improvements on a plan you set.

    You keep: a healthy app

Principles

The rules applied to every project, whatever its size.

  • Small surface area

    Fewer screens, fewer settings, fewer dependencies. Every feature has to justify its maintenance cost.

  • Accessible by default

    Dynamic Type, VoiceOver, keyboard access, and sufficient contrast are part of the first build, not a later ticket.

  • Fast on old devices

    Performance is tested on the slowest hardware your users still carry, not only on the newest.

  • Code you own

    The repository is yours from day one, with a README that explains how to build, test, and release.

  • Estimates in ranges

    Software has uncertainty. Estimates say so honestly, and narrow as the work becomes clear.

  • Plain communication

    Progress notes in plain language: what was done, what's next, and what needs your decision.

Contact

Send a short note: what you want to build, who it's for, and when you need it. A first reply includes questions, not a sales pitch.

Response time: within two working days

Jump to a section