Move Demo Button into the Options Menu

Hi all,

I want to start a discussion about moving the “demo” user button into the
"options" menu on the CommCare Client’s login screen. The reasoning: it’s
too easy to login as demo, esp. in a region like Tanzania when the barrier
to entering uid and pwd is quite high (people don’t like it, aren’t used to
it, might need to look up their credentials, etc.). User’s also experience
no consequences for selecting demo user: there are no warnings that the data
is treated differently and the application isn’t limited in functionality at
all. I think a good near-term solution to this is to make the standard login
seem like the default by moving demo into the options menu. What do you
think?

Jon

Hi Jon,

This might be a totally reasonable thing to do, but I would have some
concern of pushing the problem the other direction. By essentially
hiding the demo login, it becomes difficult to practice, so then
"fake"/practice data will likely end up coming from the login.

Playing off of a subtle point you made, I like the idea of limiting
functionality when you are in demo mode. What about a message at the
end of a form saying “this data will not be sent. if it is real data,
please login with your username/password” (or something to that
effect). Changing colors and inserting other warnings onscreen (e.g.
maybe a bar at the top of the chatterbox that says “Mazoezi!” or
something) might be another good way to remind users that they are in
demo mode.

Anyway, I definitely agree this is a problem and I’m interested to
hear what others on the list think about how to best to address it.

Brian

··· On Thu, Jun 30, 2011 at 1:26 AM, Jonathan Payne wrote: > Hi all, > I want to start a discussion about moving the "demo" user button into the > "options" menu on the CommCare Client's login screen. The reasoning: it's > too easy to login as demo, esp. in a region like Tanzania when the barrier > to entering uid and pwd is quite high (people don't like it, aren't used to > it, might need to look up their credentials, etc.). User's also experience > no consequences for selecting demo user: there are no warnings that the data > is treated differently and the application isn't limited in functionality at > all. I think a good near-term solution to this is to make the standard login > seem like the default by moving demo into the options menu. What do you > think? > Jon > > >

Jon,

This is a fascinating question. I’d love to hear how other folks feel about
the demo mode, it’s accessibility, and how apparent it is of a concept to
the CHW’s. I agree that popups and text prompts are possibly not the best
ways to handle notifying the users that they are in demo mode, since the
concept is kind of abstract and if the application feels identical
otherwise, it’s awkward. In CommCare 1.2 sense mode, the top menu bar
actually displays the name of the currently registered user, to reinforce
the login, we could experiment with places to include the logged in user
elsewhere (IE: “Send all Unsent forms from ctsims (3)”).

I feel like it will be difficult to approach this properly without a pretty
good impression of the ways in which folks use demo mode. Brian’s workflow,
for instance, is good if people only want to demo entry, but not as useful
if people want to test out a deployment on the server side as well. I don’t
believe anyone has any interest in using demo mode to submit data, is that a
correct statement?

-Clayton

··· On Thu, Jun 30, 2011 at 1:18 PM, Brian DeRenzi wrote:

Hi Jon,

This might be a totally reasonable thing to do, but I would have some
concern of pushing the problem the other direction. By essentially
hiding the demo login, it becomes difficult to practice, so then
"fake"/practice data will likely end up coming from the login.

Playing off of a subtle point you made, I like the idea of limiting
functionality when you are in demo mode. What about a message at the
end of a form saying “this data will not be sent. if it is real data,
please login with your username/password” (or something to that
effect). Changing colors and inserting other warnings onscreen (e.g.
maybe a bar at the top of the chatterbox that says “Mazoezi!” or
something) might be another good way to remind users that they are in
demo mode.

Anyway, I definitely agree this is a problem and I’m interested to
hear what others on the list think about how to best to address it.

Brian

On Thu, Jun 30, 2011 at 1:26 AM, Jonathan Payne paynejd@gmail.com wrote:

