CHI-WEB Archives

ACM SIGCHI WWW Human Factors (Open Discussion)

CHI-WEB@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Tadej Maligoj (Gmail)" <[log in to unmask]>
Reply To:
Tadej Maligoj (Gmail)
Date:
Fri, 8 Aug 2008 11:33:46 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (158 lines)
You are talking about the tool, not the product, so I do not see the  
reason of choosing the 'right' tool without regarding the skill of  
master. So, getting The tool without developer skill would give no  
great usability. Watching the matter this way would make you trouble.  
By the time getting enough available developer resources for realising  
the project there would be another tool, promising even better  
product ...

Best,

Tadej

Tadej Maligoj, Arhitekt
			m: 031 306 986
			e: [log in to unmask]
			b: http://maligoj.blogspot.com
			w: http://www.maligoj.com

On 8.8.2008, at 9:26, Mathijs Panhuijsen wrote:

> Well, fortunately I'm not looking for an easy answer. :)
> I'm more trying to find out what the pros and cons of each technology
> are.
> I'm noticing that a lot of different factors affect the choice of
> technology:
>
> -'Religious' reasons
> -Developer skills
> -Available developer resources
> -Customer requirements (e.g. do they allow installation of a plugin?)
> -Market acceptance/maturity of the technology
> and so on.
>
> As 'usability guy' in my organization, I would like to disregard all
> those factors (because other colleagues are plenty worried about  
> those)
> and look at each technology purely on the basis of UI design,
> specifically designing an enterprise-level B2B application.
>
> One objective measure, for example, would be to compare the amount and
> variety of GUI controls offered out of the box by each technology, or
> readily available for that technology.
>
> Another helpful piece of information would be to hear a usability
> designer talk about their experience working with technology X or Y  
> in a
> project (again focusing on the usability aspect): which were the
> pitfalls, what worked beautifully, and would they recommend it again?
>
> Like I said, I'm not expecting a clear, short answer to my question. I
> would just like to pick the mailing list members' brains.
>
> Kind regards,
>
> Mathijs
>
> -----Original Message-----
> From: David Malouf [mailto:[log in to unmask]]
> Sent: Friday, August 08, 2008 01:19
> To: Mathijs Panhuijsen
> Subject: Re: Best Web technology from usability perspective
>
> there r so many pieces to figuring out how to answer this question. Iy
> is part of a 1-day workshop I'll be teaching in NYC this October for
> SmartExperience.org.
>
> I have a slide deck on slideshare.net that might be helpful.
>
> But again there us not easy answer here. It really depends. Anyone who
> tells you otherwise is really blowing smoke.
>
> - dave
>
> On Aug 7, 2008, at 5:32 AM, Mathijs Panhuijsen
> <[log in to unmask]
>> wrote:
>
>> Hello everybody,
>>
>>
>>
>> My company is looking into choosing a new Web technology for building
>> their next generation GUI (browser-based).
>>
>> They are considering options ranging from a homebrew AJAX-based  
>> system
>> to the Google Web Toolkit to Microsoft Silverlight.
>>
>>
>>
>> My question to you is:
>>
>> Which Web technology would you recommend for building a RIA, purely
>> from
>> a usability point of view?
>>
>> We're talking here about a very rich application with loads of
>> functionality, not an 'interactive Web site'.
>>
>> In other words, which Web technology works best to develop the most
>> usable interfaces the quickest?
>>
>>
>>
>> Kind regards,
>>
>>
>>
>> Mathijs Panhuijsen
>>
>> Technical Writer
>>
>> SDL Tridion
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> This e-mail is intended exclusively for the addressee(s),and may not
>> be passed on to, or made available for use by any person other than
>> the addressee(s).SDL Tridion rules out any and every liability
>> resulting from any electronic transmission.
>>
>>   --------------------------------------------------------------
>>          Tip of the Day: Postings must be in plain text
>>    CHI-WEB: www.sigchi.org/web POSTINGS: mailto:[log in to unmask]
>>             MODERATORS: mailto:[log in to unmask]
>>      SUBSCRIPTION CHANGES & FAQ:  www.sigchi.org/web/faq.html
>>   --------------------------------------------------------------
>>
>
>
>
> This e-mail is intended exclusively for the addressee(s),and may not  
> be passed on to, or made available for use by any person other than  
> the addressee(s).SDL Tridion rules out any and every liability  
> resulting from any electronic transmission.
>
>    --------------------------------------------------------------
>    Tip of the Day: Quote only what you need from earlier postings
>     CHI-WEB: www.sigchi.org/web POSTINGS: mailto:[log in to unmask]
>              MODERATORS: mailto:[log in to unmask]
>       SUBSCRIPTION CHANGES & FAQ:  www.sigchi.org/web/faq.html
>    --------------------------------------------------------------
>

    --------------------------------------------------------------
    Tip of the Day: Quote only what you need from earlier postings
     CHI-WEB: www.sigchi.org/web POSTINGS: mailto:[log in to unmask]
              MODERATORS: mailto:[log in to unmask]
       SUBSCRIPTION CHANGES & FAQ:  www.sigchi.org/web/faq.html
    --------------------------------------------------------------

ATOM RSS1 RSS2