Kosmera Shell: a consistent experience for employees, less repeated work for teams
Applications built on the Shell share common screens and components, so employees find the same patterns across them. Teams that need their own frontend can build standalone instead.
In many organizations, each internal application ships its own settings screens, its own user profile, and its own tables and forms. Employees relearn each one, and developers rebuild the same screens again.
Kosmera Shell provides those common parts once for Kosmera applications. Application teams focus on the screens specific to their business process.
What this means for your organization
A more consistent employee experience
Applications built on the Shell share settings, profile, organization switching, and common components.
Less repeated work
Teams do not rebuild common screens and data grids for each new application.
Flexibility where needed
Teams with their own frontend stack can build standalone applications on the same platform services.
What the Shell provides
Included with the Shell
- Settings screens
- User profile
- Organization switching
- Ready-made grids and components
What your teams still build
- The screens and components specific to the application
- The business logic behind them
For architects: three layers of UI
Each layer builds on the one below it. Teams choose how far up the stack they go.
3. App-specific components
Your teamThe screens and components unique to your application, built by your team, with or without AI tools.
2. Kosmera Shell
RecommendedSettings screens, user profile, organization switching, and ready-made grids and components, shared across applications built on the Shell. The Shell is developed as a shared product, with new versions released over time.
1. Kosmera JavaScript library
FoundationData access, current-user details, and platform notifications. Used by Kosmera applications with or without the Shell.
Standalone apps: Shell recommended, never forced
Some teams have an existing frontend stack, or an application that needs its own look and structure. Kosmera supports that directly.
Any framework
Build in React, Angular, or another framework, using only the Kosmera JavaScript library.
Same platform services
Standalone apps use the library for data access, current-user details, and notifications.
Same delivery
Standalone and Shell apps are published and served by the platform in the same way.
The trade-off
Standalone applications do not automatically share the Shell's screens or user experience. The team building a standalone app is responsible for its settings, profile, and other common screens, and for keeping its look consistent with other applications where that matters.
Kosmera uses the same Shell
Kosmera Space ships with its own administration application, Space Admin. It is built on the same Shell that customers use for their own applications.
The result
Employees get familiar screens across applications built on the Shell. Developers stop rebuilding the same common screens. Teams with their own frontend stack can keep it, accepting responsibility for their own common screens.
Shared screens where they help, a standalone option where it is needed.