APEXSOFTWARE ENGINEERING / LDN EC1 Start a project
Services / four routes

Four routes up.
One way of moving.

Each route can be taken alone or joined to another. Most projects start with design and move into build; some arrive needing only help to release what already exists.

Route 01 / Mobile development

Mobile apps for iOS and Android

We build apps around the task people open them for, then grow features from evidence rather than wish lists. Native or cross-platform is decided with you after looking at your audience, budget and the features you need on the device.

Typical questions we ask

Who opens the app, and why today rather than next week? Which devices do they carry? What must work without signal?

What can be included

  • Discovery of the first release scope
  • Cross-platform or native build, chosen and explained
  • Offline behaviour, notifications and account flows where needed
  • Test builds distributed to your own testers
  • Handover of source code to repositories you own

Route 02 / App, UI and UX design

Interface and experience design

Design is where the most expensive mistakes are cheapest to fix. We map flows, sketch, prototype and test the main paths with real people where you can arrange them, before anything is coded.

Typical questions we ask

What should a first-time user manage in under a minute? Where do people currently give up? What words do your customers actually use?

What can be included

  • User flows and task mapping
  • Wireframes and clickable prototypes
  • Visual interface design and component library
  • Accessibility checks on contrast, targets and reading order
  • Design files you keep and can hand to any developer

Route 03 / Websites

Websites that do one thing clearly

From a few well-written pages to a larger content site, we focus on speed, accessibility and plain language. Sites are built so that you can edit them or move host without asking permission.

Typical questions we ask

What should a visitor do after reading? Who updates the site? What has to stay on your current host?

What can be included

  • Structure and page copy planning with you
  • Responsive build tested at phone, tablet and desktop widths
  • Contact forms that fail honestly and protect drafts
  • Search-friendly titles, descriptions and sitemaps
  • Hosting and domain set-up guidance

Route 04 / Release assistance

Getting it released and keeping it there

Releasing an app involves accounts, listings, privacy declarations and review processes. We prepare and check these with you. Approval is decided by the stores, so we never promise it, but we can make the submission complete and clear.

Typical questions we ask

Who owns the developer accounts? Has the app been rejected before, and why? What happens on launch day if something breaks?

What can be included

  • Developer account set-up in your organisation name
  • Store listing copy, screenshots and privacy answers
  • Pre-submission checklist and review responses
  • Staged rollout and hotfix planning
  • Post-release update routine

Need help with devices, email or accounts rather than a product? That is our IT support line, and it does not require choosing one of the routes above.

Service questions

Can you take over an app someone else started?

Often, yes. We first read the code and accounts to judge whether continuing is sensible, and tell you plainly if a partial rebuild would cost less.

Do you only work with London clients?

Our address is in London, but work is mainly done remotely, so location is rarely a constraint. Meetings are arranged within our hours.

How is pricing set?

After a conversation about scope, we propose a fixed stage or a time-based arrangement in writing. Nothing on this site, including the milestone selector, is a quote.

Will I own the result?

That is our default: code, designs, accounts and content in your name. Any exception would be agreed in writing beforehand.