Hi all,
I want to start a discussion about moving the “demo” user button into the
"options" menu on the CommCare Client’s login screen. The reasoning: it’s
too easy to login as demo, esp. in a region like Tanzania when the
barrier
to entering uid and pwd is quite high (people don’t like it, aren’t used
to
it, might need to look up their credentials, etc.). User’s also
experience
no consequences for selecting demo user: there are no warnings that the
data
is treated differently and the application isn’t limited in functionality
at
all. I think a good near-term solution to this is to make the standard
login
seem like the default by moving demo into the options menu. What do you
think?
Jon

Hey,

Interesting discussion because I, myself, have had similar concerns.

Right before going into “demo” mode, CC does show a rather lengthy
disclaimer basically saying that "you are entering demo mode “. Though,
this may not be sufficient for our low-literacy or poor eye sight users
which may have trouble reading and/or understanding the text. It would be
potentially useful if an automatic audio message could be feasible for this
"disclaimer message”.

To Brian’s suggestion, I think that submitting data in demo mode is actually
useful. During a practice periods post-training, it’s been helpful to
verify that users are actually practicing via CCHQ. If not, then we know
there needs to be follow-up.

Just throwing out another idea, what if the current “You’ve completed a
form” message could be different when in demo mode and say “You’ve completed
a form in DEMO MODE”. It’s hard to determine how closely users actually
look at this screen.

Thanks,
Nick

Nick P. Amland

CommCare Field Fellow
Dimagi, Inc.
Dodoma, Tanzania
Google Voice: 253.642.7790
TZ Mobile: +255 762 740 996
Email: namland@dimagi.com namland08@gmail.com

··· On Thu, Jun 30, 2011 at 8:18 PM, Brian DeRenzi wrote:

Hi Jon,

This might be a totally reasonable thing to do, but I would have some
concern of pushing the problem the other direction. By essentially
hiding the demo login, it becomes difficult to practice, so then
"fake"/practice data will likely end up coming from the login.

Playing off of a subtle point you made, I like the idea of limiting
functionality when you are in demo mode. What about a message at the
end of a form saying “this data will not be sent. if it is real data,
please login with your username/password” (or something to that
effect). Changing colors and inserting other warnings onscreen (e.g.
maybe a bar at the top of the chatterbox that says “Mazoezi!” or
something) might be another good way to remind users that they are in
demo mode.

Anyway, I definitely agree this is a problem and I’m interested to
hear what others on the list think about how to best to address it.

Brian

On Thu, Jun 30, 2011 at 1:26 AM, Jonathan Payne paynejd@gmail.com wrote:

Hi all,
I want to start a discussion about moving the “demo” user button into the
"options" menu on the CommCare Client’s login screen. The reasoning: it’s
too easy to login as demo, esp. in a region like Tanzania when the
barrier
to entering uid and pwd is quite high (people don’t like it, aren’t used
to
it, might need to look up their credentials, etc.). User’s also
experience
no consequences for selecting demo user: there are no warnings that the
data
is treated differently and the application isn’t limited in functionality
at
all. I think a good near-term solution to this is to make the standard
login
seem like the default by moving demo into the options menu. What do you
think?
Jon

I like the idea (for non-commcare-sense deployments) of possibly doing away
with “Send now/send later” and just trying to send the form best-effort (and
delete it if it fails to send), replacing the screen with something like

“In demo mode, forms are submitted automatically”

as Nick suggests. Maybe that screen looking different would act as a good
affordance that the user isn’t in normal CommCare mode.

-Clayton

··· On Thu, Jun 30, 2011 at 2:02 PM, Nick Amland wrote:

Hey,

Interesting discussion because I, myself, have had similar concerns.

Right before going into “demo” mode, CC does show a rather lengthy
disclaimer basically saying that "you are entering demo mode “. Though,
this may not be sufficient for our low-literacy or poor eye sight users
which may have trouble reading and/or understanding the text. It would be
potentially useful if an automatic audio message could be feasible for this
"disclaimer message”.

To Brian’s suggestion, I think that submitting data in demo mode is
actually useful. During a practice periods post-training, it’s been helpful
to verify that users are actually practicing via CCHQ. If not, then we know
there needs to be follow-up.

