Nexoracode

Practice

One practice, several instruments

We are deliberately broad in craft and narrow in focus: we build and look after software products for organisations that need a dependable technical partner rather than a large agency.

New web applications

From a booking system for a local service to an internal tool replacing a dozen spreadsheets. We map the data first, then the screens, then the code. Typical stacks include TypeScript, PHP, Python and PostgreSQL or MySQL.

  • Discovery and data modelling
  • Server-rendered or hybrid front ends
  • Authentication and roles
  • Automated tests on critical paths

Mobile applications

Native Swift and Kotlin when the device is central to the product; cross-platform when one team must serve both platforms. Either way, offline states, permissions and accessibility are designed rather than patched.

  • Platform choice with written reasoning
  • Offline-first data where it matters
  • Push notifications done respectfully
  • Store listings and submissions

Interface design

Research-light, task-heavy design. We interview a handful of people, write their tasks down and prototype until the routes are short and clear. The output is a component library, not a pile of static screens.

  • Task mapping and flows
  • Clickable prototypes
  • Accessible component library
  • Design-to-code handover

Publishing and release support

For teams who can build but struggle to ship: pipelines, store submissions, release notes and rollback plans.

  • CI/CD pipelines
  • Store submissions and review replies
  • Staged rollouts
  • Release documentation

Maintenance and support

Regular dependency updates, operating system compatibility, small improvements and help when something breaks, within agreed working hours.

  • Monthly update cycles
  • Issue triage by email form
  • Written change log
  • Annual technical review

Codebase rescue

When you inherit a product whose original developers have gone. We read before we rewrite, document what exists, and make the smallest changes that restore confidence.

  • Two-week audit
  • Risk register in plain English
  • Test harness around fragile parts
  • Gradual modernisation plan

What we do not do

We do not give financial, legal or regulatory advice, we do not resell hardware, and we do not run paid advertising. Where a project needs specialists in those areas, we will say so and work alongside the people you choose.

How engagements are shaped

Fixed discovery

A short, fixed-price phase that ends with a written plan, a prototype and an estimate with stated assumptions.

Fortnightly delivery

Build proceeds in two-week phrases with a working preview at the end of each, billed per phrase.

Ongoing care

A support arrangement sized to the product, reviewed every quarter so it never drifts from what you need.

Discuss a project