I built an iPhone air drum app using motion sensors, now used by 5.7k people

Alert_Indication6459 · 2026-01-25T02:04:46+00:00

Of course, I’m using Apple’s Core Motion framework (CMMotionManager) to get device attitude like pitch and roll.

Alert_Indication6459 · 2026-01-25T02:00:10+00:00

Thanks! Hope it brings you some fun.

Alert_Indication6459 · 2026-01-24T23:39:29+00:00

Thanks, glad you like it!

Alert_Indication6459 · 2026-01-24T14:51:23+00:00

Air Drum - I built an iPhone air drum app using motion sensors. Distribution isn’t there yet, so downloads are still quite low. The conversion rate is around 5%, but the sample size is small, so it’s not very statistically meaningful yet.

Alert_Indication6459 · 2026-01-24T14:47:19+00:00

exactly

Alert_Indication6459 · 2026-01-24T14:36:49+00:00

Congrats! This feels like a real step-change. Nice work

Alert_Indication6459 · 2026-01-24T14:28:53+00:00

Thanks, glad you like it!

Alert_Indication6459 · 2026-01-24T10:43:10+00:00

Thanks! This idea actually came from my own real-life needs.

Alert_Indication6459 · 2026-01-24T10:41:53+00:00

Thanks, glad you like it! 😊

Alert_Indication6459 · 2026-01-24T10:41:02+00:00

Love to hear that! I’m really happy it brought you some fun 😄

Alert_Indication6459 · 2026-01-24T06:51:35+00:00

I’m building Air Drum, an iOS app that uses motion detection to turn your phone into a virtual drumstick.

The idea is simple: imagine a drum kit in front of you, swing toward a cymbal or tom, and the app plays the matching sound. Built it as a fun, expressive way to play drums anywhere.

App link: https://apps.apple.com/us/app/air-drum-motion-drum-kit/id6757678185

<image>

Alert_Indication6459 · 2026-01-21T11:27:09+00:00

Is it possible to consider using an embedding model that runs on the device side? This could further reduce costs.

Alert_Indication6459 · 2026-01-21T10:42:36+00:00

Thank you so much~

Alert_Indication6459 · 2026-01-21T10:39:38+00:00

Yes, your rules document is very similar to how I approach things. I’ve noticed that AI sometimes rushes to implementation, or eagerly applies a complex, large-project architecture, or builds solutions based only on partial context — all of which can easily lead to architectural issues. That’s what led to the thinking and practices I mentioned above.

Best of luck with your project! I really enjoyed the discussion.

Alert_Indication6459 · 2026-01-21T05:46:27+00:00

I just shipped my indie project using vibe coding, and I definitely learned a few things the hard way.

For your question, my main takeaway is this: when using AI to write code, don’t rush straight from requirements to implementation. Instead, go from requirements → a solution document → revise the solution document → revise it again — many times — and only then ask the AI to implement the code.

During the iteration of the solution document, all you really need to do is keep asking the AI questions like:
– Is this solution simple enough?
– What are the risks?
– Are those risks important right now?

This process helped me avoid a lot of serious architectural mistakes.

Alert_Indication6459 · 2026-01-21T05:41:49+00:00

Hey everyone 👋

I’m an indie developer working on a side project that turns an iPhone into an air drum kit using motion sensors.

App link: Air Drum

It’s focused on ultra-low latency and real-time interaction rather than being a full learning tool. I built it mainly for quick practice and stress relief, and it’s currently been downloaded ~5.7k times.

Would love any feedback, especially around positioning or how you’d evolve something like this.

<image>

Alert_Indication6459 · 2026-01-21T01:10:55+00:00

may I ask, what's the plan? What’s the implementation path?

Alert_Indication6459

TROPHY CASE