Feedback & Feature Requests
Share your ideas, suggestions, and feature requests with the community!
Welcome!
We’re always working to improve MiraBot hardware and MiraPlay apps.
Your feedback and ideas help us build features that truly matter.
If you have any suggestions, problems, or feature requests, feel free to leave a comment below!
VR Feedback Gift Campaign
Users who share useful feedback or feature requests may be eligible for a
foldable smartphone VR glasses gift 🎁
How to participate
1. Leave your feedback or feature request
Post your comment below.
2. Place an order
Add any MiraBot product or accessory to your cart.
3. Add order note
In the order note, please include: Your comment name + “need VR glasses”
Who can receive
New customers —
New customers who purchase any model of MiraBot S6 or MiraBot Lite.
Existing users —
Existing users who have purchased MiraBot S6 or MiraBot Lite and buy any accessory.
Notes
- This VR gift can be combined with our existing bonus gifts.
- The VR glasses gift is a foldable smartphone VR glasses. Gift details and specifications: See specifications ›
- Campaign may be updated or changed without prior notice.
📝Guidelines
✅ Be respectful and constructive.
✅ Clearly describe your suggestion or the issue you encountered.
✅ Search before posting to avoid duplicate requests.
✅ Our team may reply or ask for more details.
✅ To prevent spam, comments are reviewed before publishing. After submitting, your comment will usually appear within 1 business day.
It’s great to see the Mirabot ecosystem still getting regular updates. The recent direct Deovr connection is definitely a big plus. I’ve been really happy with my S6 and the Miraplay apps so far. The only thing I’d like to see improved is making it easier to switch between Bluetooth and Wifi
I think the Mira Bot is missing a vibration implementation. It is the only feature that this device lacks that a competitor might have. Either that or a module that would implenet the KIRRA mold into the socket so its own vibration device could be implemented. Allas I do not know the negative impact such an implementation would have on the overall structure of the device as the vibration could loose up screws or over-stress joints, which would not be the best.
Mirabot would benefit from hardware locked settings that are forced when switching platform to platform – explicitly, stroke range of motion reduction, with smart controls to manage different mixes of ROM limiting based on where particular axis are located.
Slipping out is a massive issue as the full range of motion is only realistic for someone rather above average.
Making it so stroke limits or ROM limits apply to any script played in player is essential, as well as having dedicated profiles.
MiraControl Web app also needs to support Apple Login, it currently has no support for users with an Apple based account.
Thanks for the feedback! That’s a very valid point.
Actually, we’re already working on adding a device-level stroke range setting in the firmware, so the range limit can apply more consistently instead of only being adjusted inside individual apps or scripts.
The current plan is to include this in a firmware update later this month.
For Apple Login on MiraPlay Web, thanks for the reminder as well. We’ll add that to our schedule and look into supporting it.
I would look into how MFP utilizes smart limits and see if you can’t possibly reverse engineer something similar?
Happy to hear it’s in the works! I await being able to use things once the update lands!