Funding conditions also affect the resources available for software development. If funding is only provided for initial field testing, it is important to remember that further development funding will be required to bring the product to market. In addition, research projects are often under a certain cost pressure when applying for funding, which can lead to resources only being calculated up to an initial functional test. In some cases, this is sufficient from a research perspective, but it leaves a gap for continuation that should be considered.

For the development of new software and tools, research projects often collect data to test and calibrate the applications or to act as databases in the background. If this data is proprietary to individuals or companies, data protection agreements may only apply to the duration of a research project and not to the use of the data after a project has ended. This can prevent further use of the developed applications, or at least make it more difficult if new agreements have to be made. Therefore, it makes sense to think about and create usage as part of the project's data protection agreement.

In the context of a research project, new applications are often tailored and developed for a specific use case. From a research perspective, it can be very interesting to work out the developments as precisely as possible in order to gain detailed insights. However, the transferability and scalability of the applications, which are usually required for commercialization, can contradict this. This is because, among other things, the generalizability of data, expansion or location is required. A different approach is needed for this. The possibilities of transferability and scalability should be considered at the beginning of the project in order to remain flexible in the relevant areas.

Quality assurance plays a role in both research projects and commercial applications, but in different ways. While in the commercial sector there are standards and tools for what quality assurance should look like, in the research sector, it primarily concerns the quality of research results. One example is the quality assurance of input data: In a research project, data can be individually checked for quality. In a commercial application, a transferable or even automated routine must be established.

In research projects, digital applications are often operated and evaluated by the developers themselves, or by the people involved in the project, so that in some cases no user interface is developed. This is understandable in the research process, as it also requires a lot of resources. However, the development of a simple to complex user interface can be useful or even necessary, not only for commercial distribution but also for internal use. For a good user interface, however, the end users must also be involved in the development process.