Commissioned Research
Top 10 Best Application Virtualization Software of 2026

GITNUXSOFTWARE REVIEW

Technology & Digital Media

Top 10 Best Application Virtualization Software of 2026

Market-research roundup comparing application virtualization software options for teams, including Cameyo and Citrix, plus ChromeOS app streaming.

20 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

Agents extract product evidence with provenance, then collect written reviews and transcribe video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Application virtualization software lets teams package application files and runtime state into isolated delivery units or sessions so legacy apps run without full endpoint installs. This comparison helps operators weigh packaging fidelity, streaming or remote delivery behavior, and enterprise controls like RBAC, policy, and audit logging across major deployment models.

Cameyo is the best pick for IT teams virtualizing internal Windows apps for browser-based access because its one-click capture turns Windows installers into portable browser-run packages, while Google Chrome Enterprise Core with ChromeOS App Streaming is the better fit for ChromeOS-first enterprises since it delivers streamed app sessions without traditional endpoint installs.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Cameyo

One-click Windows app capture that packages an application for browser execution

Best for: IT teams virtualizing internal Windows apps for browser-based access

3

Citrix Virtual Apps and Desktops

Editor pick

Citrix Workspace provides policy-driven access to published apps and VDI desktops with session controls

Best for: Enterprises deploying managed VDI and published apps with strict access controls

Comparison Table

1
CameyoBest overall
app packaging
9.5/10
Overall
2
8.9/10
Overall
3
8.7/10
Overall
4
general virtualization
8.5/10
Overall
5
application virtualization
8.0/10
Overall
6
application streaming
7.9/10
Overall
7
server-based virtualization
7.4/10
Overall
8
remote app protocol
7.2/10
Overall
9
enterprise suite
6.8/10
Overall
10
6.6/10
Overall
#1

Cameyo

app packaging

Captures applications into portable packages and streams them from the browser or client for rapid delivery without full installs.

9.5/10
Overall
Features9.5/10
Ease of Use9.5/10
Value9.5/10
Standout feature

One-click Windows app capture that packages an application for browser execution

Cameyo stands out for turning installed Windows apps into web-accessible apps with a browser launch experience. It supports packaging via its capture flow and includes an online viewer so users can run packaged apps without traditional installation.

The platform focuses on application virtualization and delivery for common internal use cases, including remote access to business software. It does not aim to replace every enterprise OS deployment and endpoint management workflow, so larger IT shops may still use separate tools for full lifecycle control.

Pros
  • +Converts Windows installers into browser-run app packages
  • +Simple capture workflow for building new application bundles
  • +Built-in app viewer reduces client-side installation requirements
Cons
  • –Best fit for Windows app delivery, not full cross-platform virtualization
  • –Enterprise governance features can feel limited versus dedicated virtualization suites
  • –Complex apps with drivers or services often need manual handling
Use scenarios
  • IT teams in mid-sized firms

    Package Windows apps for web launch

    Fewer installs per endpoint

  • Operations teams for internal tools

    Deliver business apps to remote users

    Remote access without packaging overhead

Show 1 more scenario
  • ISVs supporting internal app demos

    Share runnable app viewers securely

    Faster stakeholder testing

    Use the online viewer so stakeholders can run packaged apps without installing the original software.

Best for: IT teams virtualizing internal Windows apps for browser-based access

#2

Google Chrome Enterprise Core with ChromeOS App Streaming

cloud endpoint delivery

Uses ChromeOS app streaming and managed delivery with secure device and policy management to present browser-based and streamed apps to users.

8.9/10
Overall
Features8.9/10
Ease of Use8.9/10
Value8.9/10
Standout feature

ChromeOS App Streaming delivers application sessions to ChromeOS devices without traditional endpoint installation.

Chrome Enterprise Core with ChromeOS App Streaming lets organizations publish Windows or web apps to ChromeOS devices through cloud streaming instead of full local installation. It integrates with Google’s Admin console for device enrollment, user permissions, and application access policies.

ChromeOS App Streaming focuses on running apps in a managed streaming session while still using ChromeOS controls for security and updates. The approach fits fleets that standardize on ChromeOS and want app delivery without managing app binaries on endpoints.

Pros
  • +Centralized app access controls in the Chrome Admin console
  • +Cloud streaming delivers apps without local Windows app installs
  • +ChromeOS device management improves consistency across endpoint fleets
  • +Works well with existing Google identity and policy workflows
Cons
  • –Limited to workloads that support ChromeOS App Streaming
  • –Performance depends on network latency and available bandwidth
  • –Operational overhead for streaming infrastructure and monitoring
  • –Not ideal for offline use of streamed apps
Use scenarios
  • IT admins standardizing ChromeOS

    Stream Windows apps to ChromeOS

    No Windows app deployment on devices

  • Security teams managing access policies

    Control app access via Admin console

    Consistent app authorization

Show 1 more scenario
  • Helpdesk teams supporting diverse endpoints

    Reduce install troubleshooting on devices

    Less app setup support work

    Deliver apps through streaming so endpoints rely on ChromeOS controls rather than app binaries managed per device.

Best for: Enterprises standardizing on ChromeOS that need streamed app delivery

#3

Citrix Virtual Apps and Desktops

VDI and app delivery

Publishes and delivers virtual applications and desktops with strong application streaming and policy-based access controls for enterprise use.

8.7/10
Overall
Features8.7/10
Ease of Use8.6/10
Value8.8/10
Standout feature

Citrix Workspace provides policy-driven access to published apps and VDI desktops with session controls

Citrix Virtual Apps and Desktops focuses on delivering Windows apps and full desktops through centralized infrastructure with strong enterprise governance. It supports app and desktop virtualization via Citrix Virtual Apps, plus desktop virtualization through Citrix Virtual Desktops, using the Citrix Workspace experience.

The solution includes policy-based delivery controls, session management, and integration with identity systems for access to published resources. Advanced graphics, audio, and peripheral redirection target knowledge-worker workloads and VDI deployments at scale.

Pros
  • +Granular delivery policies for users, apps, and sessions
  • +Robust VDI and published-app capabilities in one platform
  • +Strong enterprise integration for identity, access, and management
Cons
  • –Setup and tuning require experienced virtualization and Windows admins
  • –Licensing and licensing tiers add budgeting complexity for smaller teams
  • –Troubleshooting can be time-consuming across image, network, and policy layers
Use scenarios
  • Enterprise IT standardization teams

    Provide managed Windows apps across devices

    Unified access to business apps

  • Contact center operations

    Host shared applications for agents

    Standardized workflows

Show 2 more scenarios
  • Platform engineers with mixed stacks

    Deliver Linux workloads alongside Windows

    Centralized access to supported Linux tools

    Publish selected Linux applications alongside other virtual app and desktop workloads.

  • Security and identity administrators

    Apply shared entitlements and session policies

    Consistent governance across resources

    Use shared entitlement, identity, and session policies across published applications and full desktops.

Best for: Enterprises deploying managed VDI and published apps with strict access controls

#4

QEMU

general virtualization

Emulates full hardware and supports virtualized execution environments that can be used to run application workloads in isolated instances.

8.5/10
Overall
Features8.5/10
Ease of Use8.5/10
Value8.5/10
Standout feature

Hardware-accelerated full-system virtualization with KVM integration

QEMU stands out by providing CPU virtualization through emulation, letting you run complete operating systems on different hardware architectures. It delivers full-system emulation for x86, ARM, and other targets, plus user-mode emulation for running binaries with less system overhead. QEMU supports virtual machines with standard devices like network interfaces, block devices, and graphics, and it pairs with KVM for hardware-accelerated performance on supported hosts.

Pros
  • +Full-system emulation across many CPU architectures
  • +Hardware acceleration via KVM boosts performance on supported hosts
  • +Flexible virtual device support for networking and storage
