Mapbox vs. Swiftify

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

It is recommended to use Swiftify in any situation that requires iOS development because even if you develop just in Swift or just in Objective-C, it could be helpful for researching and investigating purposes. Additionally, if you need to convert big quantities of code from Objective-C to Swift, this tool will optimise that work. It will not translate a whole class of 2000 lines perfectly, but after converting it you can review the code and modify the lines that have not been properly converted, making you save more than the 50% of the time in that case. I've not been able to test it properly as I only used the trial version and it is really limited.

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

• Helps to prevent redoing the whole code.
• Sometimes it is hard to find the exact command of Obj-C in swift.
• It helped me to learn more :)

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

• Sometimes the conversion doesn't make much sense. The Swift conversion doesn't compile, or is not optimized.

Incentivized

It is a good tool to use. We can perform various customisations; I always end up exploring and finding a new feature that can be used in my work somewhere. And one good thing is that is actually quite reasonable in terms of cost, with the free tier being quite adequate

Incentivized

I don't have any problems with the platform. I like that their email responses are fast.

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

There's not much to compare - we haven't found any proprietary like it. Existing OpenSource solutions are unmaintained and Swiftify supports the latest versions of Swift.

• 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

• For now the impact has been small, considering that I used the trial version, it was helpful for small conversions. Summarising: Saving time on researching process

Incentivized