Mobile app development for iOS, Android, or both

What we build

The work is an installed app. Version one does one job, including the dull states: no signal, a refused permission, an empty account, a declined payment. A site that only has to fit a phone is a website quote.

We offer Swift and SwiftUI, Kotlin and Jetpack Compose, or React Native and Flutter where a shared product fits. Device integrations, widgets, Apple TV and Safari extensions need explicit platform scope. Offline data does not by itself determine the framework. We also inspect and repair existing apps, including crashes, purchase access and release-build problems.

Typical jobs

A useful first brief names the tasks: sign-in and a list from your API, offline reference search, a subscription screen, a widget, another language or a device-specific layout. If those choices are still open, discovery can define the first release and the checks needed to review it.

Narrower work shows up often. Engineering from screens you already have. An agency sub-project beside a relationship they keep. A bug list in a repository someone else started. Design, quoted alone, when the screens are still undecided. Listing copy, screenshots, and review replies, included in the build quote. We do not control how long store review takes.

How a project runs

Send the job, who uses the app, which devices are in version one, and any date that is real.

A named feature list is a fixed quote. A bug or a small change is hourly. A note that only names an industry starts as paid discovery: flows, the version-one screens, and a written estimate. You can stop there. The write-up stays yours.

You install a build before release: TestFlight on Apple, an internal testing release on Android. Ready means the agreed path works, including one failure you cause on purpose. Handoff is the repository, the steps for the next release, the accounts in your name, and the API the app calls. Few projects run at once, so you talk to the people writing the code.

The stack

Apple apps are Swift and SwiftUI: iPhone, and iPad, Mac, or Apple TV when the product needs them. StoreKit purchases, Home Screen widgets, a Safari web extension, SpriteKit, and offline SQLite are the same kind of work. Android apps are Kotlin and Jetpack Compose.

Apps we have shipped ourselves are native Apple software, not a React Native or Flutter portfolio. Share a codebase when both phones are one product and the maintainers can work in it. Stay native when a platform API is the product. Accounts and payments use your API, or we scope that API as its own line. A web companion is Next.js, React, and TypeScript, quoted apart. Accessibility, when you ask, means we implement the technical side of WCAG: names on controls, type that scales, a screen-reader path. We do not certify compliance.

Who should email

A mobile app development company is the right call when version one is specific: build it, repair it, or add the other phone. An agency can hire an app developer for hire under its own name or with credit.

If the brief is still open, paid discovery can turn it into a defined feature list and acceptance checks. If you already have a developer or agency, we can take a bounded part of the work and agree how it joins the wider project. Share the target date so we can assess capacity and dependencies before committing.

hehe.software is a small, independent studio based in Vancouver, British Columbia, Canada. We work remotely with businesses across Canada and the United States.

Proof, and what to prepare

Our nine App Store products provide concrete Apple-platform examples. Broski splits bills offline, ICD Atlas searches on-device reference data, and Tifo supports media playback on iPhone, iPad and Apple TV. They are our own products, with different interfaces and failure states. Android and shared-code work are separate offerings; their scope includes builds and checks on the platforms you commission.

Those nine are that Apple stack, taken through App Store Connect review, not a client metric.

Send the version-one job, the audience, and the devices. Designs, an API note, or a repository help if you have them. The Apple Developer account should belong to your business, and the Google Play Console account too if Android is included. Logins can wait.