Cons
  • –Command-line heavy setup slows new users
  • –No built-in desktop-like app delivery workflow for end users
  • –Performance can drop when relying on pure emulation
Use scenarios
  • Infrastructure virtualization teams

    Run KVM-accelerated virtual machines

    Faster guest execution

  • Digital preservation teams

    Boot legacy systems with virtual media

    Repeatable legacy environment access

Show 2 more scenarios
  • Software developers and testers

    Test binaries across processor architectures

    Architecture coverage without extra hardware

    Run foreign-architecture operating systems or binaries to validate software behavior without physical target hardware.

  • Kernel and OS developers

    Reproduce system-level test configurations

    Reproducible validation environments

    Launch complete guest systems with controlled machine, firmware, storage, and network configurations.

Best for: Engineers needing cross-architecture VM testing and low-level virtualization

#5

ThinApp by VMware

application virtualization

Creates application virtualization packages that run independently from the OS by virtualizing application files and registry state.

8.0/10
Overall
Features8.0/10
Ease of Use8.0/10
Value8.0/10
Standout feature

ThinApp packaging with isolation of application files and registry using per-package rules

ThinApp stands out for delivering Windows application virtualization as portable packages that users launch like native apps. It captures applications into ThinApp packages that run without installing the full application on endpoints.

Pros
  • +Packages deliver apps without full installs on endpoints
  • +Granular isolation rules for files, registry, and settings
  • +Supports per-user and per-machine package behaviors
  • +Works well with locked-down OS images and VDI deployments
Cons
  • –Packaging requires careful setup, testing, and ongoing tuning
  • –Primarily focused on Windows app virtualization and compatibility
  • –License cost can be high for small rollouts
  • –Troubleshooting package behavior can be time-consuming
Use scenarios
  • Endpoint management teams

    Run captured Windows apps without installs

    Less endpoint software sprawl

  • Security-focused IT teams

    Isolate file and registry integration

    Tighter application isolation

Show 1 more scenario
  • Virtual desktop operations

    Standardize app behavior across PCs

    More predictable app operation

    Deliver ThinApp packages with consistent behavior across diverse PCs and locked-down OS images in broader VMware environments.

Best for: Enterprises standardizing Windows apps across VDI and hard OS images

#6

Microsoft App-V

application streaming

Virtualizes Windows applications into isolated delivery packages so apps can run without traditional installation on endpoints.

7.9/10
Overall
Features7.9/10
Ease of Use7.9/10
Value7.9/10
Standout feature

Streaming delivery with client-side virtualization for packaged Windows apps

Microsoft App-V focuses on streaming and virtualizing Windows applications so they run without traditional installation on the target machine. It packages apps into deployable virtual packages and uses policies to control file, registry, and shortcut integration.

Pros
  • +Centralized application packaging and policy-driven deployment
  • +Supports streaming and offline operation modes for virtual apps
  • +Integrates with enterprise management via PowerShell automation
Cons
  • –Windows-centric architecture limits cross-platform virtualization
  • –Requires careful sequencing for packaging, publishing, and client assignment
  • –App compatibility issues can appear due to virtualization boundaries
Use scenarios
  • Windows enterprise platform teams

    Stream apps without target installation

    Centralized app delivery

  • Identity and IT governance teams

    Control app behavior with policies

    Consistent user experience

Show 1 more scenario
  • Automation-focused IT teams

    Manage lifecycle with enterprise workflows

    Repeatable rollout processes

    Coordinate App-V package delivery with PowerShell-based automation and existing enterprise management patterns.

Best for: Enterprises virtualizing Windows desktop apps with centralized packaging control

#7

Microsoft Remote Desktop Services

server-based virtualization

Provides application and desktop virtualization by hosting apps on Windows Server and delivering sessions to endpoint devices through RDS technologies.

7.4/10
Overall
Features7.4/10
Ease of Use7.4/10
Value7.4/10
Standout feature

Remote Desktop Session Host enables multi-user Windows application hosting on shared servers

