Web and mobile applications

What it is

Public-facing and internal applications that people use directly — on a phone on a worksite, or on a desktop in an office.

Accessibility and performance are treated as delivery requirements rather than as a later remediation exercise, because retrofitting either into a finished interface costs several times what building it in does.

Typical requirements we are asked about

• A public service or customer-facing application that has to meet WCAG 2.2 AA
• A mobile application for staff working away from a desk, often with poor connectivity
• An existing site that is slow, unusable on a phone, or failing accessibility audit
• A web platform that has to integrate with systems the organisation already runs

What Astri Devs delivers

• Interfaces built against WCAG 2.2 AA, tested with a keyboard and with automated checks in the build
• Responsive layouts verified across the range of real device widths, not only at desktop size
• Server-rendered or statically generated pages where that is the faster and simpler answer
• Native or cross-platform mobile applications, chosen on the requirement rather than on preference
• Offline and poor-connectivity behaviour where the work actually happens away from a signal

Typical outputs

• A deployed application with its build and release pipeline
• An accessibility test record covering automated and manual checks
• Performance measurements against Core Web Vitals
• Content and administration tooling where the organisation needs to make its own changes

Engagement approach

Fixed-scope delivery with a design and prototype phase first, so the interface is agreed before build effort is committed. Accessibility acceptance criteria are written into the specification.