UX design help

[Albert Vaca Cintora]

Hey! This looks very good :D

I left some thoughts as comments and created a task to implement your
ideas: https://invent.kde.org/network/kdeconnect-meta/-/issues/29

I do not have a lot of time at the moment, but I can probably incorporate
some changes bit by bit. And hopefully other people will too :)

Thanks a lot for putting time and thought into this, it's really
appreciated.

Albert


On Sat, Jan 17, 2026 at 11:20 PM leekleak <leekleak at proton.me> wrote:

>
> Lol, so unfortunately I wrote the email just as things got quite busy in
> life and while it'll stay that way for a while I did make a couple of
> screens.
>
> My goal was to first just take a look at all the present screens and just
> try to find as many faults in them as possible. I documented most of my
> notes in the Figma project as comments and hopefully the link I added has
> them visible.
> The visuals I don't much care about, but the concepts do include some
> pretty big conceptual changes to the navigation which I do think are quite
> an improvement and if it's unclear how it should work, please ask.
>
> Also, I made all the notes from the viewpoint of myself assuming that my
> workflow roughly matches that of an average user so if some of the things I
> note as UX issues are actually there to address a specific use case, please
> tell me about that.
>
> Final note about the comments and specifically since there's quite a lot
> of them it may bring upon an idea that I hate the current UI. Just to be
> clear I think the current UI is fine. It works. But I do think it could be
> better.
>
> You can navigate between the few screens I've concepted out in the
> expandable side bar's top left corner.
>
>
> https://www.figma.com/design/Vf30ZLTXg4Sc8KYF597jdH/KDE-Connect?m=auto&t=o68xbcnwYfd84wV1-1
> On Saturday, January 3rd, 2026 at 1:58 PM, Albert Vaca Cintora <
> albertvaka at gmail.com> wrote:
>
> 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/20260208/b0338968/attachment.htm>