# The problem in plain terms Many enterprises have at least one application that refuses to retire. It solves an indispensable business need, depends on obscure integrations, and runs on code that few people fully understand. Its interface may be decades old, but business users still need it. Replacing those apps can be costly, risky, or constrained by regulation. Yet keeping them as-is creates security exposure, productivity drag, and technical debt — and can force employees onto legacy device architectures.
# How much of the workplace is already browser-ready Forrester's 2026 Digital Workplace and Employee Technology Survey found that 50% of employees say they can do most of their work in a web browser. "Most" matters: a few locally dependent Windows apps can keep whole teams tied to traditional endpoints and the operational burden that comes with them.
# A practical bridge: virtual app delivery (VAD) Virtual app delivery delivers individual Windows or Linux applications through a browser or as progressive web apps rather than streaming a full desktop. Google integrated Cameyo into ChromeOS and Chrome Enterprise after acquiring Cameyo in 2024. The approach creates an abstraction layer between the legacy application and the endpoint so organizations can:
- Apply centralized security and access controls without exposing applications directly to the internet.
- Move toward longer-term replacement, refactor, or retirement strategies without slowing overall workplace modernization.
# Real-world example: Humana's migration path
# Operational benefits beyond device flexibility When legacy apps run across thousands of endpoints, problems can look like device, OS, driver, or patch issues. Centralized delivery reduces that noise. IT can maintain a consistent runtime, apply patches and controls centrally, and limit the surface area exposed to helpdesk tickets and endpoint-specific failures.
# How to fit VAD into a broader modernization program Adopt VAD as a tactical layer while continuing strategic application modernization. The process looks like this:
- 1Identify the small set of locally dependent apps that block device or cloud migration.
- 2Wrap those apps with a VAD solution and publish them through enterprise controls.
- 3Continue parallel efforts to replace, refactor, or retire each legacy app on a prioritized roadmap.
# Bottom line