<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Boxes and Arrows: Comments by rajat julka</title>
    <link>http://www.boxesandarrows.com/person/770</link>
    <pubDate>Fri, 26 Jan 2007 14:52:46 GMT</pubDate>
    <description>Comments by rajat julka</description>
    <item>
      <description>&lt;p&gt;Just read this entire article and feedback upon the same, I think you have not used xhtml/HTML Dom/javascript &lt;span class="caps"&gt;DOM&lt;/span&gt; to its fullest. If you use them you will see there are minimum cross browser issues.&lt;/p&gt;

	&lt;p&gt;My experience says that presentation layer should always be different than your logical layer&amp;#8230; so take any language &amp;#8230;  i see people talking lot about java here&amp;#8230; we can use tiles for layout managment but ultimately your presentation layer will involve &lt;span class="caps"&gt;HTML&lt;/span&gt;.&lt;/p&gt;

	&lt;p&gt;&lt;span class="caps"&gt;XHTML&lt;/span&gt; + css2.0 gives you lot of things in the field of accessibility, usability, faster downloads no plugin requirements on your browser&amp;#8230;.&lt;/p&gt;

	&lt;p&gt;you article is 3 years old now&amp;#8230; if you have created any site without using &lt;span class="caps"&gt;HTML&lt;/span&gt;/JS/CSS please send me the link .. i would like to see how much future insight your article had&amp;#8230;. facts speak louder and clearer&amp;#8230; :))&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/htmls_time_is_over_lets_move_on_#content_2889</link>
      <guid>http://www.boxesandarrows.com/view/htmls_time_is_over_lets_move_on_#content_2889</guid>
      <pubDate>Fri, 26 Jan 2007 14:52:46 GMT</pubDate>
      <author>rajat julka</author>
    </item>
    <item>
      <description>&lt;p&gt;This is a nice article which talks about creating wireframes instead of working &lt;span class="caps"&gt;HTML&lt;/span&gt; prototypes for the client to have a better and common understanding at the design level phase of the project.&lt;/p&gt;

	&lt;p&gt;The approach is best suitable when we are working on not very big project may be around 600-900 hours project.  Bruce as you said that Sometimes it takes you a while to figure out which one is new and which ones you have already read. you can also just take the jpg&amp;#8217;s for the design (with annotation) and import the same in flash and it will only take maximum of 8 hours to give a little interactions (you can just define click events on actual button area to call next screens)... and that can help the user to understand it better and will be more impressive way to present the UI wireframe (now interactive) to the client.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/the_guided_wire#content_3017</link>
      <guid>http://www.boxesandarrows.com/view/the_guided_wire#content_3017</guid>
      <pubDate>Fri, 26 Jan 2007 14:52:52 GMT</pubDate>
      <author>rajat julka</author>
    </item>
    <item>
      <description>&lt;p&gt;Nice approach. but do you really think that making the personas live (by using the design/development team) is no different than having the design team members make persona and profiles on paper.&lt;/p&gt;

	&lt;p&gt;You have given an example of a Robert DeNiro (taxi driver) but in that case he understands the role by actually being with the orignial driver (not an actor) and the motive behind that is too study the role. do you think in an average size project you can actually take your complete team to an end user environment and then can ask them to think and behave like the end user while making persona&amp;#8217;s and even while using those persona&amp;#8217;s ,profiles for a usable interface.&lt;/p&gt;

	&lt;p&gt;This approach may work for a big project which can handle that cost of making the team spent some time to feel and then act (to provide authentic data) as per the persona.&lt;/p&gt;

	&lt;p&gt;So i think the usability testing with a real set of users is a best approach to the most usable interface. as far as personas are concerned, be it live persona or a paper based thing only .. does not matter that much because both the approaches will document the views of designers and not the actual end user.&lt;/p&gt;

	&lt;p&gt;Thanks&lt;br /&gt;Rajat&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/bring_your_pers#content_4076</link>
      <guid>http://www.boxesandarrows.com/view/bring_your_pers#content_4076</guid>
      <pubDate>Fri, 26 Jan 2007 14:53:40 GMT</pubDate>
      <author>rajat julka</author>
    </item>
    <item>
      <description>&lt;p&gt;Good Article!&lt;/p&gt;

	&lt;p&gt;Web Anlaytics can be very usefull set of information to test wether the Information Architect has done the job correctly or not.&lt;/p&gt;

	&lt;p&gt;Web Analytics can help us calculate the difference between &amp;#8220;how designer completes the IA work &amp;#8216;THINKING from user perspective &amp;#8217; &amp;#8221; and &amp;#8220;how the target audience behaves/interacts with the application &amp;#8216;IN &lt;span class="caps"&gt;ORIGINAL&lt;/span&gt;&amp;#8217; &amp;#8221;.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/metrics_for_heu7#content_4078</link>
      <guid>http://www.boxesandarrows.com/view/metrics_for_heu7#content_4078</guid>
      <pubDate>Fri, 26 Jan 2007 14:53:40 GMT</pubDate>
      <author>rajat julka</author>
    </item>
    <item>
      <description>&lt;p&gt;This is an excellent article.&lt;/p&gt;

	&lt;p&gt;Few inputs which you might like to add in your article.&lt;/p&gt;

	&lt;p&gt;There is another focused way of presenting the &#8220;registration&#8221; form to the users unlike &lt;span class="caps"&gt;GMAIL&lt;/span&gt;. On the main page of the site user is welcome with a first focused option to &#8220;register&#8221;. Have a look at &lt;a href="http://www.linkedin.com" rel="nofollow"&gt;www.linkedin.com&lt;/a&gt; . It takes the first 3 required fields on the very first page and asks for only &#8220;required fields&#8221; data entry for the registration to complete.&lt;/p&gt;

	&lt;p&gt;The emphasis here is usable and simple IA that makes sense to any novice site user for the registration process. Use of less (or only required fields) for the registration gives the breathing space to the page and excites the user that only 7 fields are required to be filled in for getting registered with the site. The less number of fields on the page enables designers to make the text fields appear big/bold/clear that gives lot of comfort to visually week users.&lt;/p&gt;

	&lt;p&gt;Even if the user is performing the registration process which is not taken with too excitement by web users (usually &lt;br /&gt;because of lengthy forms and all) this simple IA helps in providing exciting user experience for the users.&lt;/p&gt;

	&lt;p&gt;Another thing which I personally have experienced in our user experience studies and I would suggest that you make should make it as a part of your research is the point of &#8220;validation Interaction&#8221;. As per my learning in the user experience studies the use of &lt;span class="caps"&gt;AJAX&lt;/span&gt; (asynchronous calls) for validating form fields have further helped in improving the user experience of forms. e.g  When a user enters the intended username in the form field and he moves to the password field, the system interacts with the user by showing the message of &#8220;status&#8221; of the availability of the desired user name as entered by the user.  This is an enhanced user &#8211; computer interaction where the current context of communication is not breaking as the system has responded to the user that the intended user name is not available and he/she must use another name in order to proceed with the registration process. Otherwise in the old sites (some people who still like to validate the form after the complete data entry by the users) the fields are validated when the data is submitted by the users and then the system tells them that (after entering whole lot of data) there is a problem with the very first field i.e. user name is not available or something, and that frustrates any user (novice or expert).&lt;/p&gt;

	&lt;p&gt;Meaningful interaction between user and application also enables us to design a rich user experience of form pages.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/getting-a-forms98#content_30723</link>
      <guid>http://www.boxesandarrows.com/view/getting-a-forms98#content_30723</guid>
      <pubDate>Sat, 05 Mar 2011 05:58:28 GMT</pubDate>
      <author>rajat julka</author>
    </item>
    <item>
      <description>&lt;p&gt;Good Article&amp;#8230; Erin.&lt;/p&gt;

	&lt;p&gt;There are a lot more features and concepts (depending upon your target audience) available for social sites but the above points as mentioned by Erin are basic foundation blocks. I believe point number two and three are the most important points for consideration while creating a social networking site. More social interactions/participation on sites with little or simple UI interactions is the mantra for a successful site.&lt;/p&gt;

	&lt;p&gt;Again&amp;#8230; thanks for sharing this nice article Erin&amp;#8230; Keep posting :)&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/5-steps-to-building#content_50101</link>
      <guid>http://www.boxesandarrows.com/view/5-steps-to-building#content_50101</guid>
      <pubDate>Tue, 26 Jan 2010 08:15:34 GMT</pubDate>
      <author>rajat julka</author>
    </item>
  </channel>
</rss>

