KALEIDOSCOPE
Logger app screens on iPhone

LOGGER

Logger was a customizable iPhone app for tracking anything. I designed and built it independently after finding existing tracking apps too rigid for unique personal needs.

Years
2021
Role
Designer & Developer
Platform
iOS

Working independently, I created Logger and wore every hat: design, engineering, user research, bug prioritization, copywriting, and marketing. I recruited an early set of users and grew a sizeable beta group whose feedback helped shape the product.

I laid out the onboarding screens to address the biggest feedback I got from testers—what can I use this for?

I built a variety of prompt types, from photo and location capture to custom rating sliders based on emojis.

CHALLENGE

EXTEND THE WELCOME

How could Logger make an unfamiliar data-entry model approachable to people with different levels of technical comfort?

I treated onboarding as the entire process of helping someone understand what a Log was and what it could do—not only the introductory slides at first launch. I renamed technical jargon, revised copy throughout the app, and removed points of confusion that beta testers encountered.

PROTOTYPE

An early prototype explored how to introduce Logs as customizable journals.

FINAL
Logger templates for relatable use cases

Templates made relatable use cases visible when someone started a new Log.

Instead of technical terms such as forms, fields, and inputs, I used Logs, Prompts, and Responses. Those words resonated with less technical testers, who compared Logs to journals, and avoided making the product feel like a database.

Templates then made the product’s flexibility concrete at the moment someone created a Log. They illustrated relatable use cases without forcing people to invent one on the spot.

As beta testers surfaced confusion, I kept revising the copy and removing friction. The work reinforced that onboarding was an extended experience across the product, not a set of slides people had to remember.

CHALLENGE

REDUCE THE WORK

How could a highly customizable app make repeated manual entry feel quick and sustainable?

Logger was built to be customizable, so people could edit templates and capture only what mattered to them. Suggested and Remembered Responses significantly reduced typing, helping repeated entries stay quick.

ENTRY
Suggested and remembered responses in Logger

Suggested and Remembered Responses reduced typing during repeated entries.

REVIEW
Adaptive entry cards in Logger

Adaptive cards kept important values prominent while people reviewed many entries.

I designed the card layout to adapt to whatever data a Log contained, keeping important values prominent while someone scrolled through many entries. That helped very different information feel considered without requiring a separate interface for every use case.

Logger was well received by people who arrived with a use case in mind, and conversations with beta testers helped me prioritize the highest-impact sources of friction.

Looking back, I would focus more narrowly on use cases that deliver immediate value, add CSV import and export, and simplify the interface. Some people still struggled to understand the concept, while those who downloaded without a clear use case rarely developed one. The project taught me to pair flexibility with a sharper product position.