One of the projects I've been working on for a while is a simple way to be able to publish podcasts online, without having to worry about downloading applications, or hand coding HTML or whatever. One of the main things that's been keeping me from finishing it, of course, has been lack of time. However, the other thing I noticed is that I was taking a completely wrong approach.
Before, the idea was that I would create a back end application, and then slap a UI on top of it. I realize now that for what I am trying to do, this is completely backwards, to a point. I realized that I am not creating a content management system as I have in the past, but rather a web application that serves a function. What I need to do then is work on the UI first, as this is what the user will see and interact with. It shouldn't matter what's on the back end, because the user will never interact with that.
I suppose I've been stuck in the other mindset due to having ideas of releasing stuff as open sourced projects. The mentality with that is to make the back end clean and understandable so that other developers could grab it and make it their own, which is not what the point of the podcast application is. That being said, I am officially re-announcing that I am working on a podcast application, taking what I've learned from my previous attempts and working on getting the user interface figured out first. Of course I benefit from having my podcast class already built that I can just plug in now without having to recode that part of it.
Of course one of the things I was toying with was to make it a desktop app built on Python and QT4, but that'll have to wait...
Ah, so many project ideas, so little time...
Post new comment