What we do
Where we can lend a hand.
Four kinds of work, each described in plain terms. Open the notes under each to see what is involved and what stays with you afterwards. Most projects draw on two or three of them.
Jump to: Mobile applications · UI/UX design · Web design & development · Publishing & release
Mobile applications
We plan and build apps for iOS and Android, choosing between native and cross-platform approaches according to your needs rather than our habits. Most first versions are smaller than people expect; we help you find the version worth shipping.
Ask early about permissions. Camera, location and contacts all need a clear reason the reviewer and the user can understand.
What the work involves
- Discovery workshop and written problem statement
- Choice of native or cross-platform technology, explained
- Offline behaviour, notifications and permissions planned up front
- Accessibility: dynamic text, screen readers, contrast
- Testing on real devices across common screen sizes
- Handover documentation and source code ownership
What you keep at the end
- A scoped feature list with must, should and later
- Working builds you can install during development
- A maintenance outline for operating system updates
UI/UX design
Good design here means the next step is obvious. We map journeys, sketch, prototype and test with a handful of real people before polishing anything.
Five well-chosen test participants will usually reveal most of the serious problems in a flow.
What the work involves
- User journeys and task analysis
- Information architecture and navigation
- Wireframes and clickable prototypes
- Visual interface design and a small component library
- Content design: labels, error messages, empty states
- Light usability testing with five or so participants
What you keep at the end
- Prototype links you can share
- Annotated design files ready for development
- A short findings note from testing
Web design & development
From a clear organisational site to a logged-in web application, we build for speed, readability and accessibility, with hosting you understand and can control.
If a page needs a cookie banner longer than its content, it probably has too many trackers.
What the work involves
- Static and content-managed sites
- Web applications and simple customer portals
- Responsive layouts tested on phones first
- WCAG 2.2 AA as a working target
- Performance budgets and image discipline
- Contact forms, privacy notices and cookie choices done properly
What you keep at the end
- A site deployed to hosting you own
- Admin guidance written for non-specialists
- A list of known limitations, not just features
Publishing & release
Getting through App Store and Google Play review is its own discipline. We prepare listings, privacy declarations, screenshots and release notes, and we plan staged rollouts so problems surface early.
We cannot guarantee store approval; nobody honestly can. We can make rejection less likely and easier to resolve.
What the work involves
- Developer account set-up guidance (accounts stay in your name)
- Store listing copy, screenshots and age ratings
- Privacy nutrition labels and data safety forms
- TestFlight and internal testing tracks
- Staged rollout and rollback planning
- Post-release monitoring checklist
What you keep at the end
- A release checklist specific to your app
- Submitted builds and a record of reviewer feedback
- Notes for the next update cycle
Things people usually ask next
Do you work on fixed prices?
For well-defined pieces, such as a design sprint or a store submission, yes. For open-ended builds we prefer phased estimates reviewed at each stage.
Who owns the code and designs?
You do, once invoices for that work are settled. Accounts for stores, domains and hosting should be in your organisation’s name.
Can you take over an existing project?
Often. We start with a short paid review so we can tell you honestly what state it is in.