No special Valentines Day image here folks–we need to simplify.
Duh, I know it’s best to start with feature A, and forget B, C, and D. But I’m a feature junkie and I suck at staying simple. I always blurt out “If we can do A and B, then why not add C and D too? ” After all, it’s just software.
But alas, I need to re-learn the simplicity rule to make Assetbar a better experience for users.
In his first review of Assetbar, Marshall Kirkpatrick over at RWW says:
As for the RSS reader, it’s cool in its formative stages. Scalability, sharing, time sensitive metadata, super simple reviews and off-site integration with my feed reader are all part of my “dream come true feed reader” vision.
Hey, that’s great! I was really hoping that a professional feed junkie like Marshall would appreciate the features.
BUT, we need an “a major UI overhaul”. Or more damningly: “I’m not about to use Assetbar in its current state but the concepts here are fascinating.”
The thing is, I actually agree with Marshall. I agree 100%.
In fact, Louis Gray has been rooting for a UI overhaul since we first showed it to him, and last night I let him know that we are starting on that.
The surprise in our pre-relase isn’t our over-complicated-by-Israel UI, it’s that our SQL free, single stack architecture and scaling design is working like a champ. Despite a few niggles, it’s outperforming my best expectations. We’re adding 10’s of thousands of assets every few hours, all personally searchable and with an unprecedented amount of metadata on each. All on surprisingly few servers. Go DBfilesytems!
So the bottom line is that we are really excited to improve Assetbar UI so it’s simpler and easier. And kill all the JS cruft that makes rendering slow. Our team can make that happen, if I get out the way and don’t screw it up.
Thanks for the critiques, folks–we have our marching orders.
And I still have lots to learn.