The Failures of my First AJAX application: Part 7

This is the 7th instalment of the failures of my first AJAX application and more commonly know was "It generated no feedback from anyone at all!"

As in my previous post, when I was creating the application I had grand ideas about the people who might use this application. I had visions of thousands and thousands of people using it and having to ring up Yahoo to ask to have my 5000 daily query limit increased.

In actual fact, I was really the only person who used the application. Even though I was posting about it in my journal I didn’t receive any feedback at all from the public.

This got me thinking. Even though the application is primarily for my benefit I would dearly love other people to use it. I would also need to get people talking about it. I would also need all the information to be available in one place (regarding the AJAXTagger).

My first step to more exposure is this Blog. All my content will still be aggregated on, but this blog is designed to deliver all the information about the development and use of the application in one simple place.

My next step after this will be to promote it. I need people to start talking about it; I need people to investigate the functionality it offers; I need you to use it, break it and criticise it!

Do you have any ideas how I might do this? Email me or leave a comment. I need the feedback to make this application better for me and for you. Every comment and suggestion will be taken on board.

I lead the Chrome Developer Relations team at Google.

We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.

Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.

I love to learn about what you are building, and how I can help with Chrome or Web development in general, so if you want to chat with me directly, please feel free to book a consultation.

I'm trialing a newsletter, you can subscribe below (thank you!)