In general, the user interface I've created is incredibly simplified. I like this type of interface, but I'll admit it's not pretty or easy on the eyes. In the future somebody could expand upon the application to improve upon the UI's appearance and appeal to a wider audience of users. The skeleton and backbone of the application is in place, and minor UI tweaks would be easy for the design-inclined. Additionally, implementing a message reply system into the application would be fantastic, as there is currently no system in place and that is a feature of status net that goes unused here.
Unfortunately due to the unhelpful nature of the RSS2.0 feed tags used, there is no way to separate the author from the contents of the message. However, there is room to expand on how the information we do have is presented. Currently just the contents of the message (containing the author) is displayed, and the date the message was posted is available upon pushing the message. Somebody could expand this application to have the date and possibly a link to the message presented on the main page, along with the actual message contents. This would provide much more information at a glance.
The compose view, while functional, is less than ideal. Had I more time, I would've liked to implement a system in which your username and password were stored locally somehow, so that you wouldn't have to re-enter it for every message. Additionally, the interface here is lacking as well, as is typical for my interfaces. The text field/button combination is pretty boring, and I'd fault nobody for improving upon it. There is also room for more error checking, as the current implementation does not check the HTTP response to ensure that the post went through.