The “how it works” that makes that bad feeling in the UX is that a Web app is made of 2 parts glued together, that should have proper isolated processing, the UI (client side) and the backend (server side). In many environments we write an interface code that solves things on the client side without the need to send any data to the server side, like reading a field, and do some math, and present a result concatenated to a string from other field, show an error message, asking for a retry…, all client side, and depending on the result the final value could be sent to the backend to process the server side of the app we wrote. Xojo mix those in a concept called “server round trip”, all things are sent from the UI to the server, and all processing is done on the backend, and the backend send the UI updates back. This can kind of work, for some very simple UIs, in low latency environments (like an intranet) using powerful and fast servers; but can be unacceptable for $5 VMs on the internet… that other tools can handle easily. I don’t see Xojo separating the processing in 2 sides in the current design, you guys will need to wait for Xojo Web 3.0 
