Skip to content

HTML5 platform APIs for browser and mobile decisions

We build browser features for product teams, matching capabilities to the devices your users have. We own the support checks, permissions and fallback behavior that make each feature usable in its agreed scope.

01Overview

Browser APIs provide capabilities beyond HTML markup

HTML5 is familiar shorthand for browser capabilities beyond HTML markup. Media, canvas, storage, geolocation and worker APIs have separate specifications and support requirements. CSS controls presentation.

02Capabilities

Media, offline data and browser visualizations

We build each capability around its operating conditions on the target devices.

  • Media

    Playback and capture on target devices

    We build video and audio playback with codecs, adaptive streaming and autoplay policy in view. We check capture permissions and support for camera or microphone features, and define what users see on a poor connection.

  • Offline

    Data that remains useful without a signal

    We use service workers for offline caching and local databases for application data where supported. An offline data model for field and driver tools in logistics and transportation defines what is stored and how changes merge. We plan that as web development with explicit rules for conflicting edits.

  • Canvas

    Visualizations with readable equivalents

    We use canvas for charts, diagrams, maps and dense visualizations, with a text view of the same meaningful data. We define equivalent interaction where users need to act on it, using HTML for the readable structure.

03Fit

Choose browser or mobile delivery based on the capability

Check the required behavior on the target devices before choosing the implementation.

Seven browser capability decisions
The required capabilityWhat we recommend
Play video across desktop and mobile devices Test browser mediaCheck codec support, streaming behavior and autoplay rules on target browsers and connections. Playback and capture need their own support checks.
A tool for people working where the signal drops Offline web applicationDefine the cached experience, local data and merge rules before screens. Installability and offline behavior are separate requirements; test both on the target devices.
Bluetooth peripherals, background location, or NFC on a phone Browser/native fitCheck support and permissions for each required feature on the target devices. Prototype the interaction, then compare with iOS and Android for the required operating-system access.
An interactive view of a very large dataset Canvas with equivalentsProvide meaningful equivalent content and any required interaction through HTML, alongside the drawn view. Test how users access both representations.
Keep meaningful user data on the device Design storage and recoveryAccount for browser quotas and possible eviction. Decide which data needs a server record, how local changes synchronize and what happens before the connection returns.
Push notifications and reliable background work Test background supportCheck browser, operating-system and installation support for notifications and background sync. Confirm the required permissions and define a fallback for unsupported or deferred background work.
A product brief calls for an app Compare web and nativeStart with user tasks, devices and distribution requirements. Compare a mobile web experience with iOS and Android before choosing the framework or assuming a native build.

Scope

We own the paths for denied permissions, full storage and unavailable APIs, alongside feature support on the agreed devices. unicrew has been shipping browser software since 2012. Across the company, 100+ senior in-house engineers work in six countries. The work runs under an ISO 27001:2022 certified information-security management system. We connect these capabilities through JavaScript; front-end development covers ownership of the whole interface.

04Case studies

Mobile apps built on an existing web client

We contributed layout, theming and video streaming improvements to iOS and Android apps built on a building-security software company's existing web client. The project led to the release of production apps and a prototype showcasing new features.

See all case studies

05Stack

The layers around browser capabilities

Browser APIs work alongside markup, styles and JavaScript; native delivery is another implementation choice.

06Questions

Questions about browser capabilities and delivery

Use these answers to define support, data handling and implementation scope.

Browser APIs are interfaces that let code use browser capabilities, from media and canvas to storage and geolocation.

HTML defines document structure and semantics. HTML5 is familiar shorthand for the wider browser platform; these APIs come from separate specifications and their support varies.

We check each feature's conditions. Geolocation needs a secure context and user permission in supporting browsers. We define what happens when permission is denied or the feature is unavailable.

A progressive web app can replace a mobile app when its required capabilities work on your target devices.

We check hardware access, background behavior, operating-system integration and distribution needs. A browser/device matrix and a focused prototype guide the iOS and Android decision; delivery is scoped through mobile app development.

Use SVG for icons and labelled diagrams whose shapes need individual styling or interaction. Assess canvas when drawing volume is the main constraint.

SVG shapes are document elements. We test the actual scene on target devices; canvas needs meaningful equivalent content and interaction where required, designed alongside the visualization.

Yes, when the application is designed for offline operation.

Service workers can provide offline caching in secure contexts and supporting browsers. Local data still needs its own model, including storage limits, synchronization and the rules for conflicting edits.

We settle those rules before building screens and define what users see while data is waiting to synchronize.

We quote HTML5 work against the capability, target devices and support checks.

  • Time and materials is billed hourly and quoted per project for evolving requirements.
  • Fixed price is outcome based and quoted per project after the initial capability review.
  • Team extension is billed monthly per team member.

Most engagements start within two to four weeks.

Scope the feature around your users' devices

Share the capability and target devices, including what users need when offline or permission is denied. We assess the browser path and the relevant web development or mobile app development scope.

Book a scoping call

Thank you

Thanks for your message. We will get in touch with you shortly.