What a good music app should and shouldn't do

Last year I took on a new student. Old enough to manage his own schedule, young enough to not actually do it. His previous teacher had handled everything through WhatsApp: lesson materials as photos of photocopies, appointments as text threads, and a practice schedule somewhere in a folder on his phone that he never found again. His first question to me wasn’t “what are we going to learn?” — it was: “how does this work here, exactly?”

That question stuck with me. He wasn’t asking about the content of the lessons. He was asking about the structure around them.

Around the same time I started thinking more seriously about which digital tools I was actually using, and why. Not out of hype, but out of that simple question: how does this work here, exactly?

---

In recent years a lot of software has appeared for music teachers. Apps for lesson planning, communication, tracking progress, sharing sheet music. And also: apps that try to bypass the teacher entirely — platforms selling directly to the student, promising “adaptive learning paths,” claiming to be better than a human.

I try to keep those two categories clearly separate in my mind, because confusing them costs you time and energy.

An app that helps you do your work better works with you. An app that claims to take over your work goes around you. That’s a big difference, even if the interface looks the same.

---

So what does a good app actually do?

The most honest answer I’ve found: it takes over the things you currently do by hand that add nothing to the learning process itself. Not the lesson. Not the feedback. Not the moment when you hear something in a student’s playing and you know exactly what to say. Those things can’t be automated, and they don’t need to be.

But keeping track of what was practiced last week. Sending a confirmation when someone reschedules. Finding sheet music from two months ago. Storing a note about the technical mistake that keeps coming back. Those are tasks I used to handle on loose pieces of paper, in WhatsApp threads with no structure, in my head.

If an app takes those tasks off my plate — in a way I trust and can retrieve — I get more room for the things only I can do.

---

But there’s a trap I fell into myself.

You start a new system, you’re enthusiastic, you invest energy setting everything up. Three weeks in you notice you’re spending more time maintaining the system than you ever spent on the loose papers. You’ve replaced one administrative task with another, but now with a subscription on top.

A good app has to demand less work than the alternative. Not prettier, not richer in features — less work. If after four weeks I notice I’m forgetting to open the system, that’s information. The system doesn’t fit how I work, or I’ve set it up wrong, or it requires too much friction for what it delivers.

---

There’s also something I explicitly don’t want a good app to do: replace my professional judgment.

I hear this sometimes from colleagues experimenting with AI platforms. “The app says the student is ready for the next step.” But how does the app know that? Based on how many times he’s completed an exercise. Based on a score in a digital test. Not based on whether that student’s grandmother died last week and he just needs someone to be calm around. Not based on whether he slept last night. Not based on the hesitation in his playing that tells me he technically can do it but doesn’t trust himself yet.

An app that replaces you in your own work isn’t a tool anymore. It’s a competitor.

---

I use a student file in the apps I call Musicdott — not to promote it, but because it’s the most concrete example I have. What I value most about it isn’t the scheduling or the notifications. It’s that before each lesson I can look back at what I wrote the week before. Small things. “He lifts his shoulder at speed.” “Always asks for songs, no interest in technique for its own sake.” “Comes alive when he sees that something brings him genuinely closer to a song he wants to play.”

That sounds like small details. But those details are the difference between a lesson that lands and one that disappears.

---

I sometimes see colleagues avoiding digital tools because they feel it’s cold, or impersonal. That the lesson starts to feel like a checklist. I understand that concern.

But I think that concern reveals something else: there is bad technology that really does that. That turns a lesson into a session, a student into a progress bar. If you’ve experienced that, I understand why you want nothing to do with it.

The question is just whether you’re also rejecting the technology that does the opposite — that gives you more room for the human side, precisely because it takes the logistical burden off you.

---

That’s ultimately the question I ask myself about every tool I consider: does this give me more room for the student, or less?

Not: is this efficient? Not: can this scale? But: after using this system, am I more present in the lesson, or more in my head with things I still need to sort out?

The technology that answers that question with “more” is worth your time. Everything else you can leave on the shelf.

---

What task in your teaching practice costs you the most energy right now without giving anything back to the student? That’s probably where good technology makes the most difference.