![]() ![]() Without it, I certainly would not have spent the last year of my life working on this software. So, thank you for your continued support. I love that I get to make something that people actually use. have to happen.Īnd then of course the cycle starts all over again. That's also the phase in which translations, website updates, marketing etc. Once beaTunes is feature complete (that's where we are right now), there comes the phase when I hope that many people try the EA version (please do!!), so that both little kinks and gigantic bugs are discovered before the final release. Discovering these issues and fixing them is a huge part of my daily routine. It's pretty neat that it introduced better support for classical music tags, but for some reason Apple chose to change the meaning of existing ID3 tags and introduce others that nobody else is using. Those produce a lot of work, because they break things. That's when I burn the most for my work.Ībove I mentioned outside factors. So after all the tedious nitty-gritty work is done, I get to spend a little bit of time getting my hands real dirty. But finding new ways to improve detection accuracy is among the best parts of the job. Of course creating a neat UI, solving scalability issues, and working with lots of open source libraries is fun, too. Like creating a new key or tempo detection algorithm. ![]() One thing that's probably most fun about beaTunes, is that every now and then I get to do some real research. Some survive, many don't.įeatures I want, are often of a different breed. So deciding which user features to implement is a process of elimination. Every additional feature clutters the UI and makes beaTunes harder to play with. As it is, beaTunes is already a fairly complex software. But even very reasonable wishes need to have many potential users. Obviously, it does not make sense to implement those very specific wishes in beaTunes itself-that's what beaTlets are for. And sometimes they are very specific and only interesting for a small audience. Sometimes they solve problems for many people and provide me with valuable insights into what people really need. I typically aim for a good mixture of what users want, what I want, and what simply needs to happen, because the world didn't stop spinning. Assuming you already have a product, you need to figure out what your next version needs. Let me digress and talk a little about what goes into creating a software like beaTunes as a one-man-show. Something I want to enjoy crafting-and hopefully people enjoy using. But I'm glad that I'm able to say: Writing beaTunes is not something that's primarily concerned with deadlines. Like in any good software project, this should have happened earlier. I'm very happy to write that today I can finally release the first Early Access (EA) version for beaTunes 5.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |