MACROINVERTEBRATES.ORG
  • PROJECT
  • PEOPLE
  • PRODUCTS
  • Blog
  • Resources
    • Help
    • FAQ

Web App Development for Macroinvertebrates.org

8/28/2020

 
by Chelsea Aci and Ziqi Dong
This summer we began development of an innovative open educational resource with the aim of making the task of learning to identify macronvertebrates easier and more engaging by developing a new kind of tool for guiding scientific observation and inquiry.  The goal is to release a mobile version of Macroinvertebreates.org optimized for field use in low-no wifi conditions, and which supports learning to identify aquatic insects and water quality assessments. 

Watch a video demo'ing our prototype with supporting documentation. 

Mobile App Pt. III: Usability Testing, Iterations and Changes

8/20/2020

 
By Estelle Jiang and Alice Fang

🐞📱

Moving to a higher fidelity prototype by following the design system. 
After showing our low-fidelity prototype to the entire team and developers, we decided to move forward by applying a more detailed design and developing the visual + design system. We also figured out how to showcase the relationship between orders, family and genius on the mobile application, and the UI components for each type of 'page'. It was one of the biggest challenges we met previously. 

For the color theme, we followed the guidelines the project used on the website and applied the blue color to highlight actionable parts. To keep the app clean and concise, we used white for the major user interface design. As for the typography, the body font is Nunito Sans and the title font is Roboto Slab. Due to limitations with the database information, and in an effort to bring about the features of the specimen in photography, we also worked with the gigapan background color, creating a floating, borderless 'under a microscope' look [see image on the right].
Picture
Picture
Changes we made for the high fidelity prototype after discussion: 
Picture

Homepage - We thought the card view can be bigger to attract people’s attention and intrigue their interest. Since we only have 10 orders, we did not have too many concerns about accessibility at the very beginning. The ID key button is also replaced on the home page. 

The dropdown menu was also changed to help user easily navigate and get back to main page.


Picture

​We also added icons to explain the functionalities and applied color for the side menu to make it stand out more. As we mentioned on the previous post, we were struggling between a button to expand, and swiping up. Since we were worried about the experience of swiping up which is too hidden on the bottom of the screen. we iterated and created a button on the bottom for accessibility instead.
Planning and preparing first round usability testing
To conduct our first round of testing, we started with writing the testing protocol, thinking about the purpose of the testing and the goals we want to achieve. 

The purpose of our testing was to test the logic of the user flows, and to identify potential navigation and usability issues. We wanted to understand if the application is engaging to users, and is useful in identifying macroinvertebrates and learning their characteristics. 

We assigned a few small tasks for users to finish during the testing: 
Pre-task: Users will be given 30 seconds to get familiar with the application before doing task. 

First task: Users are asked to browse the different orders though different ways. This way, we can then tell whether the design makes sense, and take note of how users navigate through the different levels of information.  

Second task: This task was focused on the detailed Order & Family page designs, users are asked to find out more detailed order and family information, as well as specific diagnostic characters for a specific family. By asking the users how difficult the task is, we can evaluate the slider design idea we had, and how accessible / noticeable the actionable button is. 

We also asked additional questions at the end of testing to check whether they can have a clear understanding about our application throughout the testing process, including:
  1. Any challenges or issues you want to highlight? 
  2. Any opportunities areas we should consider?
  3. If you were going to tell a friend / colleague about this app what would you say?
Synthesize the findings to guide our next iterations.
Overall, we conducted five user interviews, with macroinvertebrate experts, people familiar with the site, and a novice user; I also got feedback from my friend who knew nothing about the concept or field in order to get additional novice learner’s insights.  
​

Rather than use the normal user research method - affinity diagramming to synthesize the testing findings, Alice made the excel sheet to list out the key points the interviewee made for each task. It helped us highlight the common suggestions and feedback. 
Picture
Here are the findings that guided our next iterations:
  • There is a difference between experts’ needs and novice learners’ needs. The user experience of the application needs to cater the needs of both parties. Experts want to quickly access the specific order/family information but novice learners want to understand the relationship and be guided to learn. 
  • Although the card looks nice, the homepage is not accessible and it’s hard to guess the usage of the application by looking at the homepage. 
  • Users did not expect to find more information from the bottom button and it will take an extra step to access. 
  • The dropdown menu can help them easily navigate within orders and families; although different users navigated the app in different ways, including the drop-down and the hamburger menu; no one selected the back button.
  • There was also a slight gap between ages of users and expectations with swiping through different pages.
Iterations we made.
Since the first version of high fidelity prototypes are hard for novice learners to learn and understand the additional information, I quickly brainstormed two other versions to display the information and hierarchy between orders and families. 
Picture
The first version allows users to swipe and learn along the way. The experience is more immersive and easy to follow if the users have no idea about the insect and the order. However, it doesn’t give enough freedom and choices for users to explore themselves, and quickly becomes repetitive for more experienced users. 

