Read the technical brief → · PDF
1. What it does and why it matters
CloudWinks keeps the application catalogue and supplies the common screens, fields and navigation used across apps. A shared web and Android experience lets teams move between business activities without learning a different interface each time. Reusable definitions give developers a common foundation instead of rebuilding the same controls for every app.
2. How the apps work together
Crux supplies shared people and company records; KeyKook supplies sign-in and access services. Specialist apps such as Murphy, BigTalk and Roady bring their own business capabilities into the shared experience. Common interfaces keep the platform focused on the framework and each app focused on its own responsibility.
3. Using it for a separate business
The framework supports different businesses through application definitions, company context and configurable starting screens. An organization can focus on the apps relevant to its work rather than adopt every industry use case. CloudWinks provides the foundation for that chosen application experience.
4. Other choices and the CloudWinks fit
| Alternative | Its focus | CloudWinks product focus |
|---|---|---|
| Appsmith | Custom apps built with connected data and reusable screen components. | A shared definitions-led model across a family of business apps. |
| Retool | Data-connected apps built with components and code. | Common identity, navigation and business-app services in one framework. |
5. Building a competitive edge
Invest in reusable customer journeys: registration, app switching, saving work and returning to the same place. Measure the effort saved when introducing another app or business. A coherent experience and lower repeated configuration are the product’s central differentiators.
← More Foundation apps apps · All application briefs · How the framework works