There is a lot of room for improvement in Temenos Quantum. Temenos Quantum is not quite stable yet. Improvements can be made to make Temenos Quantum stable. Improvements are needed in the solution, considering how my company needs to raise a lot of tickets with the technical support team of Temenos for some basic issues every time.

There are some features in Temenos Quantum that I want to be stabilized by Temenos, just like in Android Studio and Xcode. Building an application using Temenos Quantum is not difficult, but my company needs to seek some support for the solution all the time.

It operates as a closed-loop system, meaning not every user or developer can freely access all of its products and features. In the realm of development, there are often challenges with the out-of-the-box applications that could benefit from significant improvement. When a bank acquires a new platform, there may be issues that need to be addressed before deployment. Rectifying these issues would represent a substantial leap forward for them. One particular feature that I've personally had to develop from scratch within Temenos is QR payments. Currently, Temenos does not natively support these features. It would be highly beneficial if future iterations of Temenos could incorporate support for QR-based payment methods, as it would enhance the platform's capabilities and align it more closely with modern payment trends.

Using the API manager can be complicated when you're dealing with multiple teams, projects, and APIs. Quantum doesn't have user-based access, so I can't restrict parts of the project to specific users. 

The user community isn't that great, and Temenos support is a little slow. You need a lot of coding knowledge to operate it. You need to know mobile application programming and Java. 

The UI lacks flexibility, especially regarding customizations.

There are numerous issues at the fabric end, and working with the visualizer is extremely challenging. Basic development tasks require a high-end machine, and even clicking on an icon initiates a thirty-second processing time. The challenges mainly revolve around fabric and content.

We have encountered several challenges with Visualizer and it would be beneficial to improve it. When developing our application, we also encountered certain issues related to delays and time-consuming builds.

There are many issues when integrating with native sides when building an Android application of the retail accelerator or an iOS application of the retail actuator. We have to incorporate on the native side of things, which creates a lot of issues. Temenos Quantum is a proprietary product and not open source. There is not much information available on the internet for developers to reference when solving issues. You have to contact the help desk, who will then give you an appointment and work to resolve the issue. In terms of what Temenos can do better, they can make the product more mature so that we do not encounter as many black holes when encountering an issue.

In my experience, one area where Temenos Quantum could improve is in the flexibility of widgets and additional libraries. While Temenos provides a set of widgets for development, they may not meet all requirements, and crafting custom widgets or libraries can be quite a challenge. Unlike some other platforms, Temenos Quantum doesn't readily offer extra libraries, meaning developers like me have to write our own code to create the specific widgets we need. This can be a time-consuming and complex process.

Temenos Quantum needs to improve its usability. It lacks information on the network. We have to contact the support when we are stuck with something. 

The security and the interface technology could be better in Temenos Quantum. Additionally, a module that can display all the activities that have been done in the system would be helpful.

There is definitely room for improvement, especially in the areas of AI, AR, and DR for mobile and web applications. While it has made a start in these areas, it needs to make these technologies more affordable and keep up with the fast-paced IT sector. It is essential to stay current with the industry's rapid changes.

This is an expensive solution, and it is the biggest challenge that we face when we present this platform to customers. They love it, but when they start asking us about the price, the questions are about the bare minimum requirements.

It restricts them based on the number of users that the mobile app is going to have. For example, 10K users will accept my mobile app, or 20K, 30K, 100K, etc. One of the problems is that in this world, estimating the number of users is tough. You don't know how many you are going to have in advance of it going live and public.

I think that the licensing should be changed to a more relaxed model for enterprise customers so that they are not worried about the number of users. They should just have a fixed price. This kind of flexibility might give more revenue to Kony and its partners, as well.

In terms of additional features, I would like to see more widgets and more flexibility in the widgets. Perhaps we can develop widgets of our own and the usability is just there. We would like to have widgets for graphs and analytics, as well as the integration of machine learning. If I can integrate machine learning to my mobile app, out of the box, then that would be great. AI capabilities are something that I would like to have in the platform. Right now, it's just a raw platform to develop apps. 

The technology of the solution needs an update. It is deficient in terms of connectivity.

The product needs more native features.

Some features are only enabled for paid users. It would be much better if they enabled those features without having to pay.

I would also like to see them publish information about future technologies on the Home screen under a separate tab. That would be an improvement.