My first Ajax Application was a success and a failure at the same time. I have detialed some of the points below, and hopefully I will be able to discuss them in later posts, this will give me more content in more readable bitesized chunks.
- It got me thinking Asynchronosly.
- It got me thinking about how the Yahoo! API works
- It got me thinking about how to take advantage of the Technorati API
- It got me thinking about all the other API"s that I want to see.
- It got me thinking about how I communicate over my blog
- It helped me publish related topics on Technorati
- It got me thinking about Perl again!.
- It got me thining about how I use Blogger.com
- It didn"t help me provide search facilities to related topics
- It didn"t help reduce bandwidth
- It looked absolutly terrible!!
- It didn"t work to quickly (but it did lead to success number 1, 2, 3, 4, 5 ..... :))
- It wasn"t visible to people other than myself what it actually achieved.
- It didn"t help anyone other than myself
- It genereated no feedback from anyone at all!
- It didn"t generate much in the way of extra traffic.
- It accomodated the lowest common denominator in web browsers, therefore it was not as client (as in browser) as I wanted.
With each of these points, I will guide any of the readers through my designs and desires for the next application. Hopefully, it can be used by other people as a guide of what to do and not to do.
I"ll discuss some basic requirements; show how my first idea was not really a good one and show how my next idea will be better.
I think one of the first things to do after this is to publish a "What I want" requirements document. If I have that I can think about how each of the requirements will effect the design of the Application.
If anyone has any points that they would like to yell at me. Email me: firstname.lastname@example.org
About Me: Paul Kinlan
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 web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.