On this page
No cloud desktop ships with every application humanity has compiled. Wonder maintains a large, curated software library so sessions stay stable, licensed, and safer than a free-for-all of random installers. That curation is a feature—and it means you will occasionally want something that is missing, outdated, or lacking a driver path.
This article explains the product philosophy behind requests and voting. For button-by-button instructions, use Wonder’s software inclusion tutorial; here we stay on why the system works the way it does.
Stability is a performance feature
Performance is not only FPS. It is also “the session did not rot because someone sideloaded malware yesterday.” A curated library lets Wonder test compatibility in the cloud environment, reason about licenses, and keep images maintainable across family, educational, and corporate modalities.
When thousands of users share a platform pattern, one broken codec can become everyone’s Monday. Requests create an intake valve; voting surfaces demand so engineering time follows real need.
Requests: making need visible
A software request is how individuals and admins say: this tool matters for homework, for CAD class, for the accounting close. Good requests include the product name, desired version, vendor context, and why alternatives in the library do not suffice. That quality helps reviewers distinguish a niche research binary from a widely useful office upgrade.
Drivers follow similar logic when peripherals must appear inside the remote session. Not every USB device has a clean remote story; requesting early beats discovering a blocker during an exam week.
Voting: collective prioritization
Voting exists because prioritization is zero-sum. Two hundred families needing a creative suite patch should outrank one quietly preferred utility—unless the utility is a hard dependency for an educational program, which is why narrative context in requests still matters. Voting is democracy with a safety review, not an automatic install pipeline.
Participate when you care. A library that only reflects the loudest installer-chasers will miss quieter classroom needs; a library with active educational and corporate voters stays balanced.
What “not yet” usually means
Pending items are often about licensing, security review, or compatibility testing—not indifference. Proprietary suites may need commercial arrangements. Open-source tools may need builds that behave in the Wonder session. Driver stacks may need validation with redirection features.
Wonder’s goal is a living catalog, not a frozen appliance. “Not yet” is an invitation to vote and to document the use case—not a dead end.
How this affects everyday performance
Having the right tool beats having a bloated session full of near-misses. Teams should standardize on library titles when possible, request gaps deliberately, and avoid turning each weak laptop into a private software museum. The remote desktop then spends CPU on real work—spreadsheets, editors, VoIP—rather than leftover trialware.
Parents and teachers can also reduce friction by checking the library before promising a class that “everyone will install X tonight.” If X is missing, start the request early instead of discovering the gap at homework time.
Soft next step
Browse what is already available before requesting duplicates. When something essential is missing, follow the official inclusion and voting tutorial to submit and champion it. The library grows because users treat it as a shared commons—especially across family, school, and business modalities that all depend on the same curated backbone.
A healthy Wonder Desktop experience is half remote compute and half a sensible catalog. Requests and votes are how the catalog stays alive without sacrificing the stability that makes Chrome-based sessions trustworthy.
Coordination across modalities
Family, educational, and corporate contracts often share the same library backbone. That means a classroom vote for a statistics package can help a small business team later, and a family request for a creative tool can inform educational demand. Cross-modality coordination is not automatic politics—it is a reminder to write clear use cases so reviewers understand impact beyond your household or team.
When drivers are involved, describe the hardware model, whether USB redirection is expected, and whether the device is required for graded work or optional convenience. Precise requests shorten review cycles more than urgent tone does.