Sounding 020 m
Services, by depth.
Each service below explains what you get, what we need from you, and where the usual hazards lie.
iOS and Android applications
We build native apps in Swift and Kotlin when performance, platform conventions or device features matter most, and cross-platform apps when one codebase serves both stores well. The choice is made in discovery and recorded with its reasons, including what it would cost to change course later.
- Architecture note covering offline behaviour, authentication, push notifications and data storage on the device.
- Fortnightly test builds distributed through TestFlight and Google Play internal testing.
- Automated tests around the parts that would hurt most if broken: sign-in, payments, sync.
- Accessibility checks with VoiceOver and TalkBack, dynamic text sizes and contrast.
Portals, dashboards and public products
Server-rendered or single-page, whichever suits the audience. We care about first load on a mid-range phone over a patchy connection, keyboard access, and pages that still make sense when JavaScript fails. Back ends are designed for the data you actually have, with clear boundaries so future features do not require a rewrite.
We build to WCAG 2.2 AA as a working target and tell you honestly where a third-party component falls short.
Design that has been tried on real tasks
We begin with the jobs people need to do, not with a mood board. Low-fidelity flows come first, then clickable prototypes tested with a handful of representative users. Only then do we refine visual design and assemble a component library that developers and designers share.
Deliverables typically include user flows, an annotated prototype, a design token set and a short rationale document explaining the decisions that were contested.
App store and release management
Store submission is its own discipline. We prepare listings, screenshots, privacy nutrition labels and Data safety forms, demo accounts for reviewers, and age-rating questionnaires. If a review is rejected we read the guideline cited, fix the cause and respond. More on publishing.
Maintenance after launch
Operating systems update every year, SDKs are deprecated and certificates expire. A support arrangement covers monitoring crash reports, dependency and security updates, compatibility testing against new OS releases and a fixed route for reporting problems. Response targets are agreed in writing per engagement; we do not promise round-the-clock cover we have not agreed to provide.