The Failures of my First AJAX application: Part 6

This is the 6th instalment of the failures of my first AJAX application and it is subtitled "It didn’t help anyone other than myself".

To be brutally honest, when I had this idea for the AJAXTagger I think I thought I would solve my problems with tagging my posts and also everyone else's problems.

The idea is a simple one: to provide the user with tags that Technorati can pick up without the user having to manually handcraft each tag; additionally each tag would be auto picked based on the context of the journal entry.

There were some other features I wanted in the app based around related searches, citations but they had to get pulled.

As I was creating this as my first ever AJAX, XMLHttpRequest application I knew that it wouldn’t be great, but I still had delusions of grandeur.

In the end the only person it helped was me. Looking back, this is absolutely fine by me. It helped me not get bogged down by all the extra leg work to make my blog a little more special. It helped me enjoy Blogging.

So….. [I am trying to think why it was a failure, when in actual fact it was a very good learning experience].

I think the next version of the application will be more focused around what I need, but with an eye on what extra value it might provide other users. If it adds extra value to my readers then that is all that matters.

Keep watching.

If you have any features that you would like to see, email me or post a comment.

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!)