Mapbox vs. Webix UI

For services that require maps and basic geo-functionality in production, Mapbox is one of the greatest choices out there. They're free, provide much more refined/modern productions compared to Google maps, and have very good support on different platforms. For services that require higher-computation products, like matrix routing, optimization, etc..., the prices can get quite high very quickly, and you should consider moving those services to an on-premise server at that point.

Incentivized

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

• Documentation is clean, easy to read, and very well organized which makes it easy to get going or learn something new
• The online user interface makes it quick and easy to edit maps, upload new datasets, view analytics, or get API keys
• Great integrations with Tableau and easy to develop for Android, iOS, or Web

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.

• The product is not always that easy to use, aimed at professionals understanding colors and palettes etc.
• Being a full cloud product it can be complicated working with the interface when your connectivity is not great.
• Tutorials and samples could be more visual and could cover more ideas on how to use Mapbox.

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

One feature that made me go in favor of Mapbox was its stellar documentation. Google Maps and Bing Maps are the other alternatives I considered, but the learning curve with both of them is steeper than it is with Mapbox. Also, Mapbox Studio gives newbies a very simple, clean and easy to use environment to make and store maps online

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.

• Mapbox is the only service that has all the products we need to release our product to the market. Without Mapbox, we would've spent far more time integrating multiple different map/geo services like Mapbox and HERE maps together.
• Mapbox was sometimes expensive in the testing period, and we would've definitely moved some of the services on-premise to save money if we had the time.
• Mapbox has functionality for traffic-aware routing in many countries, as well as matrix-structured routing data, which is what enables our service to function. Having all of this integrated within an API allows us to easily scale our service to multiple different cities/countries in a matter of days.

Incentivized

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