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.
I suggest improving the role-based area, particularly the token management. Instead of sending tokens via email, they could be forwarded to a client authentication number. Additionally, handling of conditions in coding areas could be enhanced by eliminating the need for coding when dealing with multiple conditions.
Unqork ( /products/unqork-reviews ) could benefit from allowing more flexibility in creating projects and extending them to other languages like JavaScript, Angular, or React. While I understand the limitations of SaaS, such an option would be useful.
I feel that the design and view aspects of Unqork could be improved. I need to add extra CSS to enhance its appearance. Offering pre-built CSS options to users would be beneficial. Additionally, the setup for API calls was initially challenging, especially when dealing with service logs and transforming large JSON codes for validation and PDF generation.
Although Unqork has made improvements in development view, I suggest focusing on data handling and integration performance, especially with higher data volumes. This includes making platforms smoother for high data volume handling. Another area I would like to see enhancements is regarding sophisticated development UI; more focus should be on performing optimally than having a sophisticated developer UI.
Tech Lead at a tech services company with 201-500 employees
Real User
Top 20
2025-04-24T08:18:20Z
Apr 24, 2025
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.
Senior Software Engineer at a retailer with 5,001-10,000 employees
Real User
Top 5
2025-04-02T14:32:53Z
Apr 2, 2025
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.
The timeout issue during server-side execution, specifically with loops, needs improvement. More features could be added to the data workflow, and there should also be enhancements in internal services, including updates and deletions.
The data workflow screen could be improved by increasing its size. Currently, the screen is small, making it difficult to work on larger data workflows since scrolling is required horizontally and vertically.
The area that needs improvement in Unqork is its performance. Proper configuration and effective coding practices are needed to enhance performance. Additionally, there are some limitations with the grid functionality, specifically the View grid and Dynamic grid. The View grid is efficient, whereas the Dynamic grid could be improved for better performance and functionality such as pagination.
Currently, Unqork has introduced the Vega compiler for better performance, alongside new components. It would be beneficial if they further improved compatibility with both the previous Sencha compiler and the new Vega compiler.
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.
Unqork is a no-code application platform tailored for businesses looking to build and manage complex applications without traditional coding. It simplifies app development, enhancing agility and reducing time to market.Unqork provides a visual development environment that allows businesses to innovate without relying on traditional IT resources, leading to faster deployment and reduced costs. Users can rapidly prototype solutions in a drag-and-drop interface, making it accessible for...
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.
I suggest improving the role-based area, particularly the token management. Instead of sending tokens via email, they could be forwarded to a client authentication number. Additionally, handling of conditions in coding areas could be enhanced by eliminating the need for coding when dealing with multiple conditions.
Unqork ( /products/unqork-reviews ) could benefit from allowing more flexibility in creating projects and extending them to other languages like JavaScript, Angular, or React. While I understand the limitations of SaaS, such an option would be useful.
I feel that the design and view aspects of Unqork could be improved. I need to add extra CSS to enhance its appearance. Offering pre-built CSS options to users would be beneficial. Additionally, the setup for API calls was initially challenging, especially when dealing with service logs and transforming large JSON codes for validation and PDF generation.
Although Unqork has made improvements in development view, I suggest focusing on data handling and integration performance, especially with higher data volumes. This includes making platforms smoother for high data volume handling. Another area I would like to see enhancements is regarding sophisticated development UI; more focus should be on performing optimally than having a sophisticated developer UI.
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.
I would like to see more detailed information on policies, as some are defined using technical language.
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.
The timeout issue during server-side execution, specifically with loops, needs improvement. More features could be added to the data workflow, and there should also be enhancements in internal services, including updates and deletions.
The data workflow screen could be improved by increasing its size. Currently, the screen is small, making it difficult to work on larger data workflows since scrolling is required horizontally and vertically.
The area that needs improvement in Unqork is its performance. Proper configuration and effective coding practices are needed to enhance performance. Additionally, there are some limitations with the grid functionality, specifically the View grid and Dynamic grid. The View grid is efficient, whereas the Dynamic grid could be improved for better performance and functionality such as pagination.
Currently, Unqork has introduced the Vega compiler for better performance, alongside new components. It would be beneficial if they further improved compatibility with both the previous Sencha compiler and the new Vega compiler.
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.