With lots of interesting client work on at the moment, I’ve decided to spend some evening time moving along the next version of Done by When. This is nothing too stressful, but the project is getting really interesting now. I think I’m over the initial conceptual learning curve and now I’m making proper progress.
Where the launch version of Done by When was primarily a working proof of concept, this next version is about attention to detail and responsiveness (that’s the speed of interactions as opposed to the adaptive layout stuff that’s already in place).
I feel like I’m properly upgrading something when I’m spending as much time removing code as I am writing it new.
More updates soon.
Following up my post about the backbone.js book I downloaded, I’ve been playing, testing and learning as much as I can. So much so that I’ve neglected my Coursera design course, though I think this is a better use of my time in the long run. This particular Coursera course was mainly to test out the MOOC process first-hand, and it’s pretty cool on the whole. I’ll still be taking part in the Game Theory course that’s coming up, and I’d give Coursera a big thumbs up overall.
I’ve studied design previously, so the content in the course (while very good) was mostly a re-hashing of old stuff for me, whereas delving into the world of Backbone.js and Single Page Applications has been a great way to challenge my existing approach to web design and development. It’s been a real brain stretch at times, but every new step in the learning process is rewarding, and you can never afford to stop learning if you work with the internet.
I’ve hacked about with Backbone enough now, that I’m starting to apply the learnings to Done by When, and though this equates to almost an entire re-write of the website front-end it’s going to make the app so much more responsive that I’m desperate to get it live. The demos I’ve put together already feel like so much more like software than web pages.
I’m not making any promises for a release date at this point as client work takes priority but I may be able to share something within a couple of weeks.
Also, though I’ve bailed on the Coursera course, I won’t give up on the menu planner, or my intentions to open source this.
I’ll keep you posted.
My most recent ‘pet project’, Done by When, grew up today.
It’s 3 months to the day since I announced a vague plan to test out an idea that had been floating around my head, and now it’s out of beta, taking payments and I’ve just notice our Mandrill email reputation has crept up to ‘Excellent’. Woohoo.
I’m delighted with where it’s going and all the helpful (positive and negative) feedback I’ve had from the first brave group of testers.
I’ve added some screenshots to my portfolio on Behance, but the interface has progressed even further since then.
Now that Done by When has a “business model” and all that, it will be given a serious amount of time and attention going forwards. But importantly, as it has an active user base I won’t be using it as a playground for new ideas and technology. It will first and foremost serve the needs of the users. Which means it’s no longer a ‘pet project’.
I needed another project/playground so I’ve enrolled (and completed my first week) in Design: Creation of Artifacts in Society with Coursera. I’ve studied design before, so mainly wanted to see what the Coursera experience was like in relation to the Open University courses I took a few years back. I’m more interested in the content of the Game Theory course, but that doesn’t start for a while yet, and all learning is good learning.
So I’ll be writing some posts about the Coursera experience, but more importantly I’ll use this as a framework for my next pet project. There are 7 weeks left to go and I’ve set myself the brief to somehow contribute to dealing with the issue of food waste.
Food is core. If we solve food, we solve most things.
Not that I’ll solve food, but I may contribute something.
I’ll keep you posted.
So, I just about scraped in inside my (second) deadline.
Done by When is live. Though very much in beta.
- Never go live on a Friday: Fail
- Ship early: Succeed
- Ship often: To be seen
In building this to-do list app I’ve learnt a few new things:
All of which I can highly recommend.
There’s loads more to do. It’s still un-branded for a start and the responsive stylesheets need tidying up, but the basic service offered if fully functional and I think it brings something new to the to-do list marketplace.
Please let me know what you think.