Hi Trystan,
The days of "We can't be bothered working out the full multifarious repercussions of this change, so lets launch it and see who complains" are long long gone! Simply not acceptable in the 21stC.
Suggest that the management of your organisation needs to seriously address the subject of Change Control in the launch process of releases of your web site software.
[Get/study the appropriate ITIL (& PRINCE2) books.]
Your high level public interfacers are denying that any change has been made, yet you are admitting that you made one unilaterally, without due assessment, authority, notification (and availability to support?). Phew!
The Rootschat user base is world-wide.
This is a serious booboo!
----
Delivery to mobile devices is a complex scenario.
Extensive work is required on the combinations of platforms, OSs, and browsers.
[Get friendly beta-testers on-board for all major changes ...
The current one would not have got out of the foundry!]
----
I onced worked for a company who encouraged innovative action.
However, they recognised the dangers.
"If we don't see you making mistakes, then we reckon that you are not pushing yourself hard enough."
[N.B. Such being very distinct from "Free feel to make mistakes."!]
This was backed up by:
"Make the same mistake twice, and you are out!".
This concentrated the mind wonderfully!
----
On the technical side ...
The Rootschat "classic" view was fine on my Samsung mobile.
The only minor complaint that I might have made was that it was sometimes difficult to select e.g. Page 2 of a multiple page topic.
This was due to the smallness of the icon and its closeness to alternatives.
Such was worked round by expanding to full screen scaling, then e.g. "pushing" the "1" icon off screen.
Perhaps you might consider making a helpful "mobile" mod to make these "Page" active areas have a larger extent?
[e.g. stretching proportionately across the screen, rather than being clustered closely together in the lower LH of the page ...?]
Capt. Jock
