The mobile version of Lagrange was in a bit of a cul-de-sac over the summer as I was struggling with my chosen approach of trying to “simply” reorganize the desktop dialogs into a different layout.

It wasn’t simple and it didn’t produce good results.

Now that I’ve thrown that piece of code in the trash, I’m making swift progress again and things are more straightforward.

It’s important to abandon the fruitless paths and to try something else, despite sunk costs.

@jk There is a Gemini client called »Ariane 4« in early development. Does it make sense to build another one from the Lagrange codebase (or a new one)?

I like Lagrange very much and use it every day. Many thanks for this nice peace of software.

Are there any ways to support you in further development?

@mado Ariane is great, but it's only for Android. Lagrange's objective is to be as platform-agnostic as possible.

Gemini is so bare-bones that there is plenty of room for clientside differentiation in content presentation, UI design, customization/extensibility, and accessibility features.

@mado It's great if people write narrow-focus clients using specific GUI toolkits, target OS's, and audiences in mind. That way the apps' UX can be optimized better, unlike Lagrange that by nature has to be generalist and middle-of-the-road.

Lagrange is meant for all traditional desktop/mobile GUI platforms, but it lacks common accessibility features due to its custom, dependency-free UI. Platform-specific frameworks sometimes support these built-in since they can afford to be tied down.


> Are there any ways to support you in further development?

The thing I need the most is time, but that's difficult to give someone. ☺️ If you'd like to donate money for code-signing fees etc., the Lagrange GitHub project page has a PayPal link.

Sign in to participate in the conversation

skyjake's personal Mastodon instance