🌎 Eco-tracker


Project Details
COGS 120 project

Team Members
Megan Dinh, Brendan Jew, Tatum Mason

Timeline
9 weeks (Winter 2020)


Overview

Eco-Tracker is an application that allows users to easily track and visualize daily habits to become more eco-friendly.

Developed as part of COGS120 project to design & code an app that uses data to motivate users in achieving a goal.



Problem


Maintaining the motivation to be eco-friendly can be hard

Through several interviews & surveys with students on campus, our group identified that the majority of young adults want to be more environmentally conscious. However, we identified three recurring issues that negatively affected their motivation.


❓ Many don't understand how, or even if, their efforts are making a difference
❓ It's confusing for them to visualize how impactful daily tasks are, such as commuting by bike vs. driving
❓ Many simply don't know what to do to become more eco-friendly

...and current solutions aren't making it easier.

Auditing existing emissions trackers, our team discovered that many were simply estimators that weren't efficient for daily use and did little to motivate an eco-conscious lifestyle.

Most only provided users with rough annual estimates of their total carbon emissions, which is too arbitrary for most users to conceptualize their impact.

ex. This calculator from the EPA doesn’t afford daily tracking and visualization of impact beyond difficult-to-visualize metrics of pounds CO2/year.


Solution


💡 Users need a tangible, adaptive tracker that keeps up with their ever-changing daily lives!


From our interview findings and audit of existing trackers, we recognized that current solutions weren't working because their results were difficult to fully conceptualize and easily track activities that varied day-to-day.

Maintaining motivation while seeing no tangible results is difficult for any goal, but even more so if you don't have an effective way to measure your progress.



Design

Storyboard

To get a better understanding of how Eco-tracker could solve these problems, our team storyboarded daily scenarios where our app can provide users ease in dynamic tracking in an everyday scenario.

This example highlights how many folks who want to be more environmentally friendly can lose their motivation—simply because they have no idea if their efforts make an impact (which Eco-track aims to fix!)

Creating storyboards helped our team synthesize our previous research and findings to envision scenarios of Eco-tracker's dynamic use & how it would address the opportunities from our need finding.

Wireframes & Paper Prototypes

With an understanding of Eco-tracker's design opportunities, our group tested with two paper prototypes that focused on different main functionalities.

Prototype 1

For prototype 1, the main functionality is for the users to add goals and reminders that will help them be more eco-friendly.

In this prototype flow, users join and can scroll through one screen to see their progress on goals, personalized tips, and stats based on their goals.

The highlight of this design is its all-inclusive home page, which houses all pages and promotes the addition of goals/tracking of progress with an “add” button cemented in the bottom corner of the screen.


Prototype 2

For this second prototype, the emphasis is focused more on tracking in general with the optional use of setting goals. As such, compared to the other design, this flow is anchored by visualizations of their day or month eco-footprint.

The primary goal for this prototype was to facilitate quick tracking and understanding of user environmental impact tangibly.

Users can navigate between different pages with the bottom menu bar to log data, view summaries of their data, discover tips to reduce their carbon footprint, create goals, and create a shareable profile.


Figma Prototype

Prototype 2 was chosen to be further developed into a mid-fidelity wireframe as its statistics-focused home page would best support users in developing eco-friendly habits and address the opportunities discovered from our need finding.

The main functionality of this prototype is data logging and viewing summaries of users' daily or monthly emissions to evaluate if they are making a difference. It visualizes the impact that users have so that they can easily recognize trends to make impactful changes.



Testing with Users

Tests were conducted using mobile phone browsers to complete tasks with our coded prototype.

For our initial round of testing, four random users from our main demographic (young, eco-conscious adults) participated. They were given a list of tasks to accomplish, as we observed for any potential pain points or issues. Afterward, they were asked a few questions regarding their overall sentiment of the app, any frustrations/confusing areas, and whether it was effective for them at all.


The results from testing were far from perfect with three general pain points that our testers all experienced.


🚫 Users couldn't understand the signifiers used, such as the summary page and log icons on the navbar.

🚫 Data figures on the summary page were too ambiguous and unmotivating to users, such as “L” for liters of carbon. Users additionally felt anxiety at how much they were wasting rather than saving.

🚫 Users couldn't understand the signifiers used, such as the summary page and log icons on the navbar.
Gestures that our team assumed were natural to do with a cursor didn’t always translate to productive results once we began testing with mobile users.
We organized issues users experienced with the prototype along with usability heuristics.


Updating Prototype

To resolve the majority of issues brought up from testing, our group focused the redesign on the home page, logging interactions, and menu bar.


In our final prototype, our team worked to address the issues brought up from our user testing sessions surrounding unclear signifiers, ambiguous data presentation, & buggy interactions.


Signifier (navbar) Updates

Clarified Data
Increasing Motivation
Easier Logging


Validating Updates

To validate if our new changes were effective, we conducted A/B testing with 152 users.


The participants, sourced by a team member who was a DSGN 1 IA, were randomly assigned either the old or updated versions.

To measure the effectiveness of our changes, we tracked how many users were able to successfully log miles traveled & how long it took them to do so using Google Analytics. We measured success through the metrics of successful task completion and how long the task took.

Of 115 successful task completions, the updated version (/viewAlt) had a higher rate of success 20% more than the original (/commute).

Additionally, (/viewAlt) was also quicker on average to complete than (/commute) by 20 seconds!

Goal completion for /viewAlt (updated ver) was much higher than /commute (previous ver).

In summary, the results validated our updates as there was a statistically higher and faster completion rate of the task than the original version. We considered it a success as more efficient tracking would make it less of a chore for users, encouraging them to continue it as a positive habit!

Not only was there a higher completion rate, but /viewAlt (updated ver) had a quicker time to completion.

You can find a more in-depth write-up of our testing data, analysis, & data figures here!


Reflection

And that's how we created Eco-tracker! From paper prototypes, wireframes, & Figma mockups, our team produced a coded version of Eco-tracker that you can click through!


✅ I learned a lot about managing rapid iteration in design and front-end development.
✅ Converting designs & interactions into functional code is HARD! For my first experience also coding a design, I've learned to appreciate developers who manage to translate complex mockups.
⏩ Given more time & resources, I would love to revisit other features like Goals and increase testing for our other prototype changes.

Thank you to my team for a great learning experience through designing, testing, and coding Eco-tracker



Check out more projects here!



Home