Platform Requirements
Our vision for Hubbub is a mobile application, compatible with all of the major smartphone lines. We implemented it using HTML5 and JavaScript, so it can run in any modern browser. Theoretically, any phone with a suitably advanced browser should be able to use Hubbub. In reality, running a browser with a JavaScript interpreter to run an application is fairly demanding, and one of our prototyping tools does a lot of work under the hood while the application is running (trading performance for speed of development), so if your phone has older hardware or a less optimized browser, Hubbub may run slowly.
If you are noticing input lag on your phone and would like a smoother testing experience, you can visit the URL in a desktop browser. The application should appear in a reduced-size area simulating a phone screen. Firefox and Chrome run Hubbub very well.
Instructions
Visit: http://www.mit.edu/~dynamic/hubbub/
As mentioned above, if your phone is having trouble running the app quickly, feel free to use a desktop browser instead.
If you're using a desktop browser, the width is already set to phone-sized with CSS. We recommend you re-size the height of your window to about the size of a phone for the full experience.
(You can download the complete source from GitHub.)
Shallow Parts
- Login and registration are not implemented
- All feed items are canned; there is currently no way to pull items from Twitter, Facebook, etc.
- The "Share" and "Save" buttons are stubs (these two actions are not directly related to the three essential tasks)
- Marking items as read has been left out (not one of the three essential tasks, and anyway, you'd quickly exhaust the list since it's canned data)
- No persistence - hitting refresh gives you a completely clean slate.
4 Comments
Christy Dennison
UI Evaluation
813HubbubUIEval.pdf
Andrew K Sugaya
Awesome job! Here's my evaluation:
Hubbub Evaluation
Unknown User (dway@mit.edu)
HeuristicEval_dway.pdf
Sacha Zyto
Wiki presentation: clear description of shallow parts.
Fidelity: good: prototype covers main scenarios
Usability: simpllicity: lots of screen real estate is taken by buttons vs real contents
double-duty: users can't really tell if tags are clickable, but they should be made clickable, to allow opportunistic filtering.
Overall: quite good realization and design stretches