SERVICES
iOS and macOS app development
An app is more than a smaller screen. It needs to work at the moment and on the device where it is useful: checking a commitment, finding a document or interacting with a game. We start with that action to assess the interface, technology and necessary checks.
For people planning an Apple experience
This service is for people with a task to bring to iPhone, iPad or Mac who want to understand a sensible first version. We describe who will use the product, how often and under what conditions. Connectivity, available storage, screen dimensions and input methods are constraints to consider early. Availability on one platform does not automatically establish functionality on the others.
Interface, records and behaviour
We assess primary flows, empty states, errors, permissions and recovery after an interruption. MyNABI provides a reference for personal organisation; NOVA Rush and Emberwatch demonstrate game interactions. Their choices differ: the portfolio includes SwiftUI, SpriteKit and the MyNABI web interface brought to mobile with Capacitor. These cases help frame a discussion without prescribing the same solution for every app.
Release and boundaries
Accounts, content, test devices and connected services need to be identified in the project. A successful build does not establish that purchases, notifications or a camera were tested on a real phone. Store review is a separate step and we do not guarantee its outcome. QuietShield remains a desktop prototype: it illustrates interface and state design, not a certified commercial product ready for release.
How we work
We begin by discussing the task and the existing tools. We describe the expected result and choose an initial journey to observe. A prototype lets us discuss the sequence, information and states before extending the work. Verification then follows the agreed cases, including errors and missing records. A demonstration and a completed check are recorded separately.
What to prepare
Bring a description of the activity, an example without confidential information and the main difficulties. Identify who will use the result and which constraints cannot change. When something is undefined, we record an open question. Scope, timing and cost can only be assessed after that initial review; the website does not imply a standard package or guaranteed delivery date.
Explore real project examples
Review the screens, technical choices and stated status of each project. These examples describe documented work, not promised outcomes for your project.
Frequently asked questions
Will it be a native app?
The choice depends on features and constraints. We compare the required interaction with the available technologies instead of choosing a label before understanding the problem.
Is App Store publication included?
Accounts, materials, responsibilities and checks need to be agreed. Linking to a published portfolio app does not promise approval for a new project.
How do you check mobile behaviour?
We distinguish automated and simulator checks from physical-device tests. The verification plan identifies the flows tested and any checks still outstanding.
Tell us about your situation
Start with an activity, a difficulty or an example without confidential information. We can discuss the expected result and what needs clarification before the work is defined.
Discuss your project