Future / ecosystem
What we’re working on
This section explains where Virex is going next without pretending those lanes are already fully live. The direction should feel ambitious and clear, while still remaining honest about what is planned, what is already part of the core direction, and what still belongs later.
Where the product is going
Future lanes should read like clear product direction, not a wall of equal boxes
Each lane here is part of a broader ecosystem direction. Some are already part of the core support story, some are planned next, and some are ecosystem layers that expand what users can do around the repo they already own.
Mobile Apps
Mobile app generation is part of the main product direction. Virex supports mobile where relevant today and is continuing to improve Expo-ready output, navigation quality, mobile UX, setup clarity, and continuation toward release preparation.
Status: Core direction. Coming next: More polish, stronger setup guidance, and clearer mobile continuation without treating mobile like a side lane.
Virex Games
Virex Games is planned as a future expansion lane starting with lightweight mobile game foundations such as arcade, puzzle, runner, and other casual formats, with a longer path toward deeper game structures over time.
Status: Planned lane. Coming next: A first lane around lighter game foundations before more advanced game systems are considered.
Marketplace
A public Virex Marketplace is planned for reusable foundations, packs, assets, premium extras, and official Virex add-ons. Over time, creators should also be able to sell their own Virex-compatible products there.
Status: Planned lane. Coming next: Reusable internal packs first, then creator-facing ecosystem growth later.
Community Center
The Community Center is intended as the builder-facing social layer where users can ask questions, show what they are building, learn from others, and discover examples from across the ecosystem.
Status: Planned lane. Coming next: A clearer builder destination for examples, discussion, and progress sharing.
Private Builder Network
Virex is moving toward a more connected builder environment with better examples, clearer updates, more visible internal activity, and a stronger feeling that products, packs, and builder knowledge all live inside one ecosystem.
Status: Ecosystem direction. Coming next: More visible internal activity, stronger examples, and a more complete connected product environment.
Optional convenience
Future hosting is meant as a convenience layer, not lock-in
Virex may later offer its own hosting or deployment convenience layer for people who want a faster path from repo to live product. That convenience is not meant to replace repo ownership or force the product into closed hosting.
The philosophy should stay simple
Own your repo, self-host if you want, and leave with your work if you want. Optional Virex hosting later is there to reduce friction for builders who care about speed and convenience, not to create dependency or lock-in.
How to think about it
Optional convenience should make the product easier, not less free. The core direction is still repo ownership, portability, and self-hosting freedom when that is what the builder wants.