Microsoft Remote Desktop Services stands out by delivering full Windows session virtualization over the network, not isolated app containers. It supports Remote Desktop Session Host for multi-user server-based apps and Remote Desktop Virtualization Host for individual VM desktops.

Pros
  • +True Windows application compatibility via streamed sessions
  • +Supports session-based and VM-based desktop delivery models
  • +Centralized deployment and management with Windows Server tooling
  • +Strong security integration with Windows identities and policies
Cons
  • –Not designed for publishing single apps without full session delivery
  • –Initial setup and tuning require Windows and RDS expertise
  • –Performance depends heavily on network latency and bandwidth
  • –License and infrastructure planning adds complexity for smaller teams
Use scenarios
  • Windows enterprise platform teams

    Stream apps without target installation

    Centralized app delivery

  • Identity and IT governance teams

    Control app behavior with policies

    Consistent user experience

Show 1 more scenario
  • Automation-focused IT teams

    Manage lifecycle with enterprise workflows

    Repeatable rollout processes

    Coordinate App-V package delivery with PowerShell-based automation and existing enterprise management patterns.

Best for: Enterprises virtualizing Windows apps for secure, managed remote access

#8

NICE DCV

remote app protocol

Delivers high-performance remote display for hosted apps and desktop workloads using an efficient remote protocol suited for application virtualization scenarios.

7.2/10
Overall
Features7.2/10
Ease of Use7.1/10
Value7.3/10
Standout feature

Adaptive display streaming that tunes quality to network conditions while preserving low-latency control

NICE DCV delivers high-performance remote desktop sessions optimized for graphics and bandwidth efficiency. It supports virtual workstation and application delivery with adaptive streaming, low latency input, and flexible session policies.

Pros
  • +Adaptive streaming improves responsiveness on constrained networks
  • +GPU-friendly remote graphics supports workstation-grade applications
  • +Scales to many concurrent sessions with session management controls
  • +Strong integration with virtualization environments and cloud deployments
Cons
  • –Administration requires deeper infrastructure knowledge than simpler VDI tools
  • –Licensing and deployment costs can outweigh needs for light users
  • –Advanced tuning for best performance adds setup time
Use scenarios
  • GPU-backed engineering teams

    Provide low-latency interactive sessions

    More responsive remote use

  • Cloud and on-prem platform owners

    Scale remote access across environments

    Scalable remote desktops

Show 1 more scenario
  • Knowledge worker support teams

    Deliver graphics-intensive desktop sessions

    Better experience under bandwidth limits

    Use graphics and bandwidth efficiency features to support interactive knowledge-worker workloads over the network.

Best for: Organizations delivering GPU-intensive remote workstations to many concurrent users

#9

VMware Workspace ONE

enterprise suite

Delivers application virtualization-style app delivery through Workspace ONE UEM and integrates with VMware virtualization and secure access to manage and present apps at scale.

6.8/10
Overall
Features6.8/10
Ease of Use6.8/10
Value6.8/10
Standout feature

Workspace ONE Access conditional access for application entitlements and brokered session control

VMware Workspace ONE stands out by combining application virtualization delivery with unified endpoint management and identity-based access in one console. It supports delivery of virtual and SaaS apps through Workspace ONE Access, including conditional access and brokered remote app workflows.

Pros
  • +Unified access and app delivery with Workspace ONE Access and identity integration
  • +Strong policy-driven app entitlements and conditional access for managed users
  • +Deep VMware ecosystem alignment with Horizon for virtual desktops and apps
  • +Centralized catalog and configuration workflows for enterprise application publishing
Cons
  • –Complex configuration can require specialized identity and certificate setup
  • –App virtualization workflows depend on VMware infrastructure for best results
  • –UI flexibility can feel heavy for small environments with few apps
  • –Troubleshooting entitlement or broker issues may take time without deep logs
Use scenarios
  • Unified endpoint management admins

    Catalog and entitle virtual apps

    Centralized access control

  • Security operations teams

    Apply conditional access for app launches

    Policy-driven app access

