Topic: Chumby 2.0?
I was just wondering if you envision keeping chumby pretty much the same over time, or if you are expecting frequent upgrades and changes to the software and/or the hardware.
Thinking outside the box for "hacking" potential, many ideas run up against the question of whether or not a particular mod will be rendered worthless by a change in the available units.
Simple example. Suppose I develop a business based on turning chumbys into kiosks. I might spend some money on tooling for the part of the thing that holds the chumby in place on the top of the unit. What sort of expectations can you give me regarding how frequently I might need to start over and re-design my kiosk because of design changes to chumby.
From the software side, I'm told that the production chumbys will ship with a microphone. Suppose I write some software that depends on that functionality. Do I have any reasonable expectation that all future chumbys will ship with a microphone?
I realize I'm asking for the moon here, but it's not an empty question. I'm just trying to get you to consider these "outside the box" uses for chumby and perhaps architect some sort of an upgrade path that makes it practical for you to give developers some sort of visibility/expectations on the stability of various aspects of the design.
One example would be making "old" versions of the product available for a year after any major design change.
A few years ago I got all excited about doing something like this with PalmOS devices, and before I even had time to get into it, they started to put out a completely new design every 6 months or so. No way to keep up with that. Trying to make iPod accessories comes with the same sort of a "that's so last week" schedule of major design changes.
Chumby is making a big deal out of it's "hackability". I just wanted to push your nose down in the carpet in a pile of stuff that is particularly difficult for a company to deal with (both the parent company and those that try to develop accessories/modifications/alternative-uses for their products.) I'm hoping you will look at this now and talk to developers about it and work out a reasonable compromise now, rather than waiting until it becomes an "issue" (or a company killing gotcha for lots of small companies that are relying on you and your success).
thanks,
jp