KDE Connect GitLab
OpenPublic

Mock History

Current Revision

Mock Description

I present to your attention a small redesign of the application.
The layouts are not completely ready, but the main idea is as follows:

  1. Animated on-board screens to which the user can allow access to phone functions (So far without animation)
  2. A small redesign of the activity of the remote control: an animated registration, which is called up when you press the button again and for the first time exit the screen.
  3. A small redesign of preaentation of remote activity.
  4. The activity of the player was redrawn: the playback source was placed down and selected using the "Advanced" button.
brute4s99 added a subscriber: brute4s99.
brute4s99 added subscribers: KDE Connect, VDG.
cblack added a subscriber: cblack.Thu, May 21, 4:40 AM

That looks stunning.

Although, we're migrating away from Phabricator to GitLab, so it would probably be best to open this as an issue on the KDE Connect GitLab.

It would be better if the onboarding screens were split into another issue. I am in favor of them, but neutral on the other things. It is a feature addition, while the others are feature modifications.

The remote input onboarding looks a bit wierd. The dialog style is almost making it look like a window. That content on a translucent background would look better.

Other things:

  • The arrow does not belong on "Done" on the last onboarding screen
  • "Skip" should have a lighter color if kept there. Otherwise, it could be moved to the bottom left
  • The remote input grid, at least at that high contrast level, makes me trypophobic
  • Onboarding screen 1 has too many colors
  • Onborading screen 4's touch cursor still looks like a mouse cursor
  • The bullet point symbols on the last onboarding screen are a bit weird
  • The huge amount of periods in the onboarding screen headings is a bit unnatural
nopomuk renamed this mock from KDE Connect Android Redesign to KDE Connect GitLab.Fri, May 22, 9:27 AM

This looks nice! It's probably a lot more user-friendly than just dropping the user onto a blank screen. One thing I don't like is that the onboarding screens leave out features (SMS sync, for one, but also imagine any future features which get added).

Rather than starting the user with a slideshow of things they might want to do, would it make more sense to have an in-app description at each place which the user navigates, to break up the "slideshow" and make sure only content in which they appear to be interested is presented?

It would be better if the onboarding screens were split into another issue. I am in favor of them, but neutral on the other things. It is a feature addition, while the others are feature modifications.

Agreed. Please split these into separate tasks, so that we can handle them separately

The huge amount of periods in the onboarding screen headings is a bit unnatural

Agreed, but I believe @nopomuk was copying from the website (https://kdeconnect.kde.org). I also do not especially like the style on the website, but I do like the consistency.

Although, we're migrating away from Phabricator to GitLab, so it would probably be best to open this as an issue on the KDE Connect GitLab.

Also agreed with this. Please use a gitlab task (on kdeconnect-android) to track this work since Phabricator will be retired "soon"

Actually, we have just disabled the task tracker on Gitlab because it was too easy for users to confuse with bug reports. Please keep working here until we know where to migrate :)

Rather than […] slideshow […]

The slideshow itself is very important. This is a standard UX pattern. Its purpose is to welcome the user and make them conformable enough to start using the app. These slideshows usually do this with a splash of color and fun animations. This is in contrast to the tips on each screen, which serve to educate.

[…] screens leave out features […]

Again, I don't think feature descriptions really belong on the slideshow. Mainly, this is beacuse the user will only be able to see it once and barely remember anything. Making it too long with all the features will defeat the purpose by causing users to start skipping it. Looking at Google's apps, the ideal length is no more than 4. The content should be quite general, along the lines of 3 slides with "KDE Connect syncs your phone and your computer," each slide worded slightly differently.

Its purpose is to welcome the user and make them conformable enough to start using the app. These slideshows usually do this with a splash of color and fun animations.

Sorry I'm not an illustrator. But I understood your idea about the welcome screens.

I believe that it is necessary to reduce the number of screens and simplify the description on them. Make an overview of the features of the application?
And when switching to a specific function, create an animated tooltip that the user can view at any time by clicking the "More" button?

nopomuk updated an image's (Presentation-Activity.png) description. (Show Details)


How is this screen option? Short description of the function and request for permission for access. My English is bad, so I can’t write a competent text.