Preset saver

Challenge

Preset saver is a mobile camera feature that gives its users the option to create and save custom camera configurations as templates.

Impact

  • Maze

  • Figma

  • Recorder

  • Google Forms

  • Google Docs

Role(s)

Salaudeen Ridhwan

Product designer, UX researcher.

Contributions

  • User interview results

  • User flow

  • Task flows

  • Low fidelity

  • High fidelity design

  • Design insights

Preset saver

Challenge

Preset saver is a mobile camera feature that gives its users the option to create and save custom camera configurations as templates.

Impact

  • Maze

  • Figma

  • Recorder

  • Google Forms

  • Google Docs

Role(s)

Salaudeen Ridhwan

Product designer, UX researcher.

Contributions

  • User interview results

  • User flow

  • Task flows

  • Low fidelity

  • High fidelity design

  • Design insights

Preset saver

Challenge

Preset saver is a mobile camera feature that gives its users the option to create and save custom camera configurations as templates.

Impact

  • Maze

  • Figma

  • Recorder

  • Google Forms

  • Google Docs

Role(s)

Salaudeen Ridhwan

Product designer, UX researcher.

Contributions

  • User interview results

  • User flow

  • Task flows

  • Low fidelity

  • High fidelity design

  • Design insights

View preset saver prototype

Overview

Preset saver is a native camera feature that gives mobile photographers and videographers the option to create and store their custom camera configurations as templates to use later to achieve consistent and desired results. This helps save time and effort in manually adjusting all the settings while shooting in varying environments.

What problem is being solved

Many people struggle to have consistent results when taking photos and videos. This is most relevant in scenarios where consistent results matter like content creation. The preset saver feature gives its users the option to create custom configurations that they can save as templates to be used whenever they please. It reduces adjustment times and grants the option to create what you feel is best for you, increasing flexibility.

Research

I conducted 3 forms of research

Market research - to understand the mobile photography, and its place in the photography landscape. User interviews - to understand who the users are, perspective and their behavior. Competitive analysis - To understand what other competitors have done.

Pain points

To get a detailed load down of the research material, please click the link below however, here are the main pain points I discovered during my research. 1. Users will require proper onboarding when the new feature. 2. The feature must follow already existing usage patterns to resonate with the users. 3. Access to community presets will be a welcome plus.

Direct link to the project research section

General default camera layout for most mid to high-end smartphones

General layout for smartphone's with "Pro mode"

Ideation Phase

In this section, we will look at how we can tackle the above-listed pain points. We'll begin with the "How Might We" (HMW) questions then set project goals, before we proceed to sketching, design iterations, usability testing, and final design prototypes: - To assess the features and functionality offered by competitor mobile preset apps to identify strengths, weaknesses, and opportunities for improvement. - Objective: To evaluate the user experience and interface design of competitor mobile preset apps to gain insights into effective design practices and identify areas for differentiation. - To analyze user feedback, reviews, and ratings of competitor mobile preset apps to identify common user pain points and gather insights for enhancing our own app. - Identify Market Trends and identify opportunities for differentiation in the mobile preset app.

Using How Might We (HMW) questions to know how we might solve the user pain points.

HMW's questions help us frame our insights and problems in a constructive manner leading to idea generation. - How might we enhance the capabilities and image quality of our default camera app to provide users with even better results and a comparable experience to third-party camera apps? - How might we integrate advanced editing features and capabilities within our default camera app to minimize the need for users to rely on external applications for image editing? - How might we ensure that our default camera app is optimized for different phone models, taking advantage of the specific hardware capabilities to deliver the best possible image and video quality?

Initial sketch design of the interface

Architecture of the preset saver

Low Fidelity Prototyping and testing

Below is a snapshot of a low fidelity prototype. I recruited alpha users from the target audience to participate in the usability tests. I had the participants share their screens while I screen recorded on my end and also monitored their interactions and expressions so I'd know how they interacted with the design and what parts of the prototype needed fixing. The results from the user tests gave me a better understanding of the users' preferences and behavior. Here are the primary insights I got from the tests conducted: - Having an easily accessible and great onboarding experience is the difference between users adopting the feature and abandoning it. - Users are more likely to stick to a feature or product that follows the already existing usage patterns. - Users value the ability to share their presets and media files

Low fidelity est prototype used for the preset savers' usability test

Conducted two rounds of usability tests. This round was used to determine the best access point(s) and most preferable layout design for the feature.

Color coded prototypes I used while trying to determine the best enter point(s) to activate the feature

Typography and font selection

High-Fidelity Design

Impact

Being able to think of this project as a system rather than a feature or one-time project helps create a more inclusive experience for the wide range of smartphone cameras which have different layouts, features, and uses. This project makes use of that thinking philosophy. 1. This project is bound to increase the reliability of users to their native camera applications while also bringing the customization and templating features third-party applications provide. 2. It creates a space for sharing where users can share their presets with other users without having to do so through third-party apps which may be pay-to-use or contain ads.

Onboarding

Onboarding users on new experiences is the best way to make this feature second nature as we push the boundaries of what our existing technology can be used for. Granted, this project may showcase various points of access as well as showcase one way to onboard users, but it is not limited and can be changed based on company preferences, camera interface and functionality ,and user behavior.

Onboarding prototype link

Access points for varying camera software

This project also showcases the features accommodation for smartphone camera differences. There is a vast difference between a high end camera smartphone like the Sony Xperia 1 and the Tecno Camon X which is a mid-range camera-focused smartphone. The multiple points of access gives the feature a higher chance of acceptability.

Preset sharing options

Besides being able to share media files with their presets attached to their metadata, you also get control of whether or not you want to share it or not. This gives the user control of what they send to others irrespective of the mode or transfer. This could also make editing much faster on editors like Photoshop as users already have a preset to work with from the get-go. Receiving preset embedded files. with this you can copy presets directly to your smartphone and possibly in the future, store it on the cloud but don’t get ahead right now. Need to also know how to identify if a file has hidden presets

Liink to preset sharing protptype

Link to full research document

User flow

FAQ's

What if the device doesn't support preset savers

In that case, the preset features like preset data sharing and the icons indicating the preset saver metadata are attached to the file will remain dormant in the media file.

How do you know a media file has “visible” preset metadata access

This icon shows that the media file has presets embedded into it.

Link to full research document

Prototype link to gallery

Want to work with me or be friends? Shoot me a message

Let's Talk

Want to work with me or be friends? Shoot me a message

Let's Talk

Want to work with me or be friends? Shoot me a message

Let's Talk

Create a free website with Framer, the website builder loved by startups, designers and agencies.