Show 1 more scenario
  • VDI administrators

    Extend policies across Horizon delivery

    Consistent governance for VDI

    Integrate with VMware Horizon so desktop and app virtualization uses shared policies under one management umbrella.

Best for: Large enterprises virtualizing apps with identity-driven access and VMware integration

#10

SaaS-based Virtual Application Delivery with Kasm Workspaces

containerized workspaces

Runs browser-accessible application containers and workspaces with session isolation and controls for application virtualization at the edge.

6.6/10
Overall
Features6.6/10
Ease of Use6.7/10
Value6.5/10
Standout feature

Kasm streaming of containerized workspaces directly in the browser

Kasm Workspaces delivers application virtualization through browser-based access to containerized desktop and app sessions. Its core strength is secure workspace streaming with per-user session management, so applications run on the server while users interact locally.

Pros
  • +Browser-based access to containerized desktops and apps without client agents
  • +Session lifecycle controls for start, stop, and monitoring across users
  • +Strong security posture with server-side execution and access restrictions
Cons
  • –Container and infrastructure setup requires meaningful technical expertise
  • –Advanced workspace tuning can be time-consuming in complex environments
  • –Integrations and fine-grained policies may add administrative overhead
Use scenarios
  • IT admins for regulated teams

    Publish containerized apps via browser access

    Apps run without endpoint installs

  • Operations teams managing per-user sessions

    Control session lifecycle for users

    Predictable session handling

Show 2 more scenarios
  • Contact center and support managers

    Enable role-based application access

    Reduced access sprawl

    Configure authentication and role-based controls for who can start specific apps or desktops.

  • Platform operators handling media and clipboard

    Standardize audio and clipboard behavior

    More consistent user interactions

    Use operational controls to handle audio and clipboard behavior during streamed sessions for reliable delivery.

Best for: Organizations virtualizing secured browser-access apps for internal users and contractors

Conclusion

After evaluating 10 application virtualization software, Cameyo stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
Cameyo

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Application Virtualization Software

How do VMware Workspace ONE and Citrix Virtual Apps and Desktops differ in how users access virtual apps and desktops?
VMware Workspace ONE uses Workspace ONE Access to deliver virtual and SaaS apps with identity-driven entitlements and conditional access controls. Citrix Virtual Apps and Desktops publishes apps and desktops through the Citrix Workspace experience and enforces policy-based session and delivery controls for those published resources.
Which tool is best when you need full multi-user Windows app hosting from shared servers, not app containers?
Microsoft Remote Desktop Services is designed for session virtualization via Remote Desktop Session Host, which supports multi-user Windows application hosting on shared servers. If you want per-user VM desktops, it also includes Remote Desktop Virtualization Host for individual VM-based desktop sessions.
What option fits a ChromeOS fleet that must receive Windows or web apps without installing app binaries on endpoints?
Google Chrome Enterprise Core with ChromeOS App Streaming streams application sessions to ChromeOS devices under device enrollment and app access policies managed in the Admin console. This approach delivers an app experience without traditional endpoint installation of Windows app binaries.
When should teams choose ThinApp versus Microsoft App-V for Windows application virtualization?
ThinApp by VMware creates portable per-application packages with rule-based publishing and file and registry isolation, which helps standardize behavior across diverse PCs and locked-down OS images. Microsoft App-V focuses on streaming and packaging Windows apps into virtual packages with policies that control integration points like files, registry, and shortcuts.
Which solution is intended for GPU-intensive interactive remote sessions with low latency input?
NICE DCV is built for high-performance remote desktop sessions using adaptive streaming to match network conditions while keeping low-latency control responsive. It is also commonly used to deliver virtual workstations and applications where GPU-backed workloads need interactive graphics.
How does Kasm Workspaces enable browser-based application virtualization compared with VDI platforms?
Kasm Workspaces delivers application virtualization through browser access to containerized sessions, so applications run on the server while users interact locally in the browser. It supports publishing individual apps or full desktops and includes session lifecycle controls plus operational handling for audio and clipboard behavior.
What’s the practical difference between Cameyo’s capture-to-web workflow and ThinApp’s package isolation workflow?
Cameyo captures an installed Windows app into a packaged output through its capture flow and then exposes it via a browser-launch experience with an online viewer. ThinApp by VMware instead focuses on portable application packages with per-package rules that isolate application files and registry to maintain consistent behavior.
Which tool is most appropriate for identity-based access control and entitlement decisions at the application layer?
VMware Workspace ONE Access provides identity-driven entitlements and conditional access so administrators can govern access to delivered apps based on user and device posture. Citrix Virtual Apps and Desktops also integrates with identity systems, but Workspace ONE is specifically positioned around centralized cataloging, entitlement, and authentication controls in one console.
How does QEMU’s emulation use case differ from the virtualization products that stream apps and desktops?
QEMU provides CPU virtualization through emulation, which lets engineers run complete guest operating systems across different hardware architectures like x86 and ARM. In contrast, tools like NICE DCV and Kasm Workspaces focus on delivering interactive remote sessions or browser-based streaming of apps rather than cross-architecture machine emulation.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Application Virtualization Software

What separates application virtualization tools is how they handle packaging and delivery details without breaking apps, and how much control you get over rollout and troubleshooting. Focus on API and automation depth plus rollback discipline, because these decide whether changes stay predictable across users and sessions.

Package and runtime compatibility checks

Why it matters

This matters because application virtualization succeeds only when the packaged app behaves the same at startup, during file access, and at exit. If the tool’s packaging and delivery pipeline is picky, you’ll spend time chasing avoidable compatibility failures.

How to check

Ask for a demo workflow where they package a small line-of-business app and run it for different users. During the run, verify file and registry-like paths you choose are redirected or preserved as expected, and check how the tool reports launch failures with clear causes.

Automation and API for provisioning

Why it matters

This matters because automation determines whether you can connect application virtualization work to your existing admin processes and reduce manual steps. Strong API surface also helps with repeatable rollouts and controlled promotion across environments.

How to check

Request an API or automation walkthrough: show how they create/update a published app and assign it to a test group. Confirm there are endpoints or scripts you can run to check status, list deployed versions, and capture outputs.

Rollback and version control for packages

Why it matters

This matters because packaging changes are where regressions appear. Good rollback and version control let you revert quickly without rebuilding everything or leaving inconsistent user states.

How to check

In a demo, have them deploy one version, then replace it with a second version. Then ask them to roll back: observe whether versions are tracked, what gets reverted, and whether users stop seeing mixed behavior.

RBAC and audit visibility for admins

Why it matters

This matters because you’ll delegate packaging, publishing, and monitoring tasks. RBAC plus audit log visibility shows who changed what and when, which is essential when application behavior shifts after updates.

How to check

Ask how they structure roles for packagers vs operators. In the admin console or API, confirm there’s an audit trail for publishing and assignment changes, and show how you can restrict access to view or modify those actions.

Throughput during delivery updates

Why it matters

This matters because update waves often fail due to slow delivery or timeouts rather than incorrect packaging. Measuring update throughput and stability tells you whether rollouts stay orderly under real usage.

How to check

Ask the demo team to simulate a modest rollout to multiple users, then update the packaged app during active sessions. Watch how many sessions get delayed, what status the system shows during the update, and whether failures are reported per user or per host.

Red flags

  • Rollback reverts inconsistently or leaves mixed app versions for users
  • API automation only supports basic actions while key steps require clicks
  • Audit logs don’t clearly record who changed publishing or assignments

Fit by situation

  • If you manage frequent app updates with tight change windows, prioritize rollback and version control for packages.
  • If your team needs repeatable releases across groups via scripts, prioritize automation and API for provisioning.
  • If multiple admins handle packaging, publishing, and monitoring, prioritize RBAC and audit visibility for admins.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.