3 ms·
Its annoying to me that they basically are just copying the interface that google maps SDK has. I would have hoped for something more declarative and easier to
by jnmandal 8y ago
Its annoying to me that they basically are just copying the interface that google maps SDK has. I would have hoped for something more declarative and easier to use from a framework like react/vue/elm etc.
- petetnt 8y agoExactly. Google Maps is already painful to use with modern workflows. I can see how the similar API can be helpful for those who just want to switch to Apple Maps.
- deleted 8y ago[deleted]
- giancarlostoro 8y agoHave you trie Bing maps sdk? We wound up ditching it and using leaflet to render the imagery from Bing instead. It was the worst.
- danpalmer 8y agoThey actually modelled it on the Swift/Objective-C MapKit interface. (They mentioned this in the WWDC session)
- outside1234 8y agoWhich doesn’t make any sense - this is for the web - not a native app
- dawnerd 8y agoSure it does. Likely the same developers would be implementing it on the web so makes sense to keep the api the same.
- bgorman 8y agoWhile it may be easier that way for the developers, it makes sense to make the API more idiotmatic for the target platform/SDK.
- bobwaycott 8y agoThe worst thing you can do when designing an API is to make that API different on the various platforms you support. Edit: That’s not to say you shouldn’t strive for the most natural and easy interface for devs to use, but even if you’re not there yet, keep things consistent on all platforms.