The Failures of my first AJAX Application: Part 3

This is the third installment of my Failures of my First AJAX application and it is titled "It looked absolutly terrible!!"

If you take a look at my application you will see that it looks diabolical. I realised about five minutes into my experimentation that I really need to improve my design skills. I thouhgt initially that it might have been the tools I was using, but as the old saying goes "A bad worker blames his tools".

I then realised that whilst I am quite good at programming, I sometimes lack the designers eye; that is to say I have a vision but not the skills to implement the final vision.

I can conceptualize the code easily and the implementation, it is just the UI that lets everything down.

The reason that this was the case is that the implementation of the software was highly dependant on the UI. The UI drove the application code. The next version of the software should be highly UI agnostic. The code that calls the web services, should not rely on the HTML elements, rather it should rely on the data structures present in the application. The UI should interrogate these data structures to determine what information to display.

In essence, the next version of the application should be tierd better. The UI and the Logic (Business Logic if you like) should be loosly coupled together. I should be able to change the Logic without affecting the page and likewise, I should be able to change the UI without having to alter the AJAX logic etc.

This would allow me to concerntrate my efforts on indiviudal parts of the application at any one time. So I can develope an AJAX framework, the business logic and the UI all independantly of each other.

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.

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