Mathew Suen


Listcase began as an exercise in developing web applications. The intention was to make a simple to-do list which would allow users to make lists of items that could be checked off and later deleted. When the basic framework was finished, I started thinking: why not develop this into something people would actually use? With this in mind, I set about designing an interface that would be fluid and intuitive. We decided early in the design process that Listcase would have to update dynamically. There could not be any page refreshes which would break the user experience, and being a list manager, it would have to save automatically. There could not be instances where people would edit their lists and forget to save. Lists often follow a person’s train of thought and the intention was never to break that—superfluous computer functions are not usually part of someone’s thought process. Listcase would have to send and receive user input on-the-fly which introduced the need for AJAX, a web technology that allows web pages to load new data without intrusively reloading the entire page. The idea was to make this feel more like a native application than a website. A fluid user interface was necessary to make using Listcase as simple and intuitive as possible. Various touches were implemented to reduce the number of buttons, and standard visual cues such as cursor types were added to make functions such as in-place editing obvious to the user.