DWKit use cases
DWKit is a universal platform that allows you to implement a huge number of different business cases. We distinguish two types of cases: development and business.
Development cases describe different scenarios for using DWKit capabilities to build enterprise information systems. Business cases describe various solutions based on DWKit that were developed by us, our partners, or our clients.
Development cases
| Name | Legend |
|---|---|
| Application template | You need to build an application that solves a problem of business users |
| Back office | You need a back-office system |
| Backend for mobile-first companies | You develop a mobile app and need to build a backend |
| Upgrading a legacy application | You’ve decided to improve or upgrade an app that is used in your company |
| User interface for a non- IT project | You don’t develop the product and your users need an information system |
Business cases
| Name | Features |
|---|---|
| Human resource management | Employee records HR processes automation within a company Employee reports |
| Customer relationship management | Coming soon |
| Invoicing | Coming soon |
| Healthcare | Coming soon |
| Service desk | Coming soon |
| Task management | Coming soon |
| Case management | Coming soon |
Application Template
Legend: You need to build an application that solves the problem of business users.
DWKit is an ideal tool for the development of single-feature applications. It will empower your team to launch an MVP faster, and then iteratively add the required business functions.
Why DWKit?
- A ready-made app template
- In-built tools for faster development: Form Builder, Workflow Designer
- Faster time to market
- Predictable quality
What do I begin with?
Take a look at a simple example of a solution built with DWKit, and then download the sample's source-code from our website.
Alternatives:
- Find the most suitable SaaS and adjust your company's business processes to it
- Redevelop one of your existing systems
- Start development from scratch
Backoffice
Legend: You need a back-office system.
If your back office cannot handle the current flow of tasks and has errors, then it's time to automate its processes. The main thing here is not to break the already existing business processes. DWKit solves this problem by allowing you to install and adjust the system to your business needs easily and flawlessly. Use the Agile methodology to consider all the non-formalized processes. Make any changes easily with the in-built Form Builder and Workflow Designer.
Why DWKit?
- Fast and easy implementation
- 100% back office operations support
- Ability to create and change forms as easily as in a CMS system
- Installation on your company's servers
- Predictable quality
What do I begin with?
Take a look at a simple example of a solution built with DWKit, and then download the sample's source-code from our website.
Alternatives:
- Find the most suitable SaaS service and move your back office to it
- Implement an ERP system
Backend for mobile-first companies
Legend: You develop a mobile app and need to build a backend
Such companies often have problems with the development of a backend which is normal since they are focused on the development of their main product—the mobile application. DWKit is the optimal solution for these companies. It has a ready-made and easily adjusted web interface, and comes with an Integration API that is configured on the basis of the data model. Besides, the access to the source code allows for 100% vendor unlock and the possibility to customize the platform to make it suit your business needs.
Why DWKit?
- 100% vendor unlock and deep customization
- A ready-made web interface and fast web forms creation with Form Builder
- IntegrationAPI
- Installation on your company's servers
What do I begin with?
Take a look at a simple example of a solution built with DWKit, and then download the sample's source code from our website.
Alternatives:
- Extend your team and start development from scratch
Upgrading a legacy application
Legend: You've decided to improve or upgrade an app that is used in your company
You need to add a number of new features to your app but you face some fundamental difficulties. You search for possible alternatives, for example, to build a new version of the app.
Consider trying a smooth migration with DWKit. First, import your current database's structure to DWKit, and integrate your app with DWKit using Integration API. Now you can gradually move the functionality to DWKit, step by step, module after module. This approach is the safest for your business.
Why DWKit?
- Smooth data migration to DWKit
- A vast number of features for easier development (Form Builder, Workflow Designer)
- 100% vendor unlock (you can have access to the entire source code of the platform)
- Modern technology stack
- IntegrationAPI
What do I begin with?
Take a look at a simple example of a solution built with DWKit, and then download the sample's source code from our website.
Alternatives:
- Continue working on the development of a legacy system
- Start development from scratch
User Interface for a non-IT project
Legend: You don't develop the product and your users need an information system.
In the modern world, you can hardly find a project that doesn't require an information system. However, you may spend months and years on the development of the beta version, and then, in several years, you may realize that it is easier to rewrite it completely rather than to continue the development of new features. DWKit and the adoption of Agile or Scrum methodologies serve well for such kind of tasks. It will empower your business to see the results of all iterations at each specific moment.
Why DWKit?
- Quick Start
- Faster time-to-market
- Predictable quality
- Low level of technical debt due to formed architecture
What do I begin with?
Take a look at a simple example of a solution built with DWKit, and then download the sample's source code from our website.
Alternatives:
- Outsource system development to a third party
- Become an IT-company and develop the system using your own resources