VNCuxf
VNCuxf is the User Experience Framework: the frontend layer that gives the suite one codebase for every operating system, every browser and every device.
Without a shared framework, every product builds its own web app, its own desktop wrapper and its own mobile app — three implementations per product, with three sets of bugs and three levels of polish. VNCuxf turns that into one: a product builds one application, and the framework delivers it as a browser app, an installed desktop application and a mobile app.
What it delivers
Section titled “What it delivers”- One codebase, many targets. Browser, desktop and mobile from the same product implementation.
- A consistent suite experience. Navigation, sign-in, notifications, appearance and the person layer behave the same way in every product, so a user learns the suite once.
- The same capabilities everywhere. Offline storage, notifications and deep links are framework services, so a product does not have to re-implement them per platform.
- Faster product delivery. A new product is built once and reaches all targets, rather than shipping later on some platforms.
- Maintainability. Fixing a behaviour once fixes it in every product and on every platform.
Main capabilities
Section titled “Main capabilities”| Capability | What it gives you |
|---|---|
| Cross-platform delivery | Web, desktop and mobile from one implementation. |
| Consistent shell | Shared navigation, appearance, notifications and account controls. |
| Person layer | The shared avatar, hover card, Action Wheel and person panel across products. |
| Offline capability | A local encrypted store and a replay model that products reuse. |
| Native integration | OS notifications, deep links, badges and mobile capabilities through the framework. |
| Design system | One visual language and component set, so products look and behave as one suite. |
Typical use
Section titled “Typical use”- A product team builds a feature once and it appears on web, desktop and mobile in the same release.
- A user installs a product as a desktop app and gets the same UI, with OS notifications and an unread badge.
- A mobile user works offline and the queued changes replay on reconnection, because the framework provides the store and the replay.
- A new product follows the suite’s design system, so it looks native in the workplace from day one.
How it fits the suite
Section titled “How it fits the suite”- VNCaxf provides the backend exchange; VNCuxf provides the user-facing framework.
- Every product is built on the framework and inherits the shared shell.
- VNClagoon AI surfaces the assistant consistently because the framework hosts it.
- VNCdirectory supplies identity to the shell.
| Role | What they do |
|---|---|
| Product team | Build on the framework rather than per platform. |
| Designer | Work in one design system for the whole suite. |
| Administrator | Distribute and update the applications. |
Related
Section titled “Related”- VNCaxf — the backend counterpart
- Getting around VNClagoon