RESOLV

Build · Digital Products

Web & mobile apps

Native-quality apps for iOS, Android and the web, engineered for low bandwidth, older devices and accessibility.

The challenge

For many institutions the app is now the front door. A citizen renews a licence, a student checks a timetable, a patient books an appointment, and every one of those journeys is judged on a phone, often on a congested network or an older handset.

Apps built for the ideal device and connection fail the people who most rely on public and financial services. Slow load times, inaccessible controls and fragile offline behaviour translate directly into call-centre volume, complaints and exclusion.

We design and build web and mobile applications that are fast on modest hardware, usable with assistive technology, secure by default and maintainable by a single codebase where that is the right trade-off.

Our method

How the work is done.

  1. 01

    Journey and device research

    Map priority user journeys and the real device, browser and network profile of your users to set performance and compatibility budgets.

  2. 02

    Platform choice

    Decide between native, cross-platform and progressive web approaches against your budgets, team skills and release constraints, recorded as a decision record.

  3. 03

    Design system and build

    Accessible components built once and reused, with test-first development and continuous integration on every change.

  4. 04

    Device and accessibility testing

    Testing on a matrix of real and emulated devices, screen readers and throttled networks, alongside mobile security testing.

  5. 05

    Store release and monitoring

    App store submission, phased rollout, crash reporting and performance monitoring from the first release.

Deliverables

What you receive.

  • iOS, Android and/or web application source code with build pipelines
  • Reusable, accessible component library and design tokens
  • Device and browser support matrix with performance budgets
  • Mobile security test report aligned to OWASP MASVS
  • WCAG 2.2 accessibility conformance report
  • App store listings, release process and signing key management guidance
  • Crash and performance monitoring dashboards

Engagement options

Ways to buy it.

  1. 01

    App audit

    Review of an existing app covering performance, accessibility, security and code quality, with a prioritised improvement plan.

    3–5 weeks
  2. 02

    New app build

    Design and delivery of a new application from discovery to store release.

    4–9 months
  3. 03

    Ongoing release team

    A standing team that ships improvements and keeps pace with operating system and store policy changes.

    Rolling, quarterly

Standards

Frameworks we work to.

  • OWASP MASVS
  • OWASP MASTG
  • WCAG 2.2
  • Core Web Vitals
  • Apple and Google platform guidelines

Questions

What buyers ask us.

Should we build native or cross-platform?

It depends on device features, performance needs and the skills of the team that will maintain it. We assess these explicitly and record the reasoning rather than defaulting to one approach.

Can the app work offline?

Yes, where the journey allows it. We design local storage, synchronisation and conflict handling deliberately, and we encrypt data held on the device.

How do you make apps accessible?

Accessibility is built into the component library and tested continuously with automated tools and manual screen-reader checks, rather than audited once at the end.

Do you handle app store submission?

Yes. We manage submission and review, but the store accounts and signing keys remain under your organisation's control.

Discuss web & mobile apps.

A senior engineer reviews every enquiry and replies within one business day.