A couple of suggestions for improving Seesmic
Loic,
First off, congratulations on seesmic's popularity. It's certainly attracting a lot of attention and a lot of users, myself included.
But as a developer and former CTO myself, I think seesmic could become even more successful if its implementation was simplified and its basic utility filled out a little better. Here are two suggestions I think might make a big difference.
Except for the video rendering and its play/pause controls, you would make a LOT of friends by going to an XHTML/CSS/javascript implementation. Memory usage would be reduced and performance would certainly improve, perhaps dramatically. Forget all the cute list animation. Those lists frequently screw up and overwrite, or stall and lock up the browser.
Finding a user could be done several ways. Here are two:
Thanks for listening!
First off, congratulations on seesmic's popularity. It's certainly attracting a lot of attention and a lot of users, myself included.
But as a developer and former CTO myself, I think seesmic could become even more successful if its implementation was simplified and its basic utility filled out a little better. Here are two suggestions I think might make a big difference.
Ditch all the Flash except for video rendering
Yeah, the rotating lists and animation are fancy, but all that "flashturbation" devours processor cycles and memory. While on seesmic, my browser will frequently pin the processor at 100% for minutes at a time, and gobble up nearly 120 megabytes of page-file usage.Except for the video rendering and its play/pause controls, you would make a LOT of friends by going to an XHTML/CSS/javascript implementation. Memory usage would be reduced and performance would certainly improve, perhaps dramatically. Forget all the cute list animation. Those lists frequently screw up and overwrite, or stall and lock up the browser.
Include some way to find users so I can follow them
It's nearly impossible to locate a user's account page unless you can find a post they've made in the public timeline.Finding a user could be done several ways. Here are two:
- A search window.
- Something like Twitter's convention of recognizing a simple URL that contains the users handle. (i.e., http://twitter.com/joec0914).
Thanks for listening!
2 Comments:
Have to agree with both of these!
The only other thing I'd love to see is a 'follow the thread' feature.
It's frustrating to come in to see a bunch of "RE:subject X" replies without being able to thread back to the original "subject X" seesmic.
Hello Joe, thank you so much for your feedback and I also saw your video. Will reply to your email now.
Post a Comment
<< Home