The main goal of the project is not to build a end user browser product, but an embeddable web runtime. As such the current egui-based, android and OHOS browsers in the repo are just meant to showcase the runtime capabilities.

The Verso project is building a Servo-based browser (https://github.com/versotile-org/verso) but I don't know if they have plans for a mobile version.

About running on mobile linux, I have a branch athttps://github.com/webbeef/servo/tree/linux-arm64 that I run once in while on my Pinephone Pro. Feel free to test it!

To be clear, I was not speaking about a dedicated "mobile version". I was more speaking about things like menus that do overflow the screen space on small screens or to speak about a current issue: when more tabs are created than screen space is available (on FHD-monitor I can open 16 tabs until it becomes a problem, on mobile probably only 2). It should just be considered while creating the desktop version.

However, I thought in "some" years, when Servo becomes feature-rich, stable and fast the project will do more work on its browser and I thought Verso is just an alternative like Fractal chat to Element of the Matrix-network project. Seems I misunderstood it, sorry.

I already found your branch and want to test it at some later point, thanks.

To be clear, I was not speaking about a dedicated "mobile version". I was more speaking about things like menus that do overflow the screen space on small screens or to speak about a current issue: when more tabs are created than screen space is available (on FHD-monitor I can open 16 tabs until it becomes a problem, on mobile probably only 2). It should just be considered while creating the desktop version.

Historically there was enough differences both in UX and OS integration to not use a common codebase for desktop and mobile browsers. I'm not convinced that mobile linux makes a difference for the UX side of the equation.

The answer is just to share knowledge, not to convince you to do something with Servo and its browser.

Historically browsers looked likethis. But times are changing. Nobody would create such an UI full of useless buttons these days. And so in the last few years the Linux mobile UX changed in the way I described above. SeeGitlab GNOME for example (they speak about this change from desktop app to convergence app). Purism created with Libhandy the starting point for this change/movement.

This UX change is useful for anything that can be used by a simple UI as browsers these days have. On my own Firefox config I removed some unnecessary buttons, added the title menu bar (my personal preference) and everything else are just size adjustments. And that would already be enough to make the browser usable with not much additional afford (still has some bugs, because no native support for this). A more shiny browser could alsooptionally add a mobile UI (URL-bar to the bottom etc). In fact, there are people who like a classic mobile view, but also some like me who want the true desktop experience even on mobile devices. The main idea which most people share: using the same application on desktop and on mobile devices is something good. Less work to maintain, similar UX on different devices and more.

And of cause there are applications that still will be created explicit for mobile or for desktop (like GIMP). It's more or less a question about the usefulness for the one or other one method. The best case however is, if people can choose what they want: feature rich convergence software or light weight mobile app. The use case can be different.

I think kumo browser was experimenting with servo iirc, if they wind up sticking with it, it would be a good show case of a mobile browser