Excitement and frustration of Google Maps announcements

Screenshot of Official Google Maps API Blog

Love My Maps? I love „your maps“ 😉 but besides the excitement of announcements, such as the one about adding editing functionality to the Google Maps API, which was made on the Official Google Maps API Blog this morning, some kind of frustration also comes along with it. Why? How many developers do you think are solving the same problems again and again? We have come to know Google as a company, which does not like to let people know too much about what’s next. Fair enough you may say – maybe you have to stick to these rules for surviving in a market, which is increasingly showing signs and giving rise to speculations about becoming disrupted or changing from a blue ocean to a red ocean or for the Google supertanker. I guess Google really has transformed into a supertanker in the last few years.

By the way, the addition of editing functionality to the Google Maps API was just one of several „new Google Maps things“ in the last week. We have now got a Google Map Flash API, new user functions and content to explore and discover the world around and far away 😉 or the new real estate options.

So why is there also frustration besides the excitement? While some people certainly like to „prototype-(p)re-invent“ wheels, others specifically DO NOT like to. Especially for smaller businesses, which use Google Maps or Google Maps Enterprise as a tool for making some kind of business idea work, it can be really frustrating to spend time and resources on developments that can literally often go in the bin a few weeks later – when the exact announcement that you were waiting for some weeks ago, is finally made.

For those, who even just intend to use Google Maps as a platform to realise their new mashup idea, planning ahead is extremely difficult. Do you want to spend a few weeks or months developing some fancy new feature, which is not available on Google Maps yet, or not exposed in the API just yet – and then find exactly that feature being added after you have engineered it yourself? If you are still working on it, you may save yourself some night shifts and this might bring at least some excitement besides the frustration that you have just wasted a lot of valuable time on inventing a wheel which is now given away to anyone for free! Or go and risk it – you may become famous in the visionary or technology enthusiasts departments and communities for a few days, and if you are quick and successful in crossing the chasm, you may become even more famous and rich – or you may end up at the bottom of the crevasse – with all the others that vanish in the awesomeness icefall.

I’ll give you an example: Google released a static maps API earlier this year. Then, a little later, Google added support for more marker options and paths on the static maps along with the message that lines can only contain 50 vertice points. Now if you need a hundred? Draw two lines? Should be an OK hack. If you need 1000 – hmm, how about building something yourself. Sophisticated server-side solution? Enough tools out there to do something like that… Or wait until Google decides that lines can be longer now? You decide! Good luck – and be sure to not be frustrated, but excited instead, if things keep changing… you know!

If you want a bit more planning, and you can afford to do without a substantial set of free geodata, then you may answer the question, „must it always be Google Maps?“ with a clear „no“! For example, follow the Open Layers Blog and you have a pretty good idea about what will be next – in fact, you can even contribute to make it happen faster!

Excitement and frustration are often very close together and timing is what may decide whether you will smile or get annoyed digesting your daily news. I’ll start my day going out for a run now – awesome nature is waiting for me!

Ein Gedanke zu „Excitement and frustration of Google Maps announcements

  1. Rob Coup

    You’re not paying for the Google Maps API or the geodata so it seems you’re still well ahead in the long-term equation.

    Lets say feature X costs $1K to develop. If it was your own mapping API or OpenLayers, it costs $1K as well. So if you need it now, you’re gonna have to spend the $1K regardless.

    Now feature Y which you need in 6 months would also cost $1K. But Google add it before you need it, so you save $1K. Bonus.

    And you start ahead with the geodata and the initial API development, so there’ll have to be a lot of „frustration“ to get back square again.

Schreibe einen Kommentar