I trained a 125M model to autocomplete piano on-device

I trained a 125M-parameter transformer to autocomplete piano performances in real time (~108 notes/sec on an iPhone 15).The idea is basically GitHub Copilot or Tabnine, except instead of prompting it with code, you prompt it by playing a few notes on a MIDI piano. The model then continues what you played, entirely on-device.The app is free if anyone wants to try it. Happy to answer questions about the model, training, Core ML, or the many things that didn't work.

Hacker NewsToolAISource
0Sign in to voteCopy link

FL score

62

out of 100

Verdict

VALIDATE

medium confidence

Competition

No competitor data yet

Trend

No signal yet

A free on-device piano autocomplete tool that generates musical continuations from MIDI input, solving the cold-start problem for composition but facing unclear monetization and limited addressable market.

The pain

Musicians hit creative blocks during composition. Pianists specifically struggle with continuation, knowing what notes come next when improvising or writing. Existing tools (DAWs, notation software) require switching contexts or don't offer real-time suggestions. The friction is real but niche.

The gap

No existing product combines on-device inference, real-time latency (~108 notes/sec), and piano-specific training at this scale. GitHub Copilot proved code autocomplete has product-market fit; this applies that pattern to music. The technical execution gap is closed, but the market gap remains open.

Build angle

Start by validating whether pianists actually want this during composition. Run 20 user interviews with composers, session musicians, and piano teachers. Measure: Do they use it repeatedly? Do they pay for premium features (MIDI export, style variants, offline packs)? Only after proving retention should you build monetization. The free distribution is smart for discovery but unsustainable long-term.

Strengths

  • Technical execution is genuinely hard and complete, 125M model on-device at playable latency is non-trivial
  • Zero cold-start friction; users can try immediately without signup or learning curve
  • On-device privacy and latency beat cloud alternatives by default
  • Narrow enough domain (piano) to train a focused, useful model rather than a generic one
  • Proof of concept already exists and is free, lowering validation cost

Risks

  • Addressable market is small, serious composers are maybe 500K globally, and many won't want AI suggestions in their creative process
  • No clear monetization path; free distribution builds users but not revenue. Subscription, premium styles, or export features may not convert
  • Quality bar is high, bad suggestions actively harm the creative experience and kill retention faster than no suggestions
  • Dependency on Apple's Core ML ecosystem limits distribution; Android users are locked out
  • Competitive risk from larger AI labs (OpenAI, Google) building music models with more training data and distribution reach
  • Network effects are absent; each user's value doesn't increase with more users

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “I trained a 125M model to autocomplete piano on-device”.

Open FlyBot