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.
What is rapid application development? Rapid application development (RAD) is an agile software development approach that was created to replace the “Waterfall” method.
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.