What is correct user expectation regarding drag and move?
I have the following note taking app - https://wenote.jstock.co
I have some question, regarding user expectation regarding drag and move.
Say, you have the following card position.
[1] [2]
[3] [4]
when you move card 1 to card 4 position
Should they become (Card 1 and card 4 are being swapped. Only position of card 1 and card 4 affected.)
[4] [2]
[3] [1]
Or, the entire cards position are being shuffled (The entire list of cards are being shifted forward, to give space to the moved card. All cards position are affected.)
[2] [3]
[4] [1]
So, I'm some how confused here. What is the correct behavior when coming to drag n move for the above case?
- Card 1 and card 4 are being swapped. Only position of card 1 and card 4 affected.
- The entire list of cards are being shifted forward, to give space to the moved card. All cards position are affected.
For me, the 1st approach has a more "Direct intuitive". But, I notice that some popular note taking app like Google Keep, Zoho Notebook are using 2nd approach.
drag-n-drop
add a comment |
I have the following note taking app - https://wenote.jstock.co
I have some question, regarding user expectation regarding drag and move.
Say, you have the following card position.
[1] [2]
[3] [4]
when you move card 1 to card 4 position
Should they become (Card 1 and card 4 are being swapped. Only position of card 1 and card 4 affected.)
[4] [2]
[3] [1]
Or, the entire cards position are being shuffled (The entire list of cards are being shifted forward, to give space to the moved card. All cards position are affected.)
[2] [3]
[4] [1]
So, I'm some how confused here. What is the correct behavior when coming to drag n move for the above case?
- Card 1 and card 4 are being swapped. Only position of card 1 and card 4 affected.
- The entire list of cards are being shifted forward, to give space to the moved card. All cards position are affected.
For me, the 1st approach has a more "Direct intuitive". But, I notice that some popular note taking app like Google Keep, Zoho Notebook are using 2nd approach.
drag-n-drop
add a comment |
I have the following note taking app - https://wenote.jstock.co
I have some question, regarding user expectation regarding drag and move.
Say, you have the following card position.
[1] [2]
[3] [4]
when you move card 1 to card 4 position
Should they become (Card 1 and card 4 are being swapped. Only position of card 1 and card 4 affected.)
[4] [2]
[3] [1]
Or, the entire cards position are being shuffled (The entire list of cards are being shifted forward, to give space to the moved card. All cards position are affected.)
[2] [3]
[4] [1]
So, I'm some how confused here. What is the correct behavior when coming to drag n move for the above case?
- Card 1 and card 4 are being swapped. Only position of card 1 and card 4 affected.
- The entire list of cards are being shifted forward, to give space to the moved card. All cards position are affected.
For me, the 1st approach has a more "Direct intuitive". But, I notice that some popular note taking app like Google Keep, Zoho Notebook are using 2nd approach.
drag-n-drop
I have the following note taking app - https://wenote.jstock.co
I have some question, regarding user expectation regarding drag and move.
Say, you have the following card position.
[1] [2]
[3] [4]
when you move card 1 to card 4 position
Should they become (Card 1 and card 4 are being swapped. Only position of card 1 and card 4 affected.)
[4] [2]
[3] [1]
Or, the entire cards position are being shuffled (The entire list of cards are being shifted forward, to give space to the moved card. All cards position are affected.)
[2] [3]
[4] [1]
So, I'm some how confused here. What is the correct behavior when coming to drag n move for the above case?
- Card 1 and card 4 are being swapped. Only position of card 1 and card 4 affected.
- The entire list of cards are being shifted forward, to give space to the moved card. All cards position are affected.
For me, the 1st approach has a more "Direct intuitive". But, I notice that some popular note taking app like Google Keep, Zoho Notebook are using 2nd approach.
drag-n-drop
drag-n-drop
asked 7 hours ago
Cheok Yan Cheng
6732812
6732812
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
User expectation for drag and move can depend on the existing mental models and the kind of affordance provided in the UI.
Pattern 1:
Commonly known as Swappable. In this pattern, when a card is dragged onto another card, the other card doesn't change its position until the user releases the drag. Usually the other card is highlighted visually to indicate that a change is going to happen. This pattern of rearranging cards is less common in most applications (reason detailed out in the end).
Pattern 2:
Commonly known as Sortable. In this pattern, when a card is dragged onto another card, the other cards shift positions to give space for the change. Here the visual feedback to the user is immediate. This pattern is the most common one.
Why Sorting is the more common approach
Applications provided the feature to rearrange so that users can arrange content in a way more meaningful for them. If we take the following example of a list of cards:
[1] [2] [3] [4] [5] [6]
To get the result [2] [3] [4] [5] [6] [1]
using 1) Swapping will take a lot of combinations whereas 2) Sorting happens in a single go.
To get the result [6] [2] [3] [4] [5] [1]
using 1) Swapping will happen in a single attempt and 2) Sorting will happen in two attempts.
Using Sorting to swap items can always happen with no more than two attempts. That's why Sorting is the more efficient approach and found in most of the apps like the examples mentioned in the question.
This makes sense based on how I think I'd personally use the app. If I'm swapping stuff, "games" mostly come to mind (obviously this is just my initial thought, not a universal truth at all) - something where the "correct" order should take some thought/effort. Here, I'd expect that notes to be somewhat purposely ordered (notes created first remain closer to the top unless deliberately moved down).
– Broots Waymb
40 mins ago
add a comment |
Should be the second (shift) approach. By dragging Card 1 to Position 4, you are saying" I want Card 1 to be in Position 4". The action never states "I want Card 4 in Position 1".
Another way safe approach is using commonly known patterns: What is the most common interface using this pattern? Smartphone home screens. In both iPhone and Android, users reorganize app icons based on the 2nd approach. Therefore they would expect this same behavior to translate into other drag and drop interfaces.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "102"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fux.stackexchange.com%2fquestions%2f122895%2fwhat-is-correct-user-expectation-regarding-drag-and-move%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
User expectation for drag and move can depend on the existing mental models and the kind of affordance provided in the UI.
Pattern 1:
Commonly known as Swappable. In this pattern, when a card is dragged onto another card, the other card doesn't change its position until the user releases the drag. Usually the other card is highlighted visually to indicate that a change is going to happen. This pattern of rearranging cards is less common in most applications (reason detailed out in the end).
Pattern 2:
Commonly known as Sortable. In this pattern, when a card is dragged onto another card, the other cards shift positions to give space for the change. Here the visual feedback to the user is immediate. This pattern is the most common one.
Why Sorting is the more common approach
Applications provided the feature to rearrange so that users can arrange content in a way more meaningful for them. If we take the following example of a list of cards:
[1] [2] [3] [4] [5] [6]
To get the result [2] [3] [4] [5] [6] [1]
using 1) Swapping will take a lot of combinations whereas 2) Sorting happens in a single go.
To get the result [6] [2] [3] [4] [5] [1]
using 1) Swapping will happen in a single attempt and 2) Sorting will happen in two attempts.
Using Sorting to swap items can always happen with no more than two attempts. That's why Sorting is the more efficient approach and found in most of the apps like the examples mentioned in the question.
This makes sense based on how I think I'd personally use the app. If I'm swapping stuff, "games" mostly come to mind (obviously this is just my initial thought, not a universal truth at all) - something where the "correct" order should take some thought/effort. Here, I'd expect that notes to be somewhat purposely ordered (notes created first remain closer to the top unless deliberately moved down).
– Broots Waymb
40 mins ago
add a comment |
User expectation for drag and move can depend on the existing mental models and the kind of affordance provided in the UI.
Pattern 1:
Commonly known as Swappable. In this pattern, when a card is dragged onto another card, the other card doesn't change its position until the user releases the drag. Usually the other card is highlighted visually to indicate that a change is going to happen. This pattern of rearranging cards is less common in most applications (reason detailed out in the end).
Pattern 2:
Commonly known as Sortable. In this pattern, when a card is dragged onto another card, the other cards shift positions to give space for the change. Here the visual feedback to the user is immediate. This pattern is the most common one.
Why Sorting is the more common approach
Applications provided the feature to rearrange so that users can arrange content in a way more meaningful for them. If we take the following example of a list of cards:
[1] [2] [3] [4] [5] [6]
To get the result [2] [3] [4] [5] [6] [1]
using 1) Swapping will take a lot of combinations whereas 2) Sorting happens in a single go.
To get the result [6] [2] [3] [4] [5] [1]
using 1) Swapping will happen in a single attempt and 2) Sorting will happen in two attempts.
Using Sorting to swap items can always happen with no more than two attempts. That's why Sorting is the more efficient approach and found in most of the apps like the examples mentioned in the question.
This makes sense based on how I think I'd personally use the app. If I'm swapping stuff, "games" mostly come to mind (obviously this is just my initial thought, not a universal truth at all) - something where the "correct" order should take some thought/effort. Here, I'd expect that notes to be somewhat purposely ordered (notes created first remain closer to the top unless deliberately moved down).
– Broots Waymb
40 mins ago
add a comment |
User expectation for drag and move can depend on the existing mental models and the kind of affordance provided in the UI.
Pattern 1:
Commonly known as Swappable. In this pattern, when a card is dragged onto another card, the other card doesn't change its position until the user releases the drag. Usually the other card is highlighted visually to indicate that a change is going to happen. This pattern of rearranging cards is less common in most applications (reason detailed out in the end).
Pattern 2:
Commonly known as Sortable. In this pattern, when a card is dragged onto another card, the other cards shift positions to give space for the change. Here the visual feedback to the user is immediate. This pattern is the most common one.
Why Sorting is the more common approach
Applications provided the feature to rearrange so that users can arrange content in a way more meaningful for them. If we take the following example of a list of cards:
[1] [2] [3] [4] [5] [6]
To get the result [2] [3] [4] [5] [6] [1]
using 1) Swapping will take a lot of combinations whereas 2) Sorting happens in a single go.
To get the result [6] [2] [3] [4] [5] [1]
using 1) Swapping will happen in a single attempt and 2) Sorting will happen in two attempts.
Using Sorting to swap items can always happen with no more than two attempts. That's why Sorting is the more efficient approach and found in most of the apps like the examples mentioned in the question.
User expectation for drag and move can depend on the existing mental models and the kind of affordance provided in the UI.
Pattern 1:
Commonly known as Swappable. In this pattern, when a card is dragged onto another card, the other card doesn't change its position until the user releases the drag. Usually the other card is highlighted visually to indicate that a change is going to happen. This pattern of rearranging cards is less common in most applications (reason detailed out in the end).
Pattern 2:
Commonly known as Sortable. In this pattern, when a card is dragged onto another card, the other cards shift positions to give space for the change. Here the visual feedback to the user is immediate. This pattern is the most common one.
Why Sorting is the more common approach
Applications provided the feature to rearrange so that users can arrange content in a way more meaningful for them. If we take the following example of a list of cards:
[1] [2] [3] [4] [5] [6]
To get the result [2] [3] [4] [5] [6] [1]
using 1) Swapping will take a lot of combinations whereas 2) Sorting happens in a single go.
To get the result [6] [2] [3] [4] [5] [1]
using 1) Swapping will happen in a single attempt and 2) Sorting will happen in two attempts.
Using Sorting to swap items can always happen with no more than two attempts. That's why Sorting is the more efficient approach and found in most of the apps like the examples mentioned in the question.
answered 2 hours ago
Anvesh Dunna
10114
10114
This makes sense based on how I think I'd personally use the app. If I'm swapping stuff, "games" mostly come to mind (obviously this is just my initial thought, not a universal truth at all) - something where the "correct" order should take some thought/effort. Here, I'd expect that notes to be somewhat purposely ordered (notes created first remain closer to the top unless deliberately moved down).
– Broots Waymb
40 mins ago
add a comment |
This makes sense based on how I think I'd personally use the app. If I'm swapping stuff, "games" mostly come to mind (obviously this is just my initial thought, not a universal truth at all) - something where the "correct" order should take some thought/effort. Here, I'd expect that notes to be somewhat purposely ordered (notes created first remain closer to the top unless deliberately moved down).
– Broots Waymb
40 mins ago
This makes sense based on how I think I'd personally use the app. If I'm swapping stuff, "games" mostly come to mind (obviously this is just my initial thought, not a universal truth at all) - something where the "correct" order should take some thought/effort. Here, I'd expect that notes to be somewhat purposely ordered (notes created first remain closer to the top unless deliberately moved down).
– Broots Waymb
40 mins ago
This makes sense based on how I think I'd personally use the app. If I'm swapping stuff, "games" mostly come to mind (obviously this is just my initial thought, not a universal truth at all) - something where the "correct" order should take some thought/effort. Here, I'd expect that notes to be somewhat purposely ordered (notes created first remain closer to the top unless deliberately moved down).
– Broots Waymb
40 mins ago
add a comment |
Should be the second (shift) approach. By dragging Card 1 to Position 4, you are saying" I want Card 1 to be in Position 4". The action never states "I want Card 4 in Position 1".
Another way safe approach is using commonly known patterns: What is the most common interface using this pattern? Smartphone home screens. In both iPhone and Android, users reorganize app icons based on the 2nd approach. Therefore they would expect this same behavior to translate into other drag and drop interfaces.
add a comment |
Should be the second (shift) approach. By dragging Card 1 to Position 4, you are saying" I want Card 1 to be in Position 4". The action never states "I want Card 4 in Position 1".
Another way safe approach is using commonly known patterns: What is the most common interface using this pattern? Smartphone home screens. In both iPhone and Android, users reorganize app icons based on the 2nd approach. Therefore they would expect this same behavior to translate into other drag and drop interfaces.
add a comment |
Should be the second (shift) approach. By dragging Card 1 to Position 4, you are saying" I want Card 1 to be in Position 4". The action never states "I want Card 4 in Position 1".
Another way safe approach is using commonly known patterns: What is the most common interface using this pattern? Smartphone home screens. In both iPhone and Android, users reorganize app icons based on the 2nd approach. Therefore they would expect this same behavior to translate into other drag and drop interfaces.
Should be the second (shift) approach. By dragging Card 1 to Position 4, you are saying" I want Card 1 to be in Position 4". The action never states "I want Card 4 in Position 1".
Another way safe approach is using commonly known patterns: What is the most common interface using this pattern? Smartphone home screens. In both iPhone and Android, users reorganize app icons based on the 2nd approach. Therefore they would expect this same behavior to translate into other drag and drop interfaces.
answered 3 hours ago
Nicolas Hung
1,354412
1,354412
add a comment |
add a comment |
Thanks for contributing an answer to User Experience Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fux.stackexchange.com%2fquestions%2f122895%2fwhat-is-correct-user-expectation-regarding-drag-and-move%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown