<body bgcolor=#000033"><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener("load", function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <iframe src="http://www.blogger.com/navbar.g?targetBlogID=4830160160028833890&amp;blogName=DanShope.com&amp;publishMode=PUBLISH_MODE_FTP&amp;navbarType=BLUE&amp;layoutType=CLASSIC&amp;homepageUrl=http%3A%2F%2Fwww.danshope.com%2Fblog%2F&amp;blogLocale=en_US&amp;searchRoot=http%3A%2F%2Fblogsearch.google.com%2F" marginwidth="0" marginheight="0" scrolling="no" frameborder="0" height="30px" width="100%" id="navbar-iframe" title="Blogger Navigation and Search"></iframe> <div></div>

Update: Robotics Playground Templates

The last few weeks have been focused on getting the robotics playground up and running for the beta testers. A big part of configuring the system is deciding how to organize and deliver the user content.

On one hand, we can take the MySpace approach and give users nearly free reign to post whatever they want. This is good, because it allows creativity and novel presentation of design. The bad thing is, general 'net users don't create very compelling designs -- even if you know what looks good/bad, you aren't always motivated to create good design.

Enter the Facebook/LinkedIn approach -- novel content, "strict" layout. This is good because it allows people to post content without requiring much effort in design. It appeals to a different but broader set of users.

The DanShope.com Robotics Playground paradigm finds somewhat middle ground. The software will provide some basic templates that expose targeted functionality for different facets of project documentation. There is also a more general template that allows for some level of customization.

While this is in no way a new concept, our approach feels very hands off while guiding the design elements into an aesthetically pleasing form. This balance is something that must be considered at both the user interface and the back end/supporting software phases of development.

If the platform is too restrictive, it doesn't inspire users to post their creative content -- but if it's too loose, viewers en masse might find it displeasing to hunt out information and won't feel comfortable on the site.

I'll be posting more about these templates shortly.

Labels: , , , ,

blog comments powered by Disqus

« Home | Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »
Subscribe to RSS Feed
Subscribe to DanShope.com
Who writes This Stuff?
Daniel Shope is the site owner and moderator of DanShope.com, a portal dedicated to robotics and engineering. Dan is currently a student at Carnegie Mellon University and is pursuing dual degrees in Mechanical and Biomedical engineering.

View Daniel Shope's profile on LinkedIn
Advertisements