As far as I grasp it the best very GOOD routes to HIDING are ...
and
The issue in both cases is you apply the "hiding" before upload. It is not dynamically applied. They don't detect context. They don't know if they are on-web or off-line.
In the longer term, especially with growth of Android usage, may be to use
Startup Actions that draw on info from the
InfoMechanism and then dynamically apply a "Read Only" HIDER.
"Hiders" can work by either / or / and: switching OFF bits of CSS or by removing tags or whatever is needed.
(Sidenote: FWIW the terminology here is confusing. Its NOT really "Read Only", simply you want to "Hide" bits of the interface. Its confusing because the TW remains fully dynamic and anybody who has played with TW will know how to subvert restrictions. "Read Only" should be limited IMO to when there is no serious Javascript TW operating at all. Usually that means "Static" sites. Here we just mean "Hiding Some Dynamics". AKA --> A Noble Pursuit of Simplification For Readers <--)
HOW to do application of "Hider" dynamically on startup I'm not sure. But the mechanisms are there and I'm sure someone with skill will get into it yet.
Yours with CAPITAL notes :-)
Josiah, x