Reducing application complexity for new users

We’re looking for ways to simplify our application for new users, so they
can gain experience using a simpler app for a few weeks/months, before
being ‘upgraded’ to the full version. An image of the main menu of the
‘full’ version is attached. As you can imagine, it can be pretty
overwhelming for new users with very limited technology experience/training.

So far we’ve consider the following approaches:

  1. Developing a ‘lite’ version of an app that includes a subset of
    modules and forms from the ‘full’ version
  2. Somehow hiding certain modules or forms using custom user properties

Approach #1 is not super scalable, as we’d need to remove the ‘lite’
version of the app and install the ‘full’ version of the app.

Approach #2 is not yet technical possible, although it currently has 43
votes in uservoice
https://dimagi.uservoice.com/forums/194738-app-builder/suggestions/5790651-conditionally-linking-from-the-end-of-one-form-to
.

My question is: does anyone have any ideas/suggestions for how to support
different ‘modes’ of a single application, where modes can be switched at
runtime (e.g. using custom user properties)?
[or, for Dimagi, any ETA for when the requested feature may be available?]

Thanks, Ray

Sorry, I linked to the wrong uservoice item. Here is the correct link
https://dimagi.uservoice.com/forums/194738-app-builder/suggestions/5654502-enable-filtering-on-modules-or-non-case-forms
(Enable filtering on modules or non-case forms). (happy for other
people to vote for it too!)

Also, as an additional idea: if modules could be automatically hidden when
there are no open cases of the case type associated with the module, that
would possibly address this use case and also allow the main menu to
’auto-adjust’. Currently, the user ends up at an empty case list when
opening a module without any cases matching the filter critera, which is
confusion. I suppose a ‘no data available’ message could be helpful.

Ray

··· On Wednesday, March 4, 2015 at 10:08:22 AM UTC-5, Ray Brunsting wrote: > > We're looking for ways to simplify our application for new users, so they > can gain experience using a simpler app for a few weeks/months, before > being 'upgraded' to the full version. An image of the main menu of the > 'full' version is attached. As you can imagine, it can be pretty > overwhelming for new users with very limited technology experience/training. > > So far we've consider the following approaches: > > 1. Developing a 'lite' version of an app that includes a subset of > modules and forms from the 'full' version > 2. Somehow hiding certain modules or forms using custom user properties > > Approach #1 is not super scalable, as we'd need to remove the 'lite' > version of the app and install the 'full' version of the app. > > Approach #2 is not yet technical possible, although it currently has 43 > votes in uservoice > > . > > My question is: does anyone have any ideas/suggestions for how to support > different 'modes' of a single application, where modes can be switched at > runtime (e.g. using custom user properties)? > [or, for Dimagi, any ETA for when the requested feature may be available?] > > Thanks, Ray >

Hi Ray,

Module display conditions are currently on our roadmap for the next version
of CommCare mobile (2.20). We are planning to enable module display
conditions based on custom user data, though are still evaluating whether
display conditions for non-case forms will be part of that effort as well.

We are currently planning to release CommCare 2.20 in the next two months.
Feel free to check back in on the status of this feature if that will help
you plan your new user application rollout!

Thanks,
Amelia

··· On Wed, Mar 4, 2015 at 10:53 AM, Ray Brunsting wrote:

Sorry, I linked to the wrong uservoice item. Here is the correct link
https://dimagi.uservoice.com/forums/194738-app-builder/suggestions/5654502-enable-filtering-on-modules-or-non-case-forms
(Enable filtering on modules or non-case forms). (happy for other
people to vote for it too!)

Also, as an additional idea: if modules could be automatically hidden when
there are no open cases of the case type associated with the module, that
would possibly address this use case and also allow the main menu to
’auto-adjust’. Currently, the user ends up at an empty case list when
opening a module without any cases matching the filter critera, which is
confusion. I suppose a ‘no data available’ message could be helpful.

Ray

On Wednesday, March 4, 2015 at 10:08:22 AM UTC-5, Ray Brunsting wrote:

We’re looking for ways to simplify our application for new users, so they
can gain experience using a simpler app for a few weeks/months, before
being ‘upgraded’ to the full version. An image of the main menu of the
’full’ version is attached. As you can imagine, it can be pretty
overwhelming for new users with very limited technology experience/training.

So far we’ve consider the following approaches:

  1. Developing a ‘lite’ version of an app that includes a subset of
    modules and forms from the ‘full’ version
  2. Somehow hiding certain modules or forms using custom user
    properties

Approach #1 is not super scalable, as we’d need to remove the 'lite’
version of the app and install the ‘full’ version of the app.

Approach #2 is not yet technical possible, although it currently has 43
votes in uservoice
https://dimagi.uservoice.com/forums/194738-app-builder/suggestions/5790651-conditionally-linking-from-the-end-of-one-form-to
.

My question is: does anyone have any ideas/suggestions for how to support
different ‘modes’ of a single application, where modes can be switched at
runtime (e.g. using custom user properties)?
[or, for Dimagi, any ETA for when the requested feature may be available?]

Thanks, Ray


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hi Amelia.
Module display conditions based on custom user data would support our
intentions. Happy to hear that it’s coming!
Thanks, Ray

··· On Wed, Mar 4, 2015 at 12:14 PM, Amelia Sagoff wrote:

Hi Ray,

Module display conditions are currently on our roadmap for the next
version of CommCare mobile (2.20). We are planning to enable module display
conditions based on custom user data, though are still evaluating whether
display conditions for non-case forms will be part of that effort as well.

We are currently planning to release CommCare 2.20 in the next two months.
Feel free to check back in on the status of this feature if that will help
you plan your new user application rollout!

Thanks,
Amelia

On Wed, Mar 4, 2015 at 10:53 AM, Ray Brunsting ray@tula.org wrote:

Sorry, I linked to the wrong uservoice item. Here is the correct link
https://dimagi.uservoice.com/forums/194738-app-builder/suggestions/5654502-enable-filtering-on-modules-or-non-case-forms
(Enable filtering on modules or non-case forms). (happy for other
people to vote for it too!)

Also, as an additional idea: if modules could be automatically hidden
when there are no open cases of the case type associated with the module,
that would possibly address this use case and also allow the main menu to
’auto-adjust’. Currently, the user ends up at an empty case list when
opening a module without any cases matching the filter critera, which is
confusion. I suppose a ‘no data available’ message could be helpful.

Ray

On Wednesday, March 4, 2015 at 10:08:22 AM UTC-5, Ray Brunsting wrote:

We’re looking for ways to simplify our application for new users, so
they can gain experience using a simpler app for a few weeks/months, before
being ‘upgraded’ to the full version. An image of the main menu of the
’full’ version is attached. As you can imagine, it can be pretty
overwhelming for new users with very limited technology experience/training.

So far we’ve consider the following approaches:

  1. Developing a ‘lite’ version of an app that includes a subset of
    modules and forms from the ‘full’ version
  2. Somehow hiding certain modules or forms using custom user
    properties

Approach #1 is not super scalable, as we’d need to remove the 'lite’
version of the app and install the ‘full’ version of the app.

Approach #2 is not yet technical possible, although it currently has 43
votes in uservoice
https://dimagi.uservoice.com/forums/194738-app-builder/suggestions/5790651-conditionally-linking-from-the-end-of-one-form-to
.

My question is: does anyone have any ideas/suggestions for how to
support different ‘modes’ of a single application, where modes can be
switched at runtime (e.g. using custom user properties)?
[or, for Dimagi, any ETA for when the requested feature may be
available?]

Thanks, Ray


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Ray Brunsting, CTO, Tula Foundation / tula.org