Yeah, it's a very difficult thing to draw the line between adding every feature that everyone would ever want, ending up with a bewildering array of settings and options, and keeping the device reasonable for someone to just pick up and use without having to consult a manual.
In some cases, I think we may have gone too far - many people find the current alarm system to be overly complicated, however, it's a direct result of user feature requests - probably the area where we've been the most reactive on features.
I tend to address these sorts of things, when a small group wants something, but can't collectively decide what it should be, as easter eggs.
There are dozens of threads like this one - one group strongly feels the chumby is a clock, and so all of the primary features should be clock-related. Another group thinks the device is first and foremost a music playing device, so those features should be brought forward. Others think of it as a widgets-playing device (what we originally designed), and so want more capabilities and options there.
A lot of these requests result in what we call "psychic chumby" - there are lots of posts that want the top button to magically know what the user wants, which is to go to the single thing they're thinking of at that moment, ex. start the music, stop the music, go to the next track, delay the next alarm, advance the widget, show the time. Everyone wants their favorite feature, or indeed multiple features, to be only one button press away, and that's simply not possible with such a small screen and only one button.
Some of these discussions eventually devolve to the next stage, "morse code chumby", when you see things like "hold for 2 seconds means X, hold for 3 seconds means Y, double click means Z", where one has to have a perfect timing to navigate an arcane and undiscoverable vocabulary of taps and clicks.
We actually have an example of this in practice - the use of the accelerometer to advance widgets. Many people don't know that you can hold the button and tilt the device to move from one widget to the next or previous. Of course, there's no reason why anyone would naturally figure that out.
The ultimate "easter egg", of course, is that the device is open enough that with sufficient skills and cleverness, one can make it do anything one wants within the restraints of the hardware. Ironically, that may be *more* frustrating to those without the skills, since the Holy Grail Chumby is there but just out of reach. If the device were closed, then one could at least be comforted that there's nothing that could possibly be done.
Anyway, be assured that we are listening and consider these things very carefully - those folks that have been chumby users for a while can attest that stuff folks request very often end up in the product, though sometimes in some different form.