<?xml-stylesheet type="text/xsl" href="https://community.element14.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>R&amp;amp;S RTM3004 RoadTest in Depth – Chapter 3: Usability Aspects</title><link>/members-area/personalblogs/b/gough-lui-s-blog/posts/r-s-rtm3004-roadtest-in-depth-chapter-3-usability-aspects</link><description>While on-paper specifications are easy to compare, they only tell part of the story. While a device might be excellent on-paper, it could be difficult to use or have a number of important limitations. In this section, I look at the usability aspects </description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator></channel></rss>