“Dude. Where the heck is MYStuff 2.0? You said, like, months ago that you were working on it.”
While not a literal email from any of the current MYStuff users, it’s a paraphrase of a number of emails as of late. So I thought I’d take a few minutes and give everyone an update.
As I stated over a year ago, MYStuff 2 is a ground-up rewrite that I started in September. It’s more than just re-writing all the existing features and making them better. I’m adding tons of new features, too. From the database backend to the user interface to all the new stuff, MYStuff 2 has been a major undertaking, and some of the features have proven to be quite ambitious. Further, all this new code has to be tested and debugged as well, and since it’s a ground-up rewrite all the program code is new. (Well, not all of it. I was able to re-purpose about 10% of the existing codebase.)
Half of me is jumping up and down with excitement about the new version and is screaming in my left ear, “It’s close enough! Wrap it up! Ship it now! Ship it now!” while the other half of me is screaming in the right ear, “It’s not done! Make sure it’s polished! Don’t cut out any features! Give the users a good value! Make it seamless!”
So I’ve been left with a decision: strip out planned features and release “soon” and dribble out the missing features as I finish them, or stick with the intended feature set for 2.0 and ship “soon-ish”.
After much hand-wringing, I’ve decided to go with the latter option.
And I’ll give you an example of one of the features that’s been slowing me down: barcode scanning.
I’ve had people asking for it since MYStuff 1.0 was in beta. Unfortunately, it’s not a trivial feature to implement. There are other programs out there that have it, but few have pulled it off successfully. I have a little test program running that scans barcodes just fine and dandy, but it’s problematic: It generates false readings about 20% of the time, and that’s assuming you have the lighting good enough to get it to recognize the barcode at all. If the lighting is good and you have everything set just so it doesn’t do a bad job, but do you want a piece of software with a feature that’s just “okay” and doesn’t work well enough for you to use all the time? I didn’t think so. At the same time, if all I gave you for an upgrade was a new paint job and no new features worth mentioning, would you be excited about it? Again, I didn’t think so.
Long story short, I’ve been working hard at making MYStuff 2 (and MYStuff 2 Pro) an upgrade worth getting excited about. Rest assured that it is under very active development at the moment, and that it will be getting into beta “soon” with an expected ship date of “soon-ish”. Have patience. I promise it will be worth the wait.