Thank you very much Markus for the shoutout I on MacUpdate. That’s really kind 
You see it by self: “you” bridge it. Nobody else does at the moment. That’s exactly the point. And I doubt that this is a good invest to spend much time in. But I am anyhow not a native lover.
DOH!
That’s possible cause they have to await no problems from it. They have no warranty for their product and if it is sh.t then it is… Thinking this further we will arrive at the point that we have only one chance: go away for another product. Java, C#, flutter/Dart, Python there are many choices we could use to work with. But for the XoJo users there is one initial thing you don’t have with C# and many others: a drag and drop screen designer. And XoJo does all the work in case of window handling. Not like you will have to do with Java, C# and others. Simply in all platforms the same way.
Or in other words: starting with XoJo is for many people really comfortable. That’s why they are users of XoJo. And the IDE handles most of the controls you have to do in other languages by self. To have the control above it. But in XoJo you don’t have even to think about it. That makes life easier for the programmers. It reduces capabilities and control. But they are happy not in the need to learn all that stuff.
Uno uses native controls under the hood - or so they advertise
I thought this is only for iOS and Android Applications available and not for Desktop. At least it still looks like it on their Website:
Following to the picture it is like I thought, following to the text it is also for Desktop, mobile and web what ever Web native UI is. Sounds a bit weird but I have no experience with it so it can be that this works like you expected it,
You need to list Objo Studio on MacUpdate.com. This would expose Objo to a large audience of Mac users.
Right now I am working on a small personal project using Xojo R19.1 on a mac in a virtual machine… As i have not coded for a few years (my job changed) I have had to use the integrated language reference more than I used to… and it’s a joy to use compared to what came after!
Why not switching to Objo? 
What kind of app are you working on @Karen? I wonder if Objo does cover its needs. If not, I’m certainly open to suggestions on what would be needed to be added to the tool to help.
impressive, reading your docs right now JSON, XMLs, SQLite, HTTP Server and Sockets even Matrices and asynchronous operations with tasks, Await and WhenAll. I am impressed
Yes, a great job. If he opts to more platforms he has a slightly better way to it than XoJo has: he can use the dotnet ecosystem for it. Much better than the way Xojo has to go.
Which programming language is the Objo compiler and runtime written in?
It’s written in 100% C# / .NET
registred to your forum and already posted first suggestions/issues.
One question: On Linux you require X11. What is your strategy regarding Wayland. More and more Distributions sunsetting X11 in favor of Wayland. Is this on your or .NET/Avalonia roadmap?
Good question. At the moment Objo Studio’s Linux build uses Avalonia’s current X11 desktop backend. On Wayland desktops the expected compatibility path is XWayland, so it should still run on most modern Wayland-based distributions, but it is not native Wayland yet.
This is mainly an Avalonia roadmap item rather than a .NET runtime item. .NET does not provide the Linux desktop windowing backend; Avalonia does. Avalonia has Wayland work underway: Avalonia 12 lays the groundwork, and their current public messaging describes native Wayland as being in private preview / testing rather than something I would treat as fully general-purpose production support today.
My strategy is to keep Objo working on X11/XWayland for now, avoid taking dependencies on X11-specific behaviour where possible, and move to Avalonia’s native Wayland backend once it is generally available and has been tested against real Objo Studio workflows on GNOME/KDE Wayland. So yes, it is on the internal roadmap, but I do not want to overpromise native Wayland support before the underlying Avalonia backend is ready.
The big item missing for me is styled text. Any plans on adding something, maybe based on MarkDown?
Good suggestion. I’ll add it to the todo list 
Added to the feature tracker: Feature #83 - Objo
any plans for ios/android deploys?