UX design help

[Albert Vaca Cintora]

That would be great.

On Fri, Jan 2, 2026 at 8:34 PM leekleak <leekleak at proton.me> wrote:

> Hmm, I see.
>
> I guess I should probably make some mockups first and get some user
> feedback to ensure that the changes I have in mind look good to everyone,
> not just me.
>
>
>
> -------- Original Message --------
> On Friday, 01/02/26 at 20:54 Albert Vaca Cintora <albertvaka at gmail.com>
> wrote:
>
> We already have some views in Compose, but definitely not all. In general
> we don't just convert XML to Compose, unless using Compose gives us some
> kind of advantage or makes implementing some feature or fixing some bug
> easier. If someone wants to convert things to Compose, I'm fine with that
> as long as the result is not worse than what we have now.
>
> On Wed, Dec 31, 2025 at 12:23 PM leekleak <leekleak at proton.me> wrote:
>
>> Hey, I've been thinking of helping to improve the UX of KDE Connect.
>>
>> Unfortunately I have no experience working with XML, just Compose, so
>> I've been thinking what would be the best course of action for me.
>>
>> Technically I could just do what most designers do - make some mock-ups
>> on Figma, get some user feedback and then ask the programmers to implement
>> that. Sadly I am aware that's not quite how open source projects work :/ If
>> I don't make the changes myself, no one will.
>>
>> If all the screens were in Compose I could just implement all the changes
>> myself, however now I'd probably have to also convert them from XML
>> beforehand which would lead to very big and unwieldy PRs. Thus I'm left
>> wondering if there are plans or an undergoing effort to move to Compose and
>> if so, how's it progressing.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdeconnect/attachments/20260103/165a4e94/attachment.htm>