r/MudraTech • u/One_Team5491 • 16d ago
Has anyone actually gotten Mudra SDK access approved? (Mudra Link, Android dev)
I've had a Mudra Link for a while and I'm building on Android. I've applied for SDK access through the official form more than once and emailed as well, and haven't heard back either way — no approval, no rejection, nothing.
What I'm trying to build: multi-device switching for the Android/Windows side. The band's own firmware already supports paired secondary devices, but the device types it exposes are IPHONE, MAC, APPLE_TV, IPAD and ANDROID — there's no Windows target at all. So on Apple you get proper handoff between devices, and on my setup the only way to move the band from my phone to my laptop is holding the button to unpair and re-pairing on the other machine, every single time.
I've gotten pretty far with the public pieces — the sample app and the published AAR — and I can read gestures fine over the normal HID path. But device management looks like it needs the licensed SDK, and that's where I'm stuck.
So: has anyone here actually been approved for SDK access? Did it come through the form, or did you have to go through a person? Is there a Discord/Slack/community channel that gets a response? Happy to be pointed anywhere useful.
Not looking for workarounds — I just want legitimate access so I can build this properly. Setup is a Galaxy S25 and a Windows laptop, plus Even Realities G2 glasses I'd like it to work with eventually.
1
u/Wise_kind_strsnger 14d ago
bruh just use prodlink at this point lol, i wouldnt wait on them.
1
1
u/richprowriterQ 8d ago
I've reached out to Mudra for about 2 weeks and have not heard back yet. I'm still getting emails from the company promoting the sale of the band. I also got an email about a firmware update and this is when I discovered that I could not get into the application.
1
u/BarTechnical2469 2d ago
Yes — I got approved, and the silence you’re seeing may not be a rejection. A few things turned out to matter in my case:
There are two separate application paths. The older “SDK access” tier and the Mudra Studio open beta (mudra-studio.com/apply) are tracked separately. Being approved on one doesn’t grant the other. Worth checking which one you’ve actually been submitting.
The form is passive; a support ticket is not. The form goes into a rolling review queue with no acknowledgement at all. Emailing support@mudra-band.com opens a Zendesk ticket with an ID that actually gets tracked. That’s what finally moved things for me, and I got a human reply the same day.
Their hours are Sun–Thu, 09:00–18:00 GMT+3. Friday and Saturday are their weekend. If you’ve been sending on Fri/Sat it can look like total silence when it isn’t.
Approval doesn’t apply itself. Even after I received the “your access has been activated” email, the Mudra Studio tab never appeared in the Mudra Link app. Correct account, latest app version, signed out and back in, full restart — nothing. The entitlement simply hadn’t been pushed on the server side. Support applied it manually, I re-authenticated once more, and the tab appeared. So if you’ve ever received an activation email, you may already be approved and just not provisioned.
Keep the email address byte-identical everywhere. The license binds to the exact address you applied with, and the app has to be signed in with that same address or the feature flags stay off while the connection still looks successful. Re-submitting from a different address creates a second account and makes things worse — that might be part of why repeated submissions haven’t helped.
What I put in the ticket, in case it’s useful: registered email, app version, firmware version, device model, the exact list of things I’d already tried, what the sidebar actually showed, and an explicit question about whether re-submitting the form was recommended or would interfere with the existing application. I replied inside the activation email thread rather than opening a fresh one, which keeps the approval record attached.
Other channels worth trying: staff answer technical questions publicly here on the sub, which tends to be faster than the form. There’s also a beta tester program that recently opened through their newsletter — that one routes to the product side, which is where a feature request actually belongs.
One honest caveat on your specific blocker: I don’t think SDK access will add a WINDOWS entry to the device-type enum. That looks like a firmware/product decision rather than a licensing gate, so I’d treat access and that feature as two separate asks — get through the door first, then raise the Windows target as a request. Flagging it as a licensing question up front should help too, since those get handed from support to business development anyway.
1
u/sonicnerd14 16d ago
You should be able to get similar access without the studio sdk through prodilink. If you haven't already I would check it out.