Services

Service line 1

Apple platform engineering

Native iOS and macOS development in Swift and Objective-C: new features, legacy rewrites, and maintenance of existing client codebases.

Delivered as source code, distributed under the client's own Apple Developer account: signing identity and App Store listing remain theirs.

• Swift application development for iOS and macOS
• Objective-C maintenance and interoperability
• Build configuration and code-signing setup
• Integration into the client's CI and source control

Service line 2

Cross-platform and embedded software engineering

Flutter and Dart development for one codebase across mobile and desktop. For an electric-vehicle client, this meant the application layer of the tool used to monitor the battery system.

The same engagement required Dart implementations of RPC and bulk data-transfer protocols, in the style of Pigweed's pw_rpc and pw_transfer, to communicate with the embedded controller, plus architecture notes. For an industrial client this has meant Android and Linux applications in Qt/C++. For a health-technology client this meant a Flutter research application for iOS, Android and web.

• Flutter/Dart application development
• Qt/C++ application development
• RPC protocol implementation in Dart
• Bulk data-transfer protocol implementation
• Embedded device communication layers
• Architecture notes

Service line 3

Technical consulting and architecture

Architecture reviews, protocol and integration design, and technical documentation for teams needing a senior opinion.

• Architecture reviews
• Protocol and integration design
• Technical documentation
• Delivery and time-progress reporting

Engagement models

Work is structured one of three ways, chosen at the scoping stage:

• Embedded engineer. A senior engineer joins the client's team for the contract's duration, billed by the hour, day or month.
• Fixed-scope project. A defined piece of work, quoted and delivered against an agreed scope.
• Advisory. A shorter architecture review or consulting engagement, without full-time embedding.

Engagement terms

Every engagement is a contract arrangement between two companies. A non-disclosure agreement is available on request. Progress is reported monthly, adjusted to the client's preferred cadence. Work is delivered through the client's own git repositories and CI, with Docker-based builds where the client uses them. AI-assisted tooling (Claude Code, Cursor) is used where the client permits it; every line delivered is reviewed and owned by the engineer.