COmanage Users List

[Mike Manske <>]

Sorry if you got this twice but I had an email bounce on the first
send. For a long time, web app designers and users alike were told not
to use the browser back button, but with the advent of mobile devices,
etc. it has returned to common use.

For me, I would like to see an info msg when a form input value has
been changed, but not saved, as is sometimes seen in apps. Perhaps you
have considered this approach and rejected reasons of simplicity. I
would say it should be reconsidered since the form paradigm has
evolved: many modern apps do not require a ‘submit’ button but send an
update to the server when a form value is changed. So, more clarity as
to the current state of my entry form is desirable.
-- 

Michael A. (Mike) Manske
Leonard E. Parker Center for Gravitation, Cosmology and Astrophysics
University of Wisconsin - Milwaukee
KIRC 4198


On Wed, Dec 5, 2018 at 12:18 PM Arlen Johnson
<>
 wrote:
>
> Thanks, Mihály - agreed: we're open for more feedback.
>
> Best wishes -
> Arlen
>
> On 12/5/18 12:05 PM, Mihály Héder wrote:
>
> Hi,
>
> well, I really have no strong opinion on the matter - I guess one data 
> point does not make a trend, so if someone else gives this feedback you 
> should consider it as an issue?
>
> Mihály
>
> On Fri, Nov 30, 2018 at 4:34 AM Arlen Johnson 
> <>
>  wrote:
>>
>> Hi, All -
>>
>>
>> As a counterpoint, consider that fewer choices lead to better UX and less 
>> potential for confusion. In the case of forms, users should have two 
>> choices: to submit the form or stop moving forward. The browser back 
>> button serves the latter purpose, and lacking any other means of doing so, 
>> the user will use it: it is a familiar paradigm.
>>
>>
>> For the same reason that reset buttons are discouraged, back (or cancel) 
>> buttons on forms can cause users to accidentally lose their work. Even if 
>> such an outcome is rare, it is so undesirable that it is better to avoid 
>> the risk entirely.
>>
>>
>> In mobile app development this is different: navigation has to be cooked 
>> into the application itself, but there are common paradigms for this as 
>> well, and designers are encouraged to follow them.  Mobile browsing is 
>> more akin to desktop browser paradigms, though, and the browser back 
>> button is easily found and regularly used.
>>
>>
>> I'm definitely open to seeing some evidence that suggests what I'm saying 
>> is incorrect.
>>
>>
>> Best wishes -
>> Arlen
>>
>>
>> On 11/29/18 10:09 AM, Richard Frovarp wrote:
>>
>> I wouldn't rely on the user using a back button in a mobile environment. 
>> It gets rather confusing on those sorts of devices for many users. Even on 
>> desktop OSes, users have been partially taught that hitting the back 
>> button can cause problems. So they are likely less likely to use it.
>>
>> ________________________________
>> From: 
>> 
>>  
>> <>
>>  on behalf of Mihály Héder 
>> <>
>> Sent: Thursday, November 29, 2018 2:36:25 AM
>> To: Benn Oshrin
>> Cc: 
>> ;
>>  
>> 
>> Subject: Re: [comanage-users] COmanage UX feedback
>>
>> Hi,
>>
>> well, I rely on our UX experts on this who say it should be fixed so if 
>> you reopen that ticket we would be grateful.
>>
>> Cheers
>> Mihály
>>
>> On Wed, Nov 28, 2018 at 2:52 PM Benn Oshrin 
>> <>
>>  wrote:
>>
>> Hey Mihály,
>>
>> For some context, here's the JIRA issue from 2011 when we first
>> discussed this :)
>>
>>   https://bugs.internet2.edu/jira/browse/CO-70
>>
>> At the time, we concluded the back/cancel buttons were confusing and
>> redundant (since you can indeed just press the back button in your
>> browser). (We also subsequently dropped all the "Reset Form" buttons.)
>>
>> I'm certainly happy to reopen this discussion, especially if we have
>> feedback from actual user testing or something.
>>
>> Thanks,
>>
>> -Benn-
>>
>> On 11/28/18 3:21 AM, Mihály Héder wrote:
>> > Hi List,
>> >
>> > as part of the eduTEAMS effort a UX expert team has conducted an
>> > analysis of our user-facing stuff and COmanage as a part of that. There
>> > is one issue I want to raise here: missing "back" or "cancel" button on
>> > forms such as "add email" for a person.
>> >
>> > I think it is fair from the UX team to raise that: while I'll just reach
>> > for the browser's back button without hesitation, I imagine it could
>> > indeed cause some confusion for some users, what happens with the data, 
>> > etc.
>> >
>> > Cheers
>> > Mihály
>> >
>> > --
>> > Mihály Héder, PhD
>> > Research Fellow
>> > Institute for Computer Science and Control
>> > Hungarian Academy of Sciences
>>
>>
>>
>> --
>> Mihály Héder, PhD
>> Research Fellow
>> Institute for Computer Science and Control
>> Hungarian Academy of Sciences
>>
>> --
>> Arlen Johnson, Spherical Cow Group
>> 
>> https://sphericalcowgroup.com
>
>
>
> --
> Mihály Héder, PhD
> Research Fellow
> Institute for Computer Science and Control
> Hungarian Academy of Sciences
>
> --
> Arlen Johnson, Spherical Cow Group
> 
> https://sphericalcowgroup.com