Pusher vs. Webix UI

As I told you earlier, if you just want to send regular push notifications to the app users, then Pusher shall not be your first choice. However, if you wish to make the app a little more interactive by making live changes in the app using Pusher and sending your user's real-time notifications, then you should definitely try it.

If you need to create an interactive data report, optimize a workflow, handle hierarchical data or make calculations in a powerful spreadsheet, you will find a proper widget for your needs in the Webix UI library. If we want to display data in various forms Webix UI layouts and widget help to organize a web page and define its overall look-and-feel.

Incentivized

• Pusher allows live changes in the UI using push requests. We can also integrate it with the PHP source code.
• They offer 99.99% uptime, so we can trust on their services.
• Pusher works well along with the Flutter codebase, so we do not have to modify it much to work on cross-platforms.

Incentivized

• The Kanban Control allowed to implement a compelling task management system with little effort.
• The Chart Control made it easy to create our dashboard and it was a lot easier than using D3js as we did before. D3 allows a lot more flexibility but it takes often 10 times longer to get a chart done than using Webix.
• Support at Webix is very helpful and responsive.

• Not a good support system.
• Poor documentation.
• Date transmission encryption issues.

Incentivized

• None at the moment

Webix UI is a cross-browser, cross-device JavaScript framework which makes it easy to build a complex Web UI. Most features work as expected. While working with large datasets, you can load data dynamically to reduce complexity and improve performance. It provides a set of integration extensions that allow you to add third-party tools into an application.

Incentivized

React was too time consuming. Kendo was another good one, but more expensive and seemed less responsive. [Sencha's] demo didn't seem to justify the price.

• We had over ten thousand customer orders go through over the course of a year with no problems with this API
• There was very minimal support for this API which allowed us to focus on other priorities.

Incentivized

• It saved us 1000s of USD for just using the Kanban Board instead of developing it from scratch.