Just throwing out another idea, what if the current “You’ve completed a
form” message could be different when in demo mode and say “You’ve completed
a form in DEMO MODE”. It’s hard to determine how closely users actually
look at this screen.

Thanks,
Nick

Nick P. Amland

CommCare Field Fellow
Dimagi, Inc.
Dodoma, Tanzania
Google Voice: 253.642.7790
TZ Mobile: +255 762 740 996
Email: namland@dimagi.com namland08@gmail.com

On Thu, Jun 30, 2011 at 8:18 PM, Brian DeRenzi bderenzi@gmail.com wrote:

Hi Jon,

This might be a totally reasonable thing to do, but I would have some
concern of pushing the problem the other direction. By essentially
hiding the demo login, it becomes difficult to practice, so then
"fake"/practice data will likely end up coming from the login.

Playing off of a subtle point you made, I like the idea of limiting
functionality when you are in demo mode. What about a message at the
end of a form saying “this data will not be sent. if it is real data,
please login with your username/password” (or something to that
effect). Changing colors and inserting other warnings onscreen (e.g.
maybe a bar at the top of the chatterbox that says “Mazoezi!” or
something) might be another good way to remind users that they are in
demo mode.

Anyway, I definitely agree this is a problem and I’m interested to
hear what others on the list think about how to best to address it.

Brian

On Thu, Jun 30, 2011 at 1:26 AM, Jonathan Payne paynejd@gmail.com wrote:

Hi all,
I want to start a discussion about moving the “demo” user button into
the
"options" menu on the CommCare Client’s login screen. The reasoning:
it’s
too easy to login as demo, esp. in a region like Tanzania when the
barrier
to entering uid and pwd is quite high (people don’t like it, aren’t used
to
it, might need to look up their credentials, etc.). User’s also
experience
no consequences for selecting demo user: there are no warnings that the
data
is treated differently and the application isn’t limited in
functionality at
all. I think a good near-term solution to this is to make the standard
login
seem like the default by moving demo into the options menu. What do you
think?
Jon

i like changing the colors in chatterbox

··· On Thu, Jun 30, 2011 at 2:07 PM, Clayton Sims wrote:

I like the idea (for non-commcare-sense deployments) of possibly doing away
with “Send now/send later” and just trying to send the form best-effort (and
delete it if it fails to send), replacing the screen with something like

“In demo mode, forms are submitted automatically”

as Nick suggests. Maybe that screen looking different would act as a good
affordance that the user isn’t in normal CommCare mode.

-Clayton

On Thu, Jun 30, 2011 at 2:02 PM, Nick Amland namland@dimagi.com wrote:

Hey,

Interesting discussion because I, myself, have had similar concerns.

Right before going into “demo” mode, CC does show a rather lengthy
disclaimer basically saying that "you are entering demo mode “. Though,
this may not be sufficient for our low-literacy or poor eye sight users
which may have trouble reading and/or understanding the text. It would be
potentially useful if an automatic audio message could be feasible for this
"disclaimer message”.

To Brian’s suggestion, I think that submitting data in demo mode is
actually useful. During a practice periods post-training, it’s been helpful
to verify that users are actually practicing via CCHQ. If not, then we know
there needs to be follow-up.

Just throwing out another idea, what if the current “You’ve completed a
form” message could be different when in demo mode and say “You’ve completed
a form in DEMO MODE”. It’s hard to determine how closely users actually
look at this screen.

Thanks,
Nick

Nick P. Amland

CommCare Field Fellow
Dimagi, Inc.
Dodoma, Tanzania
Google Voice: 253.642.7790
TZ Mobile: +255 762 740 996
Email: namland@dimagi.com namland08@gmail.com

On Thu, Jun 30, 2011 at 8:18 PM, Brian DeRenzi bderenzi@gmail.comwrote:

Hi Jon,

This might be a totally reasonable thing to do, but I would have some
concern of pushing the problem the other direction. By essentially
hiding the demo login, it becomes difficult to practice, so then
"fake"/practice data will likely end up coming from the login.

