statictrace connect

Services

Four processes.
Run one or chain them.

Expand any process below to read its scope, what you receive at the end and whether it suits you. The first one is open already.

[mobile] Mobile applications — iOS and Android apps shaped around one clear job.
scope
  • Scoping workshop that reduces an idea to the first useful version
  • Native or cross-platform recommendation, with the trade-offs written down
  • Offline behaviour, permissions and notification decisions agreed early
  • Test builds shared through TestFlight or Play internal testing
  • Accessibility checks: dynamic type, screen readers, touch target sizes
output
Files you own at the end: written scope, design source, repository access where relevant, and a short handover note on what to do next.
fit
Best for: founders and small organisations with a defined audience and a task people repeat.
[design] UI/UX design — Interfaces people understand without instructions.
scope
  • Plain-language user journeys before any visual polish
  • Wireframes you can click, so problems surface cheaply
  • A small design system: type scale, colour, spacing, components
  • Contrast and keyboard checks against WCAG 2.2 AA
  • Annotated handover so developers do not have to guess
output
Files you own at the end: written scope, design source, repository access where relevant, and a short handover note on what to do next.
fit
Best for: existing products that confuse people, or new ones that need a clear plan.
[web] Web design & development — Fast, maintainable websites and web applications.
scope
  • Static or server-rendered builds chosen for speed and low upkeep
  • Content structure, page titles and descriptions written for real searches
  • Forms that validate kindly and fail honestly
  • Hosting, domain and email setup explained in your terms
  • Documentation so another developer can take over
output
Files you own at the end: written scope, design source, repository access where relevant, and a short handover note on what to do next.
fit
Best for: organisations that want a site they can own rather than rent.
[publishing] Publishing & release — Careful preparation for App Store, Google Play and the web.
scope
  • Store listing copy, screenshots and privacy labels prepared together
  • Review-guideline check before submission, not after rejection
  • Versioning, release notes and a rollback plan
  • Data safety and privacy policy consistency
  • Post-launch checklist for the first fortnight
output
Files you own at the end: written scope, design source, repository access where relevant, and a short handover note on what to do next.
fit
Best for: anyone about to release something and keen not to be surprised.

IT help for existing clients and small teams

Domain and DNS questions, email setup on your hosting, website forms that stop sending, and app store account access. Practical help in working hours, by email or phone. See support.