What is our primary use case?
I use Temenos Quantum mainly for building hybrid mobile apps, and it is fantastic for creating user interfaces. Thanks to its Visual Aid feature, I can design forms without struggling with complicated code. I simply use a visual interface with drag-and-drop options, which gives me better control over how my app looks. And if I need to write code, it's a breeze with JavaScript ES6, and I don't have to bother with extra frameworks. What's even better is that tasks like Duo Integration are a lot simpler compared to other platforms, saving me time and effort in app development. It is a user-friendly tool that helps me build apps efficiently.
What is most valuable?
The best thing about Temenos Quantum is how it smoothly connects with Temenos Fabric. This simplifies our quantum application by handling identity, authentication, and security tasks seamlessly, saving us from extra coding. It's like an enterprise service hub, letting us use different APIs within the fabric easily. This simplification makes it easier to link our front-end app with the middleware and connect to various endpoints while keeping everything secure.
What needs improvement?
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.
For how long have I used the solution?
I have been using Temenos Quantum for nine years.
What do I think about the stability of the solution?
Temenos has become much more stable over time. I have used Temenos from version 3.5 up to version 9, and I noticed a significant improvement in stability. In the earlier versions, like 6.5, I encountered many errors that needed various fixes when building Jira or the APK. With Temenos Quantum 9.x, it has become much more stable and reliable for my work.
What do I think about the scalability of the solution?
Temenos is scalable, especially when compared to some other frameworks like Flutter or React. It generally offers good scalability and performance. However, if a page becomes too complex or has a lot of resources, it can lead to slower loading times. It is essential to aim for simplicity in mobile apps. If complexity is introduced, it might impact the performance, and that's something I have noticed while working with Temenos Quantum. Approximately 100 people use the solution at our company.
How are customer service and support?
In terms of production support, the response time is generally faster and more efficient. However, for staging deployment or non-production stages, the response time can be slower, often taking two to three days, which requires some patience. I would rate the support a seven out of ten.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Before adopting Temenos Quantum, the company initially used Ionic for mobile app development. However, they eventually transitioned from Ionic to Temenos Quantum because Ionic's technical support was bad.
How was the initial setup?
The initial setup was fairly simple. We just needed to do two things: install Java (version 8) and set up the Android SDK for building Android apps.
What's my experience with pricing, setup cost, and licensing?
It is on the expensive side and the price is determined based on usage.
What other advice do I have?
I would definitely recommend Temenos to others. The main reason is that it allows for screen design development with minimal to no coding required, making it user-friendly for creating app interfaces. It is very useful for banking and it is a good product. Overall, I would rate it an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud