Overview
It's a Practice is a mobile application designed to support focused music practice through reflection. Developed for serious musicians, the project explores how digital tools can complement study routines without competing for attention.
Many existing practice applications rely on timers, streaks, notifications, and performance metrics to encourage engagement. While these approaches can be effective, they often introduce additional interaction into activities that require deep concentration. This project explores how a digital product can support musical development while remaining secondary to the practice itself.
Problem
Serious musicians practice as part of a daily routine that requires focus and repetition. Existing practice apps are often designed for beginners or rely on metrics, timers, notifications, and interaction patterns that interrupt concentration.
As a result, many experienced musicians avoid using their phones during practice altogether.
The central design challenge became:
How might a digital tool support focused practice and meaningful progress without disrupting focus?
Design Constraints
1. The app would be a mobile-first experience.
2. Interaction during practice needed to remain minimal.
3. Workflow needed to align with real practice habits.
4. Sessions needed to be quick to start and complete.
Insights
Through interviews with four musicians, it became clear that experienced musicians already track progress through annotations, practice journals, repetition, and self-reflection. Many are also wary of introducing technology into their practice routines, as digital tools can compete for attention and disrupt concentration.
This suggested that the problem was not a lack of tracking tools, but the way many existing apps demand interaction during the practice session itself. For a practice app to provide meaningful value, it would need to support organization and reflection while remaining largely invisible during practice.
Early sketches of the app's session flow.
For a practice app to provide meaningful value, it would need to support organization and reflection while remaining largely
invisible during practice.
Design Principles
1. Minimal interaction during practice
The app should not compete with the instrument for attention.
2. Reflection over metrics
Progress should be measured through awareness and learning rather than time-based statistics.
3. Intentional simplicity
Reducing features lowers cognitive load and supports sustained focus.
4. Clear feedback loops
Users should be able to quickly review notes and recognize patterns in their practice over time.
Solution
The app is built around a simple three-stage workflow that mirrors the practice routine many musicians already follow. Rather than introducing new behaviours, the experience supports existing habits through a streamlined process focused on preparation, practice, and reflection.
Start Session
Users begin by selecting a piece and defining a clear practice goal. The streamlined setup minimizes decisions, allowing sessions to start quickly while keeping attention on the instrument rather than the interface.
Start session screen
Practice
Once practice begins, the interface becomes largely passive. Only a timer and metronome remain available, minimizing distractions and keeping attention on the instrument.
Practice screen with timer and metronome
Reflect
After each session, users record reflections, track practice time, and update their progress. Capturing these observations creates a structured history that supports long-term improvement.
Reflect screen
Key Decisions
UI Design
Typography
Two typefaces are used: Academico for display and Inter for content. Academico references traditional sheet music aesthetics, adding a sense of familiarity and authority. Inter provides clarity and readability for functional text.
Typography
Spacing
A consistent spacing system (16, 24, 32px) maintains rhythm and clarity across screens.
Spacing
Color
A restrained palette uses black, white, and grayscale for hierarchy, with lavender as an accent for primary actions and selection states.
Color
Components
Reusable components were used for buttons, cards, and headers to ensure consistency across the interface.
Components
Outcome
Initial feedback from five musicians indicated interest in incorporating the app into their practice routines, suggesting the concept aligns with real user needs. This is early feedback on a concept, not a tested product.
This project highlighted the challenge of balancing flexibility with simplicity. While the app must support varied practice styles, adding too many options risks increasing cognitive load and reducing usability.
It also reinforced a broader insight: many digital products aim to maximize engagement, but in some cases, this creates friction. Designing for utility and restraint can lead to more meaningful and sustained use.