Playing off of a subtle point you made, I like the idea of limiting
functionality when you are in demo mode. What about a message at the
end of a form saying “this data will not be sent. if it is real data,
please login with your username/password” (or something to that
effect). Changing colors and inserting other warnings onscreen (e.g.
maybe a bar at the top of the chatterbox that says “Mazoezi!” or
something) might be another good way to remind users that they are in
demo mode.

Anyway, I definitely agree this is a problem and I’m interested to
hear what others on the list think about how to best to address it.

Brian

On Thu, Jun 30, 2011 at 1:26 AM, Jonathan Payne paynejd@gmail.com wrote:

Hi all,
I want to start a discussion about moving the “demo” user button into
the
"options" menu on the CommCare Client’s login screen. The reasoning:
it’s
too easy to login as demo, esp. in a region like Tanzania when the
barrier
to entering uid and pwd is quite high (people don’t like it, aren’t
used to
it, might need to look up their credentials, etc.). User’s also
experience
no consequences for selecting demo user: there are no warnings that the
data
is treated differently and the application isn’t limited in
functionality at
all. I think a good near-term solution to this is to make the standard
login
seem like the default by moving demo into the options menu. What do you
think?
Jon

I also like the idea of different colors. Could also make the login
and demo buttons more distinct by spacing them out, making them
bigger, and using those respective different colors.

Demo mode is invaluable for training since you can create a set of
dummy data which can be copied from phone to phone. Having one button
access on the first screen allows training to start immediately with
practice cases, saving instruction on user login until later, which is
very useful if the phones don’t yet have SIMs or GPRS access.

Derek

··· On 6/30/11, Drew Roos wrote: > i like changing the colors in chatterbox > > On Thu, Jun 30, 2011 at 2:07 PM, Clayton Sims wrote: > >> I like the idea (for non-commcare-sense deployments) of possibly doing >> away >> with "Send now/send later" and just trying to send the form best-effort >> (and >> delete it if it fails to send), replacing the screen with something like >> >> "In demo mode, forms are submitted automatically" >> >> as Nick suggests. Maybe that screen looking different would act as a good >> affordance that the user isn't in normal CommCare mode. >> >> -Clayton >> >> >> On Thu, Jun 30, 2011 at 2:02 PM, Nick Amland wrote: >> >>> Hey, >>> >>> Interesting discussion because I, myself, have had similar concerns. >>> >>> Right before going into "demo" mode, CC does show a rather lengthy >>> disclaimer basically saying that "you are entering demo mode ". Though, >>> this may not be sufficient for our low-literacy or poor eye sight users >>> which may have trouble reading and/or understanding the text. It would >>> be >>> potentially useful if an automatic audio message could be feasible for >>> this >>> "disclaimer message". >>> >>> To Brian's suggestion, I think that submitting data in demo mode is >>> actually useful. During a practice periods post-training, it's been >>> helpful >>> to verify that users are actually practicing via CCHQ. If not, then we >>> know >>> there needs to be follow-up. >>> >>> Just throwing out another idea, what if the current "You've completed a >>> form" message could be different when in demo mode and say "You've >>> completed >>> a form in DEMO MODE". It's hard to determine how closely users actually >>> look at this screen. >>> >>> Thanks, >>> Nick >>> >>> Nick P. Amland >>> >>> CommCare Field Fellow >>> Dimagi, Inc. >>> Dodoma, Tanzania >>> Google Voice: 253.642.7790 >>> TZ Mobile: +255 762 740 996 >>> Email: namland@dimagi.com >>> >>> >>> >>> On Thu, Jun 30, 2011 at 8:18 PM, Brian DeRenzi wrote: >>> >>>> Hi Jon, >>>> >>>> This might be a totally reasonable thing to do, but I would have some >>>> concern of pushing the problem the other direction. By essentially >>>> hiding the demo login, it becomes difficult to practice, so then >>>> "fake"/practice data will likely end up coming from the login. >>>> >>>> Playing off of a subtle point you made, I like the idea of limiting >>>> functionality when you are in demo mode. What about a message at the >>>> end of a form saying "this data will not be sent. if it is real data, >>>> please login with your username/password" (or something to that >>>> effect). Changing colors and inserting other warnings onscreen (e.g. >>>> maybe a bar at the top of the chatterbox that says "Mazoezi!" or >>>> something) might be another good way to remind users that they are in >>>> demo mode. >>>> >>>> Anyway, I definitely agree this is a problem and I'm interested to >>>> hear what others on the list think about how to best to address it. >>>> >>>> Brian >>>> >>>> >>>> On Thu, Jun 30, 2011 at 1:26 AM, Jonathan Payne wrote: >>>> > Hi all, >>>> > I want to start a discussion about moving the "demo" user button into >>>> the >>>> > "options" menu on the CommCare Client's login screen. The reasoning: >>>> it's >>>> > too easy to login as demo, esp. in a region like Tanzania when the >>>> barrier >>>> > to entering uid and pwd is quite high (people don't like it, aren't >>>> used to >>>> > it, might need to look up their credentials, etc.). User's also >>>> experience >>>> > no consequences for selecting demo user: there are no warnings that >>>> > the >>>> data >>>> > is treated differently and the application isn't limited in >>>> functionality at >>>> > all. I think a good near-term solution to this is to make the standard >>>> login >>>> > seem like the default by moving demo into the options menu. What do >>>> > you >>>> > think? >>>> > Jon >>>> > >>>> > >>>> > >>>> >>> >>> >> >


