Hi guys!
We’ve been working on a major rebuild of MiraPlay AiO, and I think it’s finally at the point where I can start showing some of it.
The new version will bring a completely redesigned UI, no forced login for offline features, automatic device connection, Motion Studio support, and a new Remote Play workflow for DeoVR and HereSphere.
It’s still a few weeks away from release, but before everything is finalized, I’d like to share some previews here and collect feedback while there’s still time to improve things.
Why a 2.0?
MiraPlay AiO originally launched alongside MiraBot a little over a year ago.
Since then, more people have started using it and we’ve received a lot of useful feedback. We released several smaller updates along the way, fixed quite a few problems, and added new functions.
But as the app kept growing, some of the early design decisions also started becoming harder to work around.
At some point, continuing to add small updates no longer felt like the right solution.
So around three months ago, we shifted most of our development effort away from incremental updates and started rebuilding MiraPlay AiO as a new 2.0 version.
The goal is not just to make it look different. We want everyday use to require fewer steps, less setup, and less time thinking about connections and configuration.
1. Cleaner UI, Fewer Steps
The first obvious change is the interface.
We redesigned most of the UI with a simpler and more consistent layout, but more importantly, we also changed several workflows that previously required too many manual steps.
Some of the changes include:
- No forced login for offline features
Functions that do not require online services can be used without signing in. - Automatic device reconnection
Once a device has been set up, MiraPlay can reconnect automatically the next time it becomes available. - Simpler device management
Device status, connection information and settings are easier to access from one place. - Graphical Arm calibration
Arm leveling and calibration are being redesigned into a more visual setup process. - Easier mode switching
Supported Wi-Fi / Bluetooth / SLR-compatible modes can be switched directly from the device settings, without needing to connect the device to a PC with a cable.
One thing I especially wanted to improve this time was the initial device setup.
Ideally, once everything has been configured correctly the first time, you shouldn’t have to keep thinking about it every time you open the app.
2. The Existing MiraPlay Features Are Staying
The features that made MiraPlay useful in the first place are not being removed.
We’re continuing to improve:
- VR video playback
- Gesture Sync
- Script recording and playback
- Built-in Browser and Funscript playback
- Remote Connection
The interaction for some of these features has also been redesigned.
The goal here is mostly to make functions that already existed easier to understand and quicker to use rather than simply adding more buttons.
3. Motion Studio Motions Inside MiraPlay
This is one of the additions I’m personally quite interested in.
MiraPlay 2.0 will be able to use Motion projects created in or downloaded through MiraBot Motion Studio during video playback.
That means playback will no longer be limited to traditional Funscript tracks.
You’ll also be able to select reusable multi-axis Motions and use them together with a video inside MiraPlay.
Funscript will of course remain fully supported. Motion is simply another option for situations where reusable, parameter-based or multi-axis movement makes more sense.
4. Remote Play with DeoVR and HereSphere
Another feature we’re working on is Remote Play for VR.
The basic idea is:
MiraPlay on your phone
→ plays and manages the Funscript
→ controls the connected device
while
DeoVR or HereSphere on your VR headset
→ handles the actual VR video playback.
The overall workflow is somewhat similar to using MultiFunPlayer on PC, but the goal here is to make it possible with a more mobile setup.
This is still one of the areas we’re actively testing, so I don’t want to overstate what’s finished yet.
Once it gets closer to release, I’ll share more details about how the connection and synchronization work.
5. Built with Future Expansion in Mind
A major reason for rebuilding the app instead of continuing to patch the existing version was to give us more room for future features.
MiraPlay will continue supporting DIY and TCode-based devices, but we also want to build deeper integration between:
MiraPlay + MiraBot hardware + firmware + accessories + Motion Studio
Over time, this should make it easier to add things such as:
- Additional expansion module controls
- More flexible device-level settings
- Better multi-axis control
- Deeper Motion Studio integration
- More remote interaction options
We’re also experimenting with a more open remote interaction system that could eventually make it easier for users to connect and interact over the internet.
These are longer-term directions rather than promises for the first 2.0 release, but the new architecture gives us much more room to work with.
Still Free for OSR Users
MiraPlay AiO 2.0 will continue to be free for all OSR users.
Compatible OSR / TCode devices can connect directly through Wi-Fi (UDP) without needing MiraBot firmware.
One of the original goals of MiraPlay was to make multi-axis devices easier to get into without requiring new users to first learn several PC applications, bridges and configuration tools.
That goal hasn’t changed.
At the same time, we’ll continue developing MiraPlay closely alongside the MiraBot ecosystem so that MiraBot hardware, firmware, accessories and software can work together as smoothly as possible.
I’d Like Some Feedback Before Release
There are still a few weeks of work left before 2.0 is ready.
I’ll keep updating this thread with more screenshots and feature previews as things become finalized.
If there’s something you’d like to see improved, changed, or added to MiraPlay, feel free to leave a comment below.
A lot of the changes in this version came directly from things users pointed out over the past year, so I’m definitely interested in hearing more ideas before the new version is locked down.
Current MiraPlay AiO
The current version of MiraPlay AiO is available by searching for MiraPlay AiO on the App Store (iOS) or Google Play (Android).
Android users can also download the APK installation file directly from our Google Drive
I believe MiraPlay AiO works best together with MiraBot.
If you’re looking for a multi-axis device to use with MiraPlay, feel free to take a look at MiraBot here:
