Mapbox vs. Zeplin

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

I still have some issues, especially with color integration between the style guide and also project. When we update the colors, it's not automatically sync to every project. Aside from that, zeplin solves my problem for hand-off design from design to developer. I set zeplin is source of truth design file

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

• Ease in automatically building design style guides, saving time that might be spent on building style guides in another tool (such as InDesign).
• Users can use Mac, PC, or web versions of this app to collaborate on a single project, enabling us to work with a wider pool of contractors.
• Accelerates the design-to-development workflow, as it’s very easy to import Sketch or Photoshop files through plug-ins, and HTML/CSS codes are automatically created based on designs.
• Provides cross-platform specifications for web, iOS, and Android, which can save developers time in figuring out specifications beyond the “main platform" on their own.

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

• The uploading and syncing of assets is great for sketch and photoshop but we use illustrator and that can be cumbersome/tedious at times.
• There are certain elements that have been a bit confusing to navigate at times, but for the most part, it's pretty user-friendly
• More integrations

Incentivized

Great tool

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

Zeplin's component management and style guide help us to be consistent across whole product and it so easy to use for non-technical person. It is now easy to collaboration for designes between different teams like stackholders, product owner, UI/UX, developers and testers. Now there is only one point of reference is Zeplin so it is so easy to get details without asking designer or developer again and again.

Incentivized

Zeplin has classic support with a chat from the website. It's working fine, and we're also getting the support needed when needed. However, Zeplin is very good at closing the incidents and moving on. It was a while ago we had a case with their support so that it might have improved since then.

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

Zeplin is great to inspect and share user interfaces, specifications and assets, perfect for developers. Tools like InVision and Marvel are much better to create prototypes for both developers, coworkers and even stakeholders, but they don't have this kind of feature (inspection) as Zeplin does. So each of them can be used for different purposes, offering different approaches to share and interact with layouts for apps and websites.

Incentivized

• 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

• Development time has reduced as the design updates are communicated in real time to developers and they don't have to write the boilerplate code as it's already generated.
• Employee engagement has improved as every stakeholder is aware about the design changes from the beginning and can give their inputs.
• Designers save a lot of time as they don't to explicitly communicate when the update or publish their designs and also it just takes a couple of clicks to publish their designs. Also, lot of rework is saved as every stakeholder is involved right from the beginning.

Incentivized