Photo Books iOS
Kodak Moments lives under the global heritage of the renowned Kodak brand. As a team, our goal is to create delightful experiences that help customers place their treasured memories into products that will bring them to life in tangible forms.
Creating a photo book is a time-consuming process even for the most experienced. As a result of having cell-phone cameras, it is easier to end up with duplicates, screenshots, notes, and several unwanted photos in messy, unorganized collections. It is hard to sort through the clutter and find the treasured gems that best tell the story.
Role and Team
Role on Team
Research, UX, Visual Design
Moderate Design Sprints
Competitive Research Analysis
Flow and Wireframes
Who was on the Team
Front-End Developers (3)
Product Manager (1)
Mobile Web (Responsive)
Where We Started
There was a basic book builder for iOS prior to my time at Kodak. This project was, in part, a visual redesign to update to current branding guidelines.
With that said, this was the perfect time to tackle one of the most challenging parts of building a photo book, sorting through the photos and placing the best photos in the book.
How Might We
Provide a quick selection of photos from collections
Speed up the process of finding and selecting the best photos
Improve price transparency throughout the entire experience
Provide a straightforward process to complete a book in one session
As a team, we began working through design sprints in order to better understand the customer's needs and to set up the project for success.
Stakeholders were PMs, Marketing, VP, and Developers
Initial Flow Planning
There are several competitors in the photo book space, especially for iOS. Kodak is looking to play in the space but also find a competitive edge above the rest using a best photo algorithm to help customers find their best photos.
Initially, we were solving for the photo books shop page, the Made For You book, and the first time user.
It quickly became apparent that this was too large of a scope to complete before the deadline and the decision was made to focus on the first time user who is interested in just building a basic book.
Key Feature Iterations
Several iterations were made for the entire building experience. The examples below focus on a few iterations for the key features Photo Picker, Smartfill, Overview, and Edit Pages.
We used Usertesting.com to run a test a set of screens from a hi-fidelity prototype. The test was not over a flow but instead of various sections of the flow. We tested the Picker, Smartfill, and the Photo Tray.
The best case scenario would have been to test the entire flow in addition to the sections that were tested using 5 users. With that said, here are some of the key findings from the sections test we conducted:
“It’s very helpful, very quick, very easy to just go in there and if you want to include the whole story you click “Select Story” and it puts a checkmark by all of those photos included into that story.”
“I am going to go with a 4 again because I can see what it is doing and I can see it is filtering out duplicates. But I am obviously not familiar with how it determines which is the best copy of those multiples or anything like that.”
I really wish it would have said, for smartfill on that Kodak Moments Screen, and maybe gave you a description of what Smartfill is. Add Best Quality Photos with One-Click or something along those lines because I am really not grasping the concept of what a smartfill is, so I am giving it a 3 because I am uncertain.
“Looks very natural to move around and select different items, there is not really any big changes that would be kind of confusing to anyone who is not already familiar with using a phone like this.”
I went through the tests and transcribed the videos taking notes along the way that would help the team gain insight into what changes needed to be made for the next round of iterations.
Need to show photos in the Smartfill experience
Clear directions for how to use the Smartfill
Final handoff included an InVision prototype to show flow and interactions, Zeplin Files with assets, and stories using Pivotal for the development team to take action on and understand the required interactions.
As we were completing the handoff of the assets for the iOS App the web team was requesting the materials and this is the point in the project where we transitioned and strictly focused on converting the experience we created for the iOS for responsive web.
Some of the things we learned are that it is best to conduct user tests and interviews early and often. This helps eliminate the need for assumption based decisions and provides more leverage for the team when communicating with stakeholders. We also learned that it is best to bring the development team into the mix early in the design process.