DevExpress Universal vs. Mapbox

When you want to display spreadsheet based reports, it's really convenient as it has everything out of the box.

If you have very basic components like combo boxes or lists, there is hardly a point in using such a large component set.

In the end, it's a matter of finding a good balance between functionality and complexity.

Incentivized

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

• Handle large and complex datasets using its table widget (DataGrid)
• Handle large and complex hierarchical datasets using its tree table widget (TreeList)
• Customize widget to fulfill advanced requirements such as adding a complex grid inside a grid cell

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

• Documentation could be improved
• Better examples of code in languages other than C
• Better wizards for building applications

Incentivized

• 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

DevExpress Universal controls are much simpler to use, implement and customized as compared to Kendo. Learning curve for telerik is high, though level of customization that can be achieved with telerik exceeds that of DevExpress Universal. Found DevExpress Universal community support to be better then its competitors. License cost is also a wining bar here.

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

• It is good for asp.net application and it takes less time in development which we used two years back.
• We have stopped with these tools when clients were asking applications to be built in angular or react. We have switched to Kendo.

• 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