jessebushkar

Interesting situation. One point to make: CakePHP cannot cause browser compatibility issues. CakePHP is a backend framework and does not itself cause client side issues. I know this is splitting hairs, but a lot of things can contribute to client-side issues. If a design is in bad shape (ie. browser considerations were not made during planning), then CakePHP wouldn't be a relevant point for front-end issues.

That's all, carry on. I hope everyone's bickering and finger-pointing goes well on this fine Friday.

I've used pretty much all of the big geocoding services, and here are problems I've ran into.

1. Rate limiting: I get it, you have to make money and/or limit your freeloading, but rate limiting has killed things I've built in the past, especially Google's hard rate limit. A soft rate limit, or an alternate way to monetize, would be huge.

2. Accuracy: MapBox's geocoder is not good. Aside from inaccurate map tiles, their geocoder misses entire US zip codes. PLEASE at least include helpful error messages and a path to report incorrect results.

3. A solution for shared IPs and rate limiting. I have helped several small websites that do not come close to approaching Google's daily rate limit, but because their IP was used by someone else, they are not allowed to make geocoding calls. This forced us to use a different service.

Honorable mention: It would be nice to be able to specify what data I get back from a call. If all I need is lat/lng, I don't need another kilobyte of neighborhood/city/time zone info in my result.

Hope this helps.

Very cool, it's like the Leap Motion, a Multi touch track pad, and a keyboard had a baby. Looks perfect for kickstarter.

At first glance, it's pretty but distracting. I had a hard time deciding whether to focus on the video behind the words or the words themselves.