IN-HOUSE Roulette Simulator

[HardMan]

I have neither a phone nor a laptop/desktop computer -- my requirements are met with one device only that addresses all = an LTE-capable tablet.

Vic, I know you are working on RIBOT -- which, btw, I cannot use directly (Android).

However, I do have one request/suggestion: an in-house manual simulator.

[HardMan]

You know that I have been testing my systems manually, which goes at a very slow pace, taking ages ..

As its commonly known RS, its interface is great, which I was using previously, coz it can be accessed with a browser alone .. but frankly has a fucked up rng that does not nearly match real casino tables distributions, & most importantly, due to its rated games competition scheme, does not allow for importing of the spins.

RX interface .. I don't like that much (outdated 2000s design Windows-based design), has a spin import feature .. but can't use it on phones/tablets either, & as confirmed by UX software themselves, they have no intention to support Android at all.

These are the only two simulators publicly available & neither of them is fully functional in terms of satisfying my requirements -- perhaps others' too.

I already spoke to you about RIBOT's felt display module, where the systems/sessions can be replayed, spin-by-spin + jump-in on any spin count (great for group discussions & presentations of concepts, etc. .. when developing a system);

now, looking at your instructional videos I might add .. that such a module, as an option, would be great to be displayed meanwhile the original simulation is running too.

[HardMan]

But what I am writing to you about here is -- on the forum itself -- having an in-house manual simulator -- just like RS, with the import of spins & saving of the sessions + replay.
Would such interest you to set up, & how long it would take to make it operational -- so anyone with a browser can run it, anytime. Can the interface code be pulled directly from the RS site?

[HardMan]

& can RIBOT itself be adapted to use only with a browser = browser-based?

Let's be honest, the way its looks now (that has nothing to do with you, but with the Windows-inherent design) looks, as mentioned RX above .. a bit outdated .. & its multiple windows are weird to manage -- or it's just me, & being used to the modern web- & android interfaces?

Once in browser-based, its pertaining windows become sections, which are simple to resize, especially on touch-screens (lots of laptops are touchscreen too), sections expanded (minimized, opened when used), & moved about with ease .. in the way that's desired.


& potentially, also clothed as an Android/Apple app.

Some things to think about.

[VLS]

Thanks for your great input. A detailed answer is a must!

& can RIBOT itself be adapted to use only with a browser = browser-based?

Yes. We are going to do the "RIBOT DEV" version of our software using the UNO Platform.

Their promise:

The Uno Platform is a UI Platform for building single-codebase applications for Windows, Web/WebAssembly, iOS, macOS, Android, and Linux.

https://github.com/unoplatform/uno#what-is-the-uno-platform

So both RIBOT versions will coexist for a period of time: current version with the "traditional look & feel" from Windows and the RIBOT DEV version slowly building for the modern mobile/web.

In the end, the goal is to adopt the new DEV technology as our main release version.