![](https://static.wixstatic.com/media/7993a2_494aa20dadb041bea682269ffb7f25b4~mv2.png/v1/fill/w_1223,h_1920,al_c,q_95,usm_0.66_1.00_0.01,enc_auto/7993a2_494aa20dadb041bea682269ffb7f25b4~mv2.png)
![blog-header-001522-scaled.jpg](https://static.wixstatic.com/media/7993a2_28650893ce51410bb4bf084a2ab6d63e~mv2.jpg/v1/fill/w_645,h_430,al_c,q_80,usm_0.66_1.00_0.01,enc_auto/7993a2_28650893ce51410bb4bf084a2ab6d63e~mv2.jpg)
![](https://static.wixstatic.com/media/7993a2_528ba567788d4800aab32a650e7390ad~mv2.jpg/v1/fill/w_619,h_162,al_c,q_80,usm_0.66_1.00_0.01,enc_auto/7993a2_528ba567788d4800aab32a650e7390ad~mv2.jpg)
MOULTRIE MOBILE
Throughout my summer at Moultrie Mobile, I worked on a UX research study for a core app feature, and prototyped camera sharing feature.
ROLE
UX Intern
CLIENT
Moultrie Mobile
DURATION
June 2023 - Aug 2023
SUMMARY
While working at Moultrie Mobile, I learned from fellow UX Designers and a Product Manager that there’s one issue that’s been bugging them for a while: the app's device settings page.
Moultrie Mobile offers a monthly subscription-based service, where users on a plan can remotely access photos and video from their cellular cameras through their phone app.
The app’s device settings page enables users to control camera behavior, such as adjusting PIR (Passive Infrared sensor) sensitivity, upload frequency, and photo detection delay.
Device settings is central to the app's user experience, frequently being the root cause of unfavorable App Store reviews that cite issues such as cameras draining battery, receiving too many photos, not seeing the photos after the camera takes them, etc.
![Frame (1).png](https://static.wixstatic.com/media/7993a2_c230632ce12c46599c968ebc57f0688d~mv2.png/v1/fill/w_99,h_91,al_c,q_85,usm_0.66_1.00_0.01,enc_auto/Frame%20(1).png)
![IMG_1222FE4F633E-1.jpeg](https://static.wixstatic.com/media/7993a2_c4c8467899ca48a98d754a03abb61150~mv2.jpeg/v1/fill/w_266,h_192,al_c,q_80,usm_0.66_1.00_0.01,enc_auto/IMG_1222FE4F633E-1.jpeg)
UPLOAD FREQUENCY CONFUSION
![IMG_6533.jpg](https://static.wixstatic.com/media/7993a2_24d4bea3d1f14d148b8abfbac156dbb9~mv2.jpg/v1/fill/w_285,h_192,al_c,q_80,usm_0.66_1.00_0.01,enc_auto/IMG_6533.jpg)
RESEARCH GOAL
I devised a research plan to assess users' understanding of camera settings and how these settings impact battery and image capture — aiming at identifying effective strategies to enhance the user experience and address any shortcomings in the camera settings page.
1
How users determine their camera settings
3
Uncover the pain points users ecnountered
2
Assess user's understanding of Settings terminologies
4
Assess the information architecture of the settings page according to user prioritization
METHOD & RESULT
We send out 500 emails to a selected list of existing users, specifically those who recently called customer service for settings problems. I created recruitment emails, the studies were conducted remotely through Microsoft Teams.
The study was a directed story telling session followed by semi-formal interview. Participants were asked to recount the last time they had trouble with device settings page. They were also asked to give their best definition for terminologies on the existing interface.
I conducted 10 directed storytelling sessions over two weeks.
65%
of participants had an inaccurate definition for terminologies like motion detection and PIR settings
70%
of participants would like recommended settings as a reference point to aid their decision-making.
60%
of participants can self-identify as wanting to optimize based on: minimize data usage
An overwhelming majority of participants mentioned trial and error as how they currently learned about what each setting does.
HOW CURRENT USERS
LEARN ABOUT SETTINGS
1
Trial and Error
"I learned how they work by just playing around with it and looking at the settings." -- P5
2
Moultrie Mobile Website
"I look at device manual and online resources to learn about how these work" -- P3
3
Youtube/other online resources
"I occasionally do a google search on features and how they work" -- P7
4
Device Manuals
AFFINITY DIAGRAM
![Screenshot 2023-10-22 at 11.36.43 PM.png](https://static.wixstatic.com/media/7993a2_df04fae47ca94b70be81cecab2b8f316~mv2.png/v1/fill/w_1198,h_532,al_c,q_90,usm_0.66_1.00_0.01,enc_auto/Screenshot%202023-10-22%20at%2011_36_43%20PM.png)
FEATURE SUGGESTIONS
I pitched two feature suggestions to a room of product managers and senior developers.
#1. Incorporating tips to give user available information within the settings page. In addition, Moultrie Mobile website should include
season-based tips.
![Smart Capture - All Activity (3).png](https://static.wixstatic.com/media/7993a2_77a2c742448448538375799d29418a1b~mv2.png/v1/fill/w_277,h_600,al_c,q_85,enc_auto/Smart%20Capture%20-%20All%20Activity%20(3).png)
![Season Based Tooltip.png](https://static.wixstatic.com/media/7993a2_2148452a04f344ff9f5e4dd18ba6f57b~mv2.png/v1/fill/w_162,h_137,al_c,q_85,usm_0.66_1.00_0.01,enc_auto/Season%20Based%20Tooltip.png)
![Current Tips.png](https://static.wixstatic.com/media/7993a2_7186d43145d1414a926a0c1b86057c16~mv2.png/v1/fill/w_167,h_600,al_c,q_85,enc_auto/Current%20Tips.png)
#2 Created preset settings according to optimization preferences identified through the research.
![Smart Capture - All Activity (2).png](https://static.wixstatic.com/media/7993a2_c9f94f0684cb4adf89d3d5e94f0c810a~mv2.png/v1/fill/w_277,h_600,al_c,q_85,enc_auto/Smart%20Capture%20-%20All%20Activity%20(2).png)
![Smart Capture - All Activity.png](https://static.wixstatic.com/media/7993a2_f9ccbdce5ece424e962472e8407e51e7~mv2.png/v1/fill/w_277,h_600,al_c,q_85,enc_auto/Smart%20Capture%20-%20All%20Activity.png)
Leading the research process from start to finish was a fun and challenging experience.
Through talking with participants I learned core user's goals that helps me to put their thoughts in context of their larger goals, like monitoring property.
Considering naming conventions from the user's perspective is crucial.
Working with a relatively older user group, improving legibility and ensuring the ease of navigation are both important. I would anticipate the process of refining terminology continues to be a relevant problem, and the current naming convention of terminologies can be methodically assessed through Maze tests.
TAKEAWAYS
![unnamed (2).gif](https://static.wixstatic.com/media/7993a2_93ef69ee58c9422585a5011e320e861b~mv2.gif)
PROJECT II
CAMERA SHARING
SUMMARY
While working at Moultrie Mobile, I was responsible for prototyping camera sharing, a beta MVP feature. Users can select cameras and share that camera’s images with additional Moultrie Mobile users.
Sharing a camera’s images has been requested of Moultrie Mobile repeatedly for years. Competitors enable sharing in various forms.
PRELIMINARY RESEARCH
We conducted a preliminary study to learn the reality of account sharing. Sharing gallery would lose its value if users were comfortable with simply their account and passwords with friends and family.
Result shows that sharing with friends can be a problem as Moultrie Mobile accounts often contain sensitive information such as bank cards.
We talked to 3 expert users and initiated a meeting with a room of developers to the feasibility of what could be achieved.
![image 1.png](https://static.wixstatic.com/media/7993a2_bd7c114ddcca43afbe16a7c823ad8568~mv2.png/v1/fill/w_984,h_466,al_c,q_90,usm_0.66_1.00_0.01,enc_auto/image%201.png)
LO-FI WIREFRAMES
The task flow help us scope the project with MVP requirements in mind.
I was responsible for prototyping the gallery sharing flow (shown below), while another UX designer on the team was responsible for gallery view.
![image 2.png](https://static.wixstatic.com/media/7993a2_265bb8f1f8c648d697c6d49d78040c1f~mv2.png/v1/crop/x_473,y_0,w_3623,h_1768/fill/w_1334,h_651,al_c,q_90,usm_0.66_1.00_0.01,enc_auto/image%202.png)
I then recreated icons and additional UI elements for the camera-sharing page to ensure all the new components were in line with the existing design system.
![Component 3 (2).png](https://static.wixstatic.com/media/7993a2_3c6c9b96206b4ab89e876064e333aef7~mv2.png/v1/fill/w_599,h_428,al_c,q_85,usm_0.66_1.00_0.01,enc_auto/Component%203%20(2).png)
After using a couple internal design jams to gather feedback and make revisions, I translated the screens to high-fidelity designs.
HIGH FIDELITY DESIGN
USER FIND CAMERA SHARING FEATURE ON ACCOUNT PAGE
![Account Page.png](https://static.wixstatic.com/media/7993a2_4876b43ee58142118e795c8d64d4528f~mv2.png/v1/fill/w_277,h_599,al_c,q_85,usm_0.66_1.00_0.01,enc_auto/Account%20Page.png)
USER CAN VIEW LIST AND ADD A NEW GUEST
![Future Proof Guest.png](https://static.wixstatic.com/media/7993a2_8e721894572d41ad9a2c97cfae7b34be~mv2.png/v1/fill/w_277,h_599,al_c,q_85,usm_0.66_1.00_0.01,enc_auto/Future%20Proof%20Guest.png)
ADD NEW GUEST - SHARED CAMERA SELECTION
![First Time Sharing-3.png](https://static.wixstatic.com/media/7993a2_856c113101634ab0a95e82cf2f86ff44~mv2.png/v1/fill/w_277,h_599,al_c,q_85,usm_0.66_1.00_0.01,enc_auto/First%20Time%20Sharing-3.png)
SHARED CAMERA SELECTION
![First Time Sharing-4.png](https://static.wixstatic.com/media/7993a2_b7ceb609555f4050968bab5f175950df~mv2.png/v1/fill/w_277,h_599,al_c,q_85,usm_0.66_1.00_0.01,enc_auto/First%20Time%20Sharing-4.png)
ADD NEW GUEST - ENTER GUEST EMAIL
![First Time Sharing-1.png](https://static.wixstatic.com/media/7993a2_b14bfe9bb07e4e7aa170b82fb67e4e7f~mv2.png/v1/fill/w_277,h_599,al_c,q_85,usm_0.66_1.00_0.01,enc_auto/First%20Time%20Sharing-1.png)
SUCCESS
![First Time Sharing-2.png](https://static.wixstatic.com/media/7993a2_357a5192be8e46b8adcc5f15cdd56bb5~mv2.png/v1/fill/w_277,h_599,al_c,q_85,usm_0.66_1.00_0.01,enc_auto/First%20Time%20Sharing-2.png)
VIEW SHARED WITH ME
![Future Proof Guest-1.png](https://static.wixstatic.com/media/7993a2_1fa4817dc7b147fda880b04a832c9eee~mv2.png/v1/fill/w_277,h_599,al_c,q_85,usm_0.66_1.00_0.01,enc_auto/Future%20Proof%20Guest-1.png)
TAKEAWAYS
Anticipating the future use case of specific components can be challenging. Especially when new design concepts create new scenarios that might not align with the conventional or anticipated usage patterns. Oftentimes I would come to an idea and realize, oh that would be a new component that we don't yet have.
To address this, the practice of documenting edge case additions becomes important. Having documentation allows designers and developers to proactively prepare for unforeseen challenges.
DOCUMENTED THE SNACK BAR COMPONENT
![unnamed (1).gif](https://static.wixstatic.com/media/7993a2_16c9edf7fa9742a59d9b8a0bc5325a2c~mv2.gif)