Picture
The second version can cater the needs of both experienced users and novice learners since it allows them to quickly switch between various levels of information. The structure of the insects are also easy to tell and discover. The homepage was also iterated from showing only one order to display multiple orders at once. 

The developers moved forward with this version, and worked to develop a beta version. It was interesting and difficult figuring out how to work in parallel; they were focused on setting up the database and structure, while we were iterating through the designs, but we couldn't progress too far or change too many things after they began developing the pages.


Mobile App Pt. II: New Team, New Ideas!

8/12/2020

 
By Alice Fang

🐞📱

Re-framing with a new team!
Chelsea and I were joined by Estelle (Yi Cheng) Jiang and Dakota (Zi Qi) Dong in late May. Moving forward, Chelsea and Dakota will be working on development, while Estelle and I will be working on the design and user-testing of the app. There was an adjustment period as we introduced the project to the new members and got everyone acquainted while figuring out how to work collaboratively in a remote wfh environment. 

Through this process, we've been utilizing google docs and spreadsheets, as well as Figma, but coordinating between design and development has been tricky. Accommodating and synching the design and development timelines was difficult, and it was a bit touch-and-go.
Spreadsheets and Organizing Data
Previously, I struggled with establishing a structure to the app that allowed for navigation in and out of orders/families. To make the taxonomy clear (as we are non-scientists and non-bug experts), and to organize the information for design purposes, I created a spreadsheet with the following:​
Picture
1. Inventory of functions that exist on the website​
In order to figure out the minimum viable product that can be developed by students within a summer, and to compare what needs to change from Order to Family, I listed all of the functions for Order/Family/Genus.
Picture
 2. List of insect orders, the families in each order, and the number of specimen (genera) in each family, and the number of diagnostic characters for each family and order 

While many of the families have similar numbers of specimen, there were a lot of outlier cases we needed to keep an eye on, and account for while designing. The length of names, both common and scientific, impacts the typographic system, and the number of diagnostic characters affects how we visually set up that information. Some of the cases are as follows:
  • Greatest number of diagnostic characters in a family is 8 (most families range 2-4)
  • In comparison, the range of Order diagnostic characters is 1–3
  • Longest scientific name: Polycentropodidae
  • Shortest scientific name: Dixidae
  • Longest common name: Broad-Shouldered Water Striders, Shortlegged Water Striders, Riffle Bugs
  • Shortest common name: Darners​

*Dev team has to set up the database (I don’t know the exact details). We ran into a challenge late in the summer [early August] where the Gigapan database had to be moved, and there was no way to extract some of the family traits and text information, requiring manual copy and pasting
Collecting References and Resources for Ideation Round II
Getting the design team on the same page.

I showed Estelle the previous mockups and ideas that I had for the mobile app, but in order to refresh and sort of create a mutual visual language, we took the time to research and look at other apps. We compared and discussed field guide apps, quiz apps, and other text-based apps like news/media.
Picture
Estelle's feedback + insights
Picture
Picture
*Referencing Headspace, AirBnB, Medium, WWF Together
Alice’s Points:
  • Organizing info: list vs. grid (text vs. image)
  • Switching back from family to order (internal navigation)
  • Making clear important areas of app (use as field guide) and what information to highlight (ie. pollution tolerance vs. life history; diagnostic characters as learning tool)​
Picture
*Referencing Twitter, Google Maps, Medium Merlin ID, Audubon
Lo-fi Version 2
New Ideas and Changes

Estelle quickly mocked some basic page structures, and documented user stories. This allowed us to see possible entry points and user profiles for the app. What are possible ways people would use the app? What would they be looking for? And how do we prioritize that development at the same time?
Picture
User Stories
Picture
She also created this flow diagram of entry in the app and access points to different functions; however, it didn't include navigation and returning to previous pages, or other major functions we hope to implement in the future, like a quiz.
Picture
Home Page and Order Page Templates that Estelle created
  • High level navigation → broad view of orders with the drop-down menu!
  • Actually designing a home page! :-) that is visually interesting and hopefully incites curiosity
Picture
Scroll-up Popup for additional information, as well as an 'introduction' to the Order Page
Picture
Picture
*Comparing what a bottom pop-up that scrolls up, and a button on the bottom, would look like.

Between a button to expand, and swiping up, we originally decided on a swiping up action, but were worried about the screen experience that it would be too hidden on the bottom of the screen. As we moved into user testing, we created a button on the bottom for accessibility instead. It stood out more, and for someone holding a phone, was located in a position that was easy to access.
Picture
Through this process, we also started to get into the look and feel of the application. As the focus and beauty of the collection is the high definition images and close-up thumbnails, I really wanted typography to play a role in the visual style while staying close to what the desktop site looks like.

Mobile App Pt. I: Beginning a Mobile Macroinvertebrates.org!

5/25/2020

 
by Alice Fang
🐞📱
A little after spring break, Chelsea and I started on conceptualizing and developing a mobile app version of Macroinvertebrates.org, which we will continue to work on into the summer.
​

The original question we started with was what should the app do? (and what can we do to create a minimum viable product as a 2 person group?) The primary functions of the site that could be reflected in a mobile app were:
  • ID Key
  • Traits/Characteristics
  • Practice Quiz

Primary Goals for mobile: learning orders! and providing access when you don't have internet connectivity (creating a lighter weight, downloadable version)

A mobile version of the ID Key was already prototyped by Jaclyn last year, so the majority of the focus will be working on integrating Order and Family level information. Based on how far concept/prototyping goes, we may also integrate a practice quiz as well.
Picture
Different ways of showing 'additional information'
The first issue we ran into while refining the ID Key was the number of cases that the original design couldn’t accommodate for. For example, in the ID Key on the site, there were a few questions that examined/compared two different physiological traits ("wings OR wing pads", instead of just "wings"). How could the gallery of characteristics show images of both, and how should the help button appear to show both text explanations as well? 

This was the first (and definitely not the last) time where I struggled designing for mobile, instead of desktop or 'website on mobile.' I don't have much experience in designing a purely mobile app product, so I'm excited for the challenge and learning experience.

​Areas that need resolving as we move forward!:

  • Level of detail/information? Order to Family; genus is too specific, but how to show family-level information without genus? 
  • Information architecture
  • Working on mobile flow and interaction
​
Looking at Mobile Interactions
Picture
Google Maps|Twitter|Medium
​I took note of some common features of mobile apps to help structure our app as well. These are some references that could help with structure/organization.
​
  • Menu bar on the bottom of the screen, to direct to different functions of the app. Trying to incorporate this to separate viewing the images of the specimen from diagnostic characteristics and order/family overview. [consistent on many mobile apps]
  • How to display diagnostic characters + additional information? Is the bottom bar the way to go, or should the information overlay on top of the actual images? [Google Maps]
  • High-level menu from the left of the screen, to lead back to the ID Key, or a menu of just insect orders (see all the orders at once). [Twitter]​​
  • Scrolling down to see more content (eg. families in an order) and scrolling horizontally to see within the content (eg. genura within a family) [Medium]

​
Organization + Hierarchy
Picture
Trying to figure out how everything fits together
Once a user selects an order, the organization from Order > Family > Zoomable Image (Genus) becomes a little confusing. Should the user be able to select into a family page (option 1) or does it lead directly to the zoomable image? At what level is family-specific information displayed then?

*We established early on that Genus-level information was probably too specific for mobile, trying to keep the app more general
Picture
High-Level Menu
Picture
Bottom bar; popup additional information?

    Project Team

    An interdisciplinary team
    ​of entomologists, learning scientists, software engineers and designers collaborating to improve macroinvertebrate identification training and technologies with volunteer biomonitoring organizations.

    Categories

    All
    Broader Impacts
    By Clemson
    By CMU
    By Educators
    By Powdermill
    By Stroud
    Design Studies
    Educator Innovations
    Entomology
    Imaging
    Learning Research
    Mobile App
    NSF REU
    User Research

    Archives

    January 2021
    December 2020
    September 2020
    August 2020
    July 2020
    May 2020
    November 2019
    August 2019
    July 2019
    June 2019
    May 2019
    April 2019
    March 2019
    February 2019
    January 2019
    October 2018
    September 2018
    August 2018
    June 2018
    May 2018
    March 2018
    December 2017
    August 2017
    June 2017
    May 2017
    April 2017
    March 2017
    December 2016
    November 2016
    October 2016
    September 2016
    August 2016
    July 2016
    June 2016
    May 2016
    April 2016
    March 2016

    RSS Feed

Project INFO

ABOUT
www.ept.macroinvertebrates.org
NSF Award  Listing

Partners

Learning Media Design Center@CMU
CREATE Lab @CMU
​
Clemson University 
Stroud Water Research Center
Carnegie Museum of Natural History

Collaborators

ALLARM
MD Streamwaders
Senior Environmental Corp
Pittsburgh Parks Conservancy

Trout Unlimited
Picture
This material is based upon work supported by the National Science Foundation under Grant #1623969.
Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of NSF. ​​

  • PROJECT
  • PEOPLE
  • PRODUCTS
  • Blog
  • Resources
    • Help
    • FAQ