Sent from my mobile device

yes…even I agree with others…there is no fun of having a
demo mode forms 2 be sent…it should just

serve the purpose of training for CHW and practice that CHW can do.

··· On Fri, Jul 1, 2011 at 12:06 AM, Derek Treatman wrote:

I also like the idea of different colors. Could also make the login
and demo buttons more distinct by spacing them out, making them
bigger, and using those respective different colors.

Demo mode is invaluable for training since you can create a set of
dummy data which can be copied from phone to phone. Having one button
access on the first screen allows training to start immediately with
practice cases, saving instruction on user login until later, which is
very useful if the phones don’t yet have SIMs or GPRS access.

Derek

On 6/30/11, Drew Roos droos@dimagi.com wrote:

i like changing the colors in chatterbox

On Thu, Jun 30, 2011 at 2:07 PM, Clayton Sims csims@dimagi.com wrote:

I like the idea (for non-commcare-sense deployments) of possibly doing
away
with “Send now/send later” and just trying to send the form best-effort
(and
delete it if it fails to send), replacing the screen with something like

“In demo mode, forms are submitted automatically”

as Nick suggests. Maybe that screen looking different would act as a
good

affordance that the user isn’t in normal CommCare mode.

-Clayton

On Thu, Jun 30, 2011 at 2:02 PM, Nick Amland namland@dimagi.com wrote:

Hey,

Interesting discussion because I, myself, have had similar concerns.

Right before going into “demo” mode, CC does show a rather lengthy
disclaimer basically saying that "you are entering demo mode ".
Though,

this may not be sufficient for our low-literacy or poor eye sight users
which may have trouble reading and/or understanding the text. It would
be
potentially useful if an automatic audio message could be feasible for
this
"disclaimer message".

To Brian’s suggestion, I think that submitting data in demo mode is
actually useful. During a practice periods post-training, it’s been
helpful
to verify that users are actually practicing via CCHQ. If not, then we
know
there needs to be follow-up.

Just throwing out another idea, what if the current “You’ve completed a
form” message could be different when in demo mode and say “You’ve
completed
a form in DEMO MODE”. It’s hard to determine how closely users
actually

look at this screen.

Thanks,
Nick

Nick P. Amland

CommCare Field Fellow
Dimagi, Inc.
Dodoma, Tanzania
Google Voice: 253.642.7790
TZ Mobile: +255 762 740 996
Email: namland@dimagi.com namland08@gmail.com

On Thu, Jun 30, 2011 at 8:18 PM, Brian DeRenzi <bderenzi@gmail.com wrote:

Hi Jon,

This might be a totally reasonable thing to do, but I would have some
concern of pushing the problem the other direction. By essentially
hiding the demo login, it becomes difficult to practice, so then
"fake"/practice data will likely end up coming from the login.

Playing off of a subtle point you made, I like the idea of limiting
functionality when you are in demo mode. What about a message at the
end of a form saying “this data will not be sent. if it is real data,
please login with your username/password” (or something to that
effect). Changing colors and inserting other warnings onscreen (e.g.
maybe a bar at the top of the chatterbox that says “Mazoezi!” or
something) might be another good way to remind users that they are in
demo mode.

Anyway, I definitely agree this is a problem and I’m interested to
hear what others on the list think about how to best to address it.

Brian

On Thu, Jun 30, 2011 at 1:26 AM, Jonathan Payne paynejd@gmail.com wrote:

Hi all,
I want to start a discussion about moving the “demo” user button
into

the

“options” menu on the CommCare Client’s login screen. The reasoning:
it’s
too easy to login as demo, esp. in a region like Tanzania when the
barrier
to entering uid and pwd is quite high (people don’t like it, aren’t
used to
it, might need to look up their credentials, etc.). User’s also
experience
no consequences for selecting demo user: there are no warnings that
the
data
is treated differently and the application isn’t limited in
functionality at
all. I think a good near-term solution to this is to make the
standard

login

seem like the default by moving demo into the options menu. What do
you
think?
Jon


Sent from my mobile device


Regards

Rahul Dhar

9872874932

Nick/Clayton,

I think this was said already, but just to be clear:

I do think that actually submitting demo data to the server is useful,
as Nick points out. What I had in mind (but did not articulate) was
that demo mode would still be sent automatically. This suggestion is
different than Clayton’s where we say ‘data is sent automatically in
demo mode’

It’s kind of a dirty trick to lie to users like that, but I think
everyone wins. We still get data and they think that data isn’t being
sent, so they’re more motivated to actually to figure out how to
login. At least with my experience in TZ, people were concerned and
focused on making sure their data was sent successfully.

I think the more visual cues in chatterbox the better too. We want to
trigger the “something isn’t right” sense in people. That said, I
think it does introduce a challenge for training. If you spend all
your time working in demo mode during training, then the actual login
is going to trigger the “something isn’t right” feeling.

Brian

··· On Thu, Jun 30, 2011 at 10:03 PM, rahul dhar wrote: > yes.........even I agree with others.........there is no fun of having a > demo mode forms 2 be sent........it should just > serve the purpose of training for CHW and practice that CHW can do. > > On Fri, Jul 1, 2011 at 12:06 AM, Derek Treatman wrote: >> >> I also like the idea of different colors. Could also make the login >> and demo buttons more distinct by spacing them out, making them >> bigger, and using those respective different colors. >> >> Demo mode is invaluable for training since you can create a set of >> dummy data which can be copied from phone to phone. Having one button >> access on the first screen allows training to start immediately with >> practice cases, saving instruction on user login until later, which is >> very useful if the phones don't yet have SIMs or GPRS access. >> >> Derek >> >> On 6/30/11, Drew Roos wrote: >> > i like changing the colors in chatterbox >> > >> > On Thu, Jun 30, 2011 at 2:07 PM, Clayton Sims wrote: >> > >> >> I like the idea (for non-commcare-sense deployments) of possibly doing >> >> away >> >> with "Send now/send later" and just trying to send the form best-effort >> >> (and >> >> delete it if it fails to send), replacing the screen with something >> >> like >> >> >> >> "In demo mode, forms are submitted automatically" >> >> >> >> as Nick suggests. Maybe that screen looking different would act as a >> >> good >> >> affordance that the user isn't in normal CommCare mode. >> >> >> >> -Clayton >> >> >> >> >> >> On Thu, Jun 30, 2011 at 2:02 PM, Nick Amland wrote: >> >> >> >>> Hey, >> >>> >> >>> Interesting discussion because I, myself, have had similar concerns. >> >>> >> >>> Right before going into "demo" mode, CC does show a rather lengthy >> >>> disclaimer basically saying that "you are entering demo mode ". >> >>> Though, >> >>> this may not be sufficient for our low-literacy or poor eye sight >> >>> users >> >>> which may have trouble reading and/or understanding the text. It >> >>> would >> >>> be >> >>> potentially useful if an automatic audio message could be feasible for >> >>> this >> >>> "disclaimer message". >> >>> >> >>> To Brian's suggestion, I think that submitting data in demo mode is >> >>> actually useful. During a practice periods post-training, it's been >> >>> helpful >> >>> to verify that users are actually practicing via CCHQ. If not, then >> >>> we >> >>> know >> >>> there needs to be follow-up. >> >>> >> >>> Just throwing out another idea, what if the current "You've completed >> >>> a >> >>> form" message could be different when in demo mode and say "You've >> >>> completed >> >>> a form in DEMO MODE". It's hard to determine how closely users >> >>> actually >> >>> look at this screen. >> >>> >> >>> Thanks, >> >>> Nick >> >>> >> >>> Nick P. Amland >> >>> >> >>> CommCare Field Fellow >> >>> Dimagi, Inc. >> >>> Dodoma, Tanzania >> >>> Google Voice: 253.642.7790 >> >>> TZ Mobile: +255 762 740 996 >> >>> Email: namland@dimagi.com >> >>> >> >>> >> >>> >> >>> On Thu, Jun 30, 2011 at 8:18 PM, Brian DeRenzi wrote: >> >>> >> >>>> Hi Jon, >> >>>> >> >>>> This might be a totally reasonable thing to do, but I would have some >> >>>> concern of pushing the problem the other direction. By essentially >> >>>> hiding the demo login, it becomes difficult to practice, so then >> >>>> "fake"/practice data will likely end up coming from the login. >> >>>> >> >>>> Playing off of a subtle point you made, I like the idea of limiting >> >>>> functionality when you are in demo mode. What about a message at the >> >>>> end of a form saying "this data will not be sent. if it is real data, >> >>>> please login with your username/password" (or something to that >> >>>> effect). Changing colors and inserting other warnings onscreen (e.g. >> >>>> maybe a bar at the top of the chatterbox that says "Mazoezi!" or >> >>>> something) might be another good way to remind users that they are in >> >>>> demo mode. >> >>>> >> >>>> Anyway, I definitely agree this is a problem and I'm interested to >> >>>> hear what others on the list think about how to best to address it. >> >>>> >> >>>> Brian >> >>>> >> >>>> >> >>>> On Thu, Jun 30, 2011 at 1:26 AM, Jonathan Payne wrote: >> >>>> > Hi all, >> >>>> > I want to start a discussion about moving the "demo" user button >> >>>> > into >> >>>> the >> >>>> > "options" menu on the CommCare Client's login screen. The >> >>>> > reasoning: >> >>>> it's >> >>>> > too easy to login as demo, esp. in a region like Tanzania when the >> >>>> barrier >> >>>> > to entering uid and pwd is quite high (people don't like it, aren't >> >>>> used to >> >>>> > it, might need to look up their credentials, etc.). User's also >> >>>> experience >> >>>> > no consequences for selecting demo user: there are no warnings that >> >>>> > the >> >>>> data >> >>>> > is treated differently and the application isn't limited in >> >>>> functionality at >> >>>> > all. I think a good near-term solution to this is to make the >> >>>> > standard >> >>>> login >> >>>> > seem like the default by moving demo into the options menu. What do >> >>>> > you >> >>>> > think? >> >>>> > Jon >> >>>> > >> >>>> > >> >>>> > >> >>>> >> >>> >> >>> >> >> >> > >> >> -- >> Sent from my mobile device > > > > -- > Regards > > Rahul Dhar > 9872874932 >