While thinking of design, i looked on biggest “competitors” on mobile OS market – Android and iOS. Mainly i am taking design ideas from Android, since i am thinking it has good proportion between usability and functionality, while i am studying/following KDE Human Interface Guidelines, https://community.kde.org/KDE_Visual_Design_Group/HIG and as recommended i am using Kirigami 2 framework, which implement most of HIG rules by itself.
These are quick mock-ups:
Main list view with available connections and password dialog:
Expanded actions for some network:
Using Kirigami.SwipeListItem, contextual actions of specific network like connect, disconnect, show details and delete will be hidden “behind”.
Contextual actions of network manager – custom connection, hotspot, list connection history where you can change network settings
Difference between desktop and smartphone approach is mainly that phone is mean as lightweight version of OS, with design simplified for easier and quicker use. That also means stripping some (or lets a lot) of functionality, which is present in desktop and targeted for advanced users.
Comparison between current desktop KCM and my proposal
I am mostly stripping functionality which does not have meaning in phones – phone has just one user, one network device or it will be possible to set just one IP address manually (on desktop you can have set to choose from multiple addresses ).