Optimized data collection fosters user validation but faces challenges in UI-driven applications
What is our primary use case?
We are working for a leading insurer in America. The purpose of the application is to validate whether the user is eligible for the insurance, including coverage details and underwriting screens.
Unqork is efficient in collecting information through various channels and APIs. It populates the data based on sign-in types, such as direct login or
SSO login, and then redirects users to underwriting screens. The system validates user eligibility and sends updates to another channel, like an
AWS system, which decides the user's eligibility or application processing status.
What is most valuable?
The integration of API components is valuable. We use a component called a plugin in
Unqork, which fetches data from any schema, whether external or internal. Recent updates allow direct data fetching from local databases, enhancing flexibility without needing microservices. Unqork optimizes the process of storing and fetching data through plugins, making it easy compared to other products and enhancing productivity.
What needs improvement?
Unqork is not efficient for building e-commerce sites where the user interface is more dominant than the data. While it handles backend functionalities well, user interface-focused applications like multiple complex dashboards face limitations. These areas need improvements in Unqork.
For how long have I used the solution?
I have been working with Unqork for almost two years now.
What was my experience with deployment of the solution?
The deployment process is straightforward with Unqork. From staging to QA, we have a service administration tool to visualize which modules need promotion. It is a matter of one click to deploy, making it efficient.
What do I think about the stability of the solution?
Unqork is stable. In our experience, there have been no major production issues due to Unqork in the 1.5 years it has been in production. While minor bugs occasionally occur, they are not significant, and the platform remains reliable.
What do I think about the scalability of the solution?
If considering scalable functionalities, Unqork rates eight out of ten. However, when managing exceptionally large data volumes, the architecture might require adjustments, making it about six and a half to seven out of ten.
How are customer service and support?
The interaction with Unqork's technical support lacks efficiency in terms of speedy responses. We generally communicate through a single point of contact linked to our client's license, and there is room for improvement in the promptness of addressing issues.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Unqork is the first no-code platform I am using. Though I am familiar with another platform called
OutSystems, Unqork is more efficient as it is a no-code platform, which eliminates the need for traditional coding.
How was the initial setup?
The initial setup can be challenging for those new to low code methods. Transitioning from traditional coding in Python or Java to a no-code platform like Unqork can be difficult initially but becomes easier once you understand the scenarios for use.
What about the implementation team?
Deployment can be handled by one person, however, the number of people required for maintenance depends on the application's scope. Two to three knowledgeable individuals are sufficient for managing maintenance.
What's my experience with pricing, setup cost, and licensing?
I am not certain about the annual licensing cost, but it is somewhat on the pricier side. It's justified if all features of Unqork are fully utilized.
Which other solutions did I evaluate?
As far as I know, my colleagues are using
OutSystems, but I find Unqork offers a more efficient way to build applications without needing to write any code.
What other advice do I have?
If you're leveraging all of Unqork's functionalities and features fully, the investment is worthwhile. My overall rating for Unqork is seven out of ten. Efficiency in using no-code features makes it a good fit when fully utilized.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Deployment process improves productivity but optimizations are needed in new features
What is our primary use case?
Our primary use case for
Unqork includes working on projects in various domains. First, it was with ONHS related to the oncology healthcare department. Second, it was with UBS in the financial domain. Third, it involved
Guardian Life, an insurance company based in America. Currently, we are working with Grayscale, a platform for digital coins investment like Bitcoin or
Ethereum.
What is most valuable?
The deployment process of
Unqork is highly valuable. The platform provides features such as grids to easily change the UI without writing extra code. Dynamic grids allow for changes without additional coding. The integration capabilities are also notable, with flexibility in using internal or external services for data storage. Unqork’s stability is commendable, with no bugs reported in the stable version. The DLC toolkit facilitates promoting projects with a single click, enhancing productivity.
What needs improvement?
There are areas in Unqork that need improvement. The ongoing development of the Vega feature, which is built on React compared to the older Century built on AngularJS, should be optimized. Vega promises faster experience, but it's still in progress. Additionally, there are limitations like showing a grid with a tree-like structure that Unqork currently cannot achieve.
For how long have I used the solution?
I have been working with Unqork for five years. Although I have a total of eight years in software development, the first three were focused on Node.js.
What do I think about the stability of the solution?
Unqork is very stable. With the Century version, I have not seen any bugs or instability in the last five years. However, users may encounter instability with the developing Vega feature as it is ongoing. Overall, I would rate the stability as ten out of ten.
What do I think about the scalability of the solution?
Unqork's scalability is good, and I would rate it as eight or nine out of ten. Its ease of use, minimal need for extra logic, and good integration capabilities make it significant.
How are customer service and support?
The technical support for Unqork is excellent, receiving a nine out of ten. I receive assurance that the team is addressing my issue within one to two hours, and I'll get a response within two working days.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Before Unqork, I worked with the MEAN stack, specifically Angular and Node.js. With Angular and Node.js, extra code was needed to manage data tables and deployment required setting up servers and using version control like
Git. In contrast, Unqork simplifies these processes.
How was the initial setup?
The initial setup of Unqork is straightforward, and I would rate it eight or nine out of ten. Mastering the DWPF and dynamic grids is essential, which simplifies much of the setup. The community is active and responsive, enhancing the overall setup experience.
What other advice do I have?
Unqork has some limitations, so ensure your requirements are assessable before deciding. For new developers, focusing on workflow and data workflow is essential. I rate the overall solution as seven out of ten.
Building workflows with security and ease but facing challenges in complex customization
What is our primary use case?
I work for an organization called Nuveen, an asset management company in financial services. We use
Unqork for building a lot of internal workflows, primarily small-scale one-to-two page applications for various uses in our client services, operations, and middle office. Most of the applications are primarily slackers, which means if somebody does something, it goes to a workflow, needs approval, and goes through. We use workflow and case management type applications, and this is what we've been using for the past two years.
What is most valuable?
From a capability point of view, there is very little infrastructure setup required compared to similar SaaS applications. I have built on
Salesforce power platform and have experience with other applications, and
Unqork is very comparable. Unqork offers two major advantages. It is a single-tenant application versus multi-tenant applications, which makes our security team more comfortable using it for processing confidential data. Additionally, the ease of use, especially in building form-type applications and workflows, is excellent.
What needs improvement?
The drag and drop functionality works well for basic form structures, but customization of complex layouts is challenging. If I have five to ten widgets on a screen and need to customize them, the work involved is substantial. Without proper guidance, one might create a clunky and difficult-to-use system from a developer's perspective. Simple page forms are fine, but more complex layouts could benefit from a layout manager or similar tool. As for architecture changes, Unqork moved from the Sanctuary to Vega platform without providing a migration tool, necessitating manual updates.
For how long have I used the solution?
I have been using Unqork since about 2022, so it has been roughly two years and a couple of months.
What was my experience with deployment of the solution?
The deployment process is straightforward. Although the initial setup took some effort, building applications and deploying changes is efficient. I have rarely encountered deployment issues, except for minor ones due to configuration errors or change control problems.
What do I think about the stability of the solution?
The platform has been reasonably stable, with availability issues only occurring twice due to underlying
AWS infrastructure problems. From the stability point of view, I would rate it a nine.
What do I think about the scalability of the solution?
I rate the scalability a seven. We increased the volumes, and over two years, I only encountered an issue once when there was some slow movement due to misconfigured elements.
How are customer service and support?
The support and service from Unqork have been very good. We have premium support as part of our organization's licensing, and I have almost never had an issue where I needed to escalate due to inadequate support.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I have built applications on
Salesforce power platform and have experience with other applications.
How was the initial setup?
The initial setup was a bit involved, but once we started building applications, the deployment process became straightforward.
What's my experience with pricing, setup cost, and licensing?
Unqork is expensive compared to other platforms we use, which are of different scales. Pricing is custom, depending on the type of organization. However, I would say the solution offers good value for money due to its capabilities.
What other advice do I have?
I would recommend Unqork but advise potential users to evaluate their needs carefully. It is ideal for building single-page applications that scale independently. However, it should not replace analytical tools. Identify the right use cases and utilize it effectively. Overall, I would rate Unqork a six due to the fact they haven’t yet built tools for architecture changes, requiring manual updates.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
No-code capabilities save time but learning resources and collaboration need improvement
What is our primary use case?
I use
Unqork as a no-code platform to create various types of websites based on user requirements. For example, I can use it for developing solutions for insurance, banking-related issues, transaction-related matters, and claim-related matters. This allows me to easily develop what I need without writing extensive code.
What is most valuable?
In
Unqork, I don't have to write long codes. The drag-and-drop feature allows me to create forms with components like text fields and email components easily. I can set up validation for email and phone numbers to ensure correctness. Additionally, Unqork allows direct API integration, whether internal or external, facilitating easier development compared to other technologies. It also promotes the use of module-based applications and workflow options, which aids in application scalability and stability.
What needs improvement?
Unqork needs to improve its learning resources because there aren't many available on platforms like YouTube or Google. Furthermore, troubleshooting is an area for improvement as errors should be visible directly in the code platform rather than just the web browser console. Collaboration needs enhancement since, currently, multiple developers cannot work simultaneously on the same functionality.
For how long have I used the solution?
I have been working with Unqork since last September.
What was my experience with deployment of the solution?
The initial setup with Unqork is straightforward. I need to create a workspace, and within that, create an application by defining its type, such as content-based or API-based. Depending on the selection, the corresponding UI options are provided, and it takes only two to three minutes for the setup.
What do I think about the stability of the solution?
The main issue I have with Unqork is the limited availability of learning resources. While other technologies have various resources available, Unqork mainly relies on its community hub and learning platforms.
How are customer service and support?
Unqork provides tech support and community support. I can raise tickets, and Unqork will respond and provide solutions accordingly.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I have worked with both
Mendix and Unqork. In comparison, Unqork is a no-code platform, while
Mendix allows coding by the user. Collaboration and functionalities differ significantly between both platforms.
How was the initial setup?
The initial setup is straightforward and involves creating a workspace where I create the application by specifying its type. If the application is module-based, specific details about what is to be done in that module are required. The entire setup hardly takes two to three minutes.
What was our ROI?
Time-saving is a substantial benefit, as I can develop applications with multiple functionalities in just a few days.
What's my experience with pricing, setup cost, and licensing?
I am not aware of the pricing, but I know that the certification cost is around $200, which is valid for one year.
What other advice do I have?
I would recommend Unqork because of its time-saving capabilities and ease of use. However, Unqork should enhance its collaboration features, as currently, only one developer can work on a functionality at a time. Unqork could work on improving this aspect. Overall, I rate Unqork a six out of ten.