Developers benefit from easy integration and UI development but face challenges with data manipulation and complex workflows
What is our primary use case?
I mostly work with Unqork to develop internal applications, and right now, I'm working with JPMorgan in a department called Asset Wealth Management. We try to automate processes that were previously done manually through emails, SharePoint, and Excel, which can be error-prone and time-consuming. We aim to serve internal employees rather than client-facing applications.
Only one application I have developed is client-facing, but the traffic for that application is very low.
What is most valuable?
With Unqork, you can develop user interfaces easily, and it's mostly beneficial for developers and firms rather than at the client level. The drag-and-drop feature makes it very easy and fast to develop, which drastically reduces costs compared to regular coding technologies that require database purchases and maintenance. With Unqork, everything comes in a package, so there's no need to worry about databases, provided your firm is okay with the security standards they follow.
Unqork makes data integration very easy, especially in how you make API calls and retrieve data from external APIs. They simplify the process to the point where even a business person can learn to integrate with other systems using the integration system in the administration tab. As a business person, I just need to use the applications and integrations already provided in Unqork.
What needs improvement?
The areas of Unqork that need improvement include the UI, as data-driven applications in banks require displaying data effectively on forms and dashboards. When working with JPMorgan, the data structures stored in APIs present challenges in retrieving and displaying data. It is tough to understand the data workflows in Unqork and manipulate them, especially for someone without experience. The functionality for data manipulation is not straightforward, and the transforms component requires additional coding, which complicates API responsiveness and impacts user experience due to latency issues.
For how long have I used the solution?
I have been using Unqork for nearly more than 1 1/2 years, with a break in between. Before this, I used it for 8 months, and now again, I am using the tool for around 6-7 months.
What do I think about the stability of the solution?
I would rate Unqork's stability as an 8, because whatever they promise is consistent and reliable until production. I do not see any instabilities regarding the features they promised.
What do I think about the scalability of the solution?
I rate Unqork's scalability as a 3 or 4; it is not highly scalable. For applications facing around 1 lakh customers, it's better to avoid using Unqork due to significant data latency issues and limited control over optimizations for API calls.
How are customer service and support?
I would rate the technical support for Unqork as a 9. We have a community where we can ask questions and usually receive support within 3-4 hours from other developers who can assist us.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I have worked with Core AI, another low-code platform, recently, about 3 months ago, alongside Unqork.
How was the initial setup?
I would rate my experience with the initial setup of Unqork as a 10, because it is a cloud-based application. You can directly access it via any browser by entering the URL and land in the development environment without needing to download or set anything up.
What other advice do I have?
Unqork is assisting with AI-driven projects for my customers through Gen AI developments, but to be frank, I have never used that technology with AI. They are developing it, but it's not fully complete or widely used yet. We typically use our in-house AI to integrate by making API calls and then sending and receiving data.
As of now, with Persistent, I had one customer for whom we developed two applications, but unfortunately, they are not using either due to performance issues. This dates back to around 2021.
Now, I'm working with JPMorgan, where we have multiple in-house applications that everyone is using because they are not complex applications. We're using Unqork for systems such as ticketing, but I am also working on a more complex application that is still in the development phase.
I rate the pricing for Unqork as a 7. They should consider making their pricing more flexible, particularly for small applications where customers may only want to test if it works before committing further. In those cases, they shouldn't charge as much as they do for standard applications.
For JPMorgan, we have the license for approximately 2-3 crores per year, but I am not 100% sure since I haven't been involved in enterprise meetings for first-hand information.
Overall, I would rate Unqork 6.5 to 7 out of 10.
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?
Other
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.
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?
Other
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.
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?
Other
Great UI and out-of-the-box integrations, but needs expanded cloud platform support
What is our primary use case?
Our primary use case for Unqork is to rapidly develop customer-facing web applications and portals to improve digital user experience and self-service capabilities. We operate in the insurance industry, which traditionally has lacked robust and convenient digital capabilities for customers and agents. With legacy software development approaches, it can take significant time and resources to design, code, test, and deploy new digital insurance applications and web portals.
Using Unqork's visual no-code platform, we can shorten these development cycles from months down to weeks. Our environment includes connecting with various legacy backends and core insurance systems running things like policy admin, claims, billing, etc. Integrating to these systems to build customer experiences on top has been challenging with traditional coding.
Unqork provides pre-built connectors to these systems that we can leverage right out of the box. For example, one of the first solutions we developed on Unqork was an agent portal that gives our insurance agents quick access to customer policies and claims status from any device. This also allows them to update records that sync back to the backend policy admin system. Building this with traditional coding would have taken over four months. With Unqork, we designed and tested the entire application in six weeks with an MVP. We are now able to use Unqork to rapidly design and iterate on new concepts for customers - like policy self-service portals, document upload flows, payment statuses, chatbots, and more.
Unqork's built-in AI capabilities also let us incorporate optical character recognition, chatbots, and other features faster than custom coding these. The flexibility of Unqork allows our business analysts and process designers to take concepts right from whiteboard to working software in days.
The reusable components and drag-drop interface accelerate what used to be months of requirements gathering and backend work before UI code could even start. By empowering more team members to own ideation and prototyping of solutions, Unqork unlocks our ability to translate digital ideas directly into customer-facing applications. We aim to improve NPS scores and retention rates and lower servicing costs through better self-service options.
Unqork is a strategic no-code solution enabling our ambitious digital experience roadmap.
How has it helped my organization?
Using Unqork's no-code platform has unlocked tremendous improvements across our organization - from product development velocity to breaking down silos between IT and business teams. Before Unqork, we struggled with slow release cycles for customer-facing solutions that met the pace of business demands. Our reliance on legacy coding and systems integrators created dependencies that caused bottlenecks. Requirement changes or enhancements would often add months to timelines, even for small features.
Unqork has transformed our ability to translate product ideas and business priorities into software at unprecedented speeds. What previously took four to six months of upfront planning, coding and testing now gets delivered in four to six weeks with Unqork's drag-and-drop development approach.
We are also seeing much higher adoption of completed solutions across business units because the no-code approach allows their direct participation in shaping requirements and designs. instead of just handing off specs to developers. Unqork's easy-to-understand visual models make it simple even for non-technical teams to provide input and make changes. Some key metrics reflecting Unqorks impact:
- Reduced time-to-market for new customer web portals by over 60%
- Lowered budgetary needs for simple web and mobile apps by over 40%
- Increased rate of requirements implementation from 53% to over 80%
- Increased business user participation in application builds from 17% to 89%
With faster and more aligned execution on digital solutions, our policy and claims processing volumes have seen 12% and 9% increases, respectively, from improved self-service options.
While adopting any new enterprise technology has challenges, we have not faced any major blockers from the Unqork platform itself. Their robust enterprise-grade architecture scales and secures our solutions without needing extensive backend coding. Instead of grappling with technical debt, we are now focused clearly on using Unqork to rapidly turn around innovative customer experiences.
Unqork delivers the speed, collaboration, and functionality we need as an agile insurance provider preparing for the next decade.
What is most valuable?
Of Unqork's wide range of no-code platform capabilities, the most valuable features for us have been its enterprise integrations, built-in AI engines, and advanced UI components.
The out-of-the-box enterprise integrations with systems like Salesforce, databases, ERP platforms etc. have been immense time-savers. Connecting Unqork frontends to core backend systems used to be a huge lift with traditional coding. Unqork removes this heavy lifting by providing pre-built connectors, APIs and data models for enterprise systems. For example, setting up a two-way sync between our claims management database and an Unqork portal took less than a day by simply pointing and clicking compared to weeks of effort previously.
The bi-directional capabilities ensure data updated in Unqork UIs can flow back to update source-of-truth systems. Unqork's integrated AI capabilities, like natural language processing, optical character recognition, and conversation bots, have also been game-changers.
We can incorporate document analysis and chatbots into portals without needing to code complex machine-learning pipelines and models. The no-code simplicity allows us to experiment with cutting-edge AI capabilities much faster. Advanced UI widgets like dynamic forms, Kanban boards, rich galleries, and even 3D model viewers have unlocked engaging self-service portal designs that previously required expensive custom development.
Unqork UI behaves consistently across devices and seamlessly adapts to various form factors. By leveraging out-of-the-box, AI, and UX features instead of reinventing the wheel, our teams can completely focus on business logic and process automation using Unqork. We estimate over 50% acceleration by relying on Unqork’s built-in capabilities versus traditional coding. The composability this provides is invaluable for interacting with legacy systems while delivering modern, competitive user experiences.
Unqork has been a force multiplier, making our technology team twice as productive while also bringing business teams directly into the creation process.
What needs improvement?
Given the rapid pace of innovation we’ve already seen from Unqork, there are a few major capability gaps we face currently. However, some areas of improvement and features we would benefit from in upcoming releases include:
1. Enhanced accessibility compliance - While meeting baseline standards, further WCAG conformance and widgets optimized for screen readers could expand access for disabled users of Unqork solutions. Added compliance certifications would also be welcomed.
2. Expanded cloud platform support - The addition of Azure and Google Cloud alongside AWS would allow our deployment options to better align with enterprise strategic cloud choices outside just Amazon.
3. More analytics and observability - Increased telemetry on app performance, component reuse rates, load testing etc. would help fine-tune Unqork solutions. More data and dashboard visibility into adoption would optimize our ROI.
4. Managing technical debt - As portfolios of Unqork apps grow over time, best practices and features to facilitate updating legacy components, refactoring old solutions, and preventing erosion will be helpful. Added controls to manage technical debt long-term.
5. Evolution of existing components - Existing rich widgets and connectors rounding out maturity with incremental capabilities would expand Unqork's versatility. Expanding the range of use cases served by current components.
6. Offline functionality - For mobile solutions, some limited persistent caching and offline usability during intermittent connectivity would better support field agents/inspectors. Tolerating offline states is key.
7. Design version control - Advancing visual version control capabilities for better design history, branching, merging, and reverting changes to Unqork sites would improve collaboration and prevent overwrite errors by nontechnical users.
For how long have I used the solution?
I've used the solution for one year.
