Google has relaunched Cameyo, which it procured final year, to give a virtual‑app conveyance benefit that empowers bequest Windows applications to run on ChromeOS gadgets (or by means of the Chrome browser) without requiring a full Windows desktop environment.
The Verge
+2
TechCrunch
+2
With this relaunch (beneath the pennant “Cameyo by Google”), the benefit is more firmly coordinates with ChromeOS: Windows apps (for case, Exceed expectations, AutoCAD) can be gushed or conveyed as web‑apps or dynamic web apps, side‑by‑side with local ChromeOS/web apps.
The Verge
+2
Google Cloud
+2
The show is: associations keep utilizing the few Windows applications they still require, but move endpoints/devices toward ChromeOS, and streamline their IT stack (less reliance on Windows desktops/VMDs). Google casts this as bridging the “app gap” that has made endeavor appropriation of ChromeOS troublesome.
The Verge
+1
Why this matters
The challenge for ChromeOS adoption
For a long time, ChromeOS has been a compelling device/OS elective particularly in instruction, lightweight settings, and frequently in web‑based workflows. But one of the huge blockers to ventures exchanging from Windows (or indeed utilizing Chromebooks in sincere) has been bequest Windows applications: particular apparatuses (building, plan, desktop‑only apps) that essentially don’t run natively on ChromeOS.
Google distinguishes this as the “app gap” ‑ the idea that a few clients still require Windows‑only apps, and ventures must either keep Windows gadgets or keep up complex virtualization foundation.
The Verge
+1
The guarantee: lower fetched, less difficult administration, way better security
By conveying Windows apps by means of Cameyo’s Virtual App Conveyance (VAD) innovation, Google is advertising a few advantages:
You dodge having to virtualize whole desktops (VDI/DaaS) for each client fair to back one or two Windows apps. For case, with VAD you provide fair the app.
Google Cloud
+1
ChromeOS as of now has a security and administration profile that requests (programmed upgrades, sandboxing, “Chromebook”‑style straightforwardness). Blending that with bequest app get to makes ChromeOS more practical as a full venture endpoint.
Cameyo
+1
Cost efficiencies: In the integration declaration, the information proposed expansive diminishments in TCO (add up to fetched of proprietorship) when moving from virtual desktops to VAD + ChromeOS. For occasion, one source citing the combination claimed: 82% diminishment in equipment costs, 75% lessening in authorizing costs, 53% diminishment in operational costs, yielding by and large ~54% TCO diminishment vs conventional virtual desktops.
Cameyo
Flexibility: Clients can utilize ChromeOS gadgets and still get to the Windows apps they require; associations can receive a crossover endpoint environment (ChromeOS + bequest Windows apps) without being bolted into Windows desktops.
Strategic significance for Google
It reinforces Google’s endeavor esteem recommendation for ChromeOS. If undertakings accept they can keep their basic Windows apps whereas moving absent from Windows desktops, that makes ChromeOS essentially more compelling.
It possibly shifts future gadget obtaining absent from Windows‑based PCs toward Chromebooks or ChromeOS‑enabled endpoints, which are frequently lower fetched, easier to oversee. Google has an intrigued in developing ChromeOS share in enterprise.
It strengthens Google’s “cloud to begin with / web‑first” story: the move is less approximately desktops and more approximately applications being conveyed from anyplace, running in browsers or lean clients. This adjusts with broader industry patterns.
Google Cloud
+1
How the relaunch works & what is actually new
Virtual App Conveyance (VAD) with Cameyo
Cameyo’s innovation empowers applications (Windows, Linux, inner web apps, SaaS apps) to be conveyed through HTML5 browser, or as PWAs (Dynamic Web Apps), without introducing them locally on the gadget.
Cameyo
+1
With ChromeOS integration, the client encounter is consistent: the Windows app can show up as an symbol in the launcher/taskbar of a Chromebook; the nearby record framework and clipboard integration are backed (so clients double‑click records, or copy / paste between apps) as if the app were local.
9to5Google
+1
The backend can be in the cloud (open, private or half breed) or on‑premises; what things is that the gadget (ChromeOS endpoint) is lean and the app is streamed/virtualized.
TechCrunch
+1
Relaunch / Rebranding as “Cameyo by Google”
While the securing of Cameyo by Google was reported in June 2024.
TechCrunch
+1
The relaunch underscores more tightly integration, progressed client encounter, and situating for endeavors needing to “move to ChromeOS” whereas protecting Windows app get to. For case, Google’s web journal post: “ChromeOS + Cameyo: Reimagining Bequest Apps for the Present day Enterprise”.
Google Cloud
Why this is more than fair a “run Windows in a VM”
Traditional virtual desktops (VDI / DaaS) require running a full Windows OS picture, overseeing all apps interior that picture, and regularly include inactivity, client involvement issues, higher framework overhead.
Google Cloud
VAD’s approach is to stream as it were the application, not the whole desktop, lessening overhead, complexity and fetched. This makes relocation to a web‑first endpoint environment more practical.
Cameyo
Because Cameyo + ChromeOS integration underpins record framework, clipboard, PWA arrangement, etc, it makes the streaming/virtualized app see and carry on much more like a local app, lessening grinding for clients.
9to5Google
Use‑case scenario
An undertaking has numerous clients as of now on Windows tablets requiring get to to a blend of cutting edge SaaS apps additionally a modest bunch of bequest Windows desktop apps (for illustration designing plan devices or particular databases). The IT group would like to move to more effective endpoints (possibly Chromebooks or other low‑cost ChromeOS gadgets) and decrease Windows‑PC support, but the bequest apps anticipate them from doing so.
With Cameyo by Google:
The bequest Windows apps are virtualized by means of Cameyo and conveyed to clients on ChromeOS gadgets (or through browser) as if they were installed.
The client can open the app from the ChromeOS launcher, the app may open a record (from neighborhood client organizer) through ChromeOS record framework connector, utilize the clipboard etc, all seamlessly.
The IT group oversees one endpoint OS (ChromeOS), furthermore the app conveyance through Cameyo, without keeping up full Windows desktop pictures or VDI infrastructure.
Over time, clients move more and more workflows to web/SaaS, encourage contracting the dependence on Windows.
The association diminishes equipment taken a toll (Chromebooks regularly cheaper), licensing/maintenance fetched, foundation complexity.
Implications & Benefits
For IT groups and organisations
Reduced endpoint OS differences: Centering on ChromeOS rearranges administration compared to supporting Windows furthermore other OS variants.
Lower foundation & permitting fetched: As cited over, moving from full VDI to app‑delivery decreases TCO essentially.
Cameyo
+1
Better security pose: ChromeOS is architected to be more secure (sandboxed, programmed overhauls, less bequest stuff). When matched with Cameyo’s zero‑trust show and confinement of apps, the association may diminish assault surface, hazard of ransomware, etc.
Cameyo
Faster arrangement for apps: With VAD, conveying a Windows app may ended up less complex (or maybe than provisioning full desktops). A few case‑studies report much less difficult setup.
Google Cloud
+1
Flexible gadget demonstrate: Clients might possibly utilize ChromeOS gadgets (indeed cheaper ones) and still get to basic Windows apps, making revive cycles cheaper, and empowering more BYOD/hybrid endpoint strategies.
For end‑users
They get get to to both advanced web/SaaS apps and the bequest Windows apps they still require, all from one gadget (ChromeOS) with negligible disruption.
The involvement points to feel local: app symbols in launcher, bolster for double‑click records, cut/copy/paste, record framework get to. That decreases contact and alter resistance.
9to5Google
Potentially superior execution (since gushing as it were the app, not the full desktop) and less inactivity compared with farther desktop setups, in spite of the fact that this will depend intensely on network/hosting.
If the association revives to Chromebooks or ChromeOS endpoints, clients may get lighter, more battery‑efficient gadgets, easier client experience.
For ChromeOS / Google ecosystem
This move reinforces ChromeOS’s endeavor pitch: that it is competent not fair of web apps but moreover of bequest Windows apps.
It may quicken ChromeOS appropriation in divisions that have been moderate since of Windows app conditions (building, fabricating, plan, money related services).
It makes a difference Google position itself more emphatically in endpoint OS/enterprise IT showcase, possibly capturing share from Windows PCs or from full‑blown virtual desktops.
It adjusts with broader industry patterns: “cloud‑first”, move absent from conventional desktops, application conveyance as a benefit or maybe than OS‑centric.
Caveats, Dangers & Considerations
While promising, there are a few caveats associations ought to keep in mind:
Performance & client involvement: Gushing virtualized apps (particularly resource‑intensive ones like AutoCAD, 3D displaying, GPU‑heavy) may still cause idleness, organize reliance, and may not completely coordinate local execution in all cases. Undoubtedly, Cameyo underpins GPU‐accelerated workloads, but genuine execution will change.
Redmondmag
Dependency on internet/cloud foundation: With app conveyance models, arrange execution, information middle arrangement, idleness, transmission capacity matter. Associations in districts with weaker network may confront issues utilizing spilled apps reliably.
Licensing & fetched show changes: Whereas TCO is said to be diminished vs VDI, associations require to assess what the permitting costs are for Cameyo (or “Cameyo by Google”), how they coordinated with existing Windows permitting, how numerous users/devices. For illustration, in one 2023 article, authorizing gauges were given (in spite of the fact that these may not speak to the most recent Google‑integrated advertising) such as ~$264 per user/year for Cameyo full‑hosted.
Redmondmag
+1
Install base and biological system development: Indeed in spite of the fact that integration is live all inclusive concurring to the declaration, the real‑world development and bolster for all sorts of Windows bequest apps may change. A few unordinary or more seasoned apps may still carry on unexpectedly.
Change administration / client preparing: If clients are moved from Windows desktops to Chromebooks or ChromeOS gadgets, there still must be alter administration: indeed if the Windows apps are accessible, the rest of the workflow (how they open records, how they spare, how they associated) may contrast. Clients may stand up to change.
Device revive methodology: Exchanging to ChromeOS endpoints may require equipment revive. Associations require to assess lifecycle, compatibility with other peripherals, gadget administration tooling, etc.
Integration with other endeavor frameworks: Associations will need to guarantee that the ChromeOS + Cameyo environment coordinating with personality administration (e.g., Purplish blue Advertisement, Google Workspace), security instruments, endpoint administration, observing, compliance systems, and that bequest Windows apps stay compliant with those controls.
Vendor lock‑in / key chance: Whereas moving to ChromeOS + Cameyo might diminish dependence on Windows desktops, it may increment dependence on Google’s biological system. Associations ought to consider exit techniques, cross‑platform adaptability, and future sealing.
0 Comments