Paths Short or LongIs my suspicion correct, that QR codes will be a short-lived standard with little...
Does rpcpassword need to be non-obvious in bitcoind?
(How long) Should I indulge my new co-workers?
What is the origin of the “clerics can create water” trope?
Is it worth the risk to apply to REUs? How likely am I to be accepted?
With a 500GB SSD and a 250GB SSD is it possible to mirror a 250GB partition on the 500GB with the 250GB SSD using ZFS?
All numbers in a 5x5 Minesweeper grid
How can I create folders in folders in terminal
Does Mage Hand give away the caster's position?
Is the name of an interval between two notes unique and absolute?
Is there an in-universe reason Harry says this or is this simply a Rowling mistake?
Lumens specs when buying a flashlight/torch. Why maglite has only 680lm but cheap ones have 900,000?
Minimum number of lines to draw 111 squares
What's the word for a student who doesn't register but goes to a class anyway?
Can't make parabola without including the tip
Why do things cool down?
Why would a fighter use the afterburner and air brakes at the same time?
Is it safe to put a microwave in a walk-in closet?
Why can't we use uninitialized local variable to access static content of its type?
Can one guy with a duplicator trigger a nuclear apocalypse?
Paradox regarding phase transitions in relativistic systems
Account creation and log-in system
What's the purpose of autocorrelation?
Should the pagination be reset when changing the order?
Can I separate garlic into cloves for storage?
Paths Short or Long
Is my suspicion correct, that QR codes will be a short-lived standard with little effect?Are long query strings in URLs bad for usability?8 short tutorial videos: all embedded in one page vs separate pages with title link?Displaying domain name or URL that is long or contains many wordsDo long domain names really affect user experience?Displaying information on minimalistic long panelsUser-friendly short URL aliases with words or emojisHow to layout / structure a page with a long sidebar but a short content section?URL paths: to change or not to changeDocumentation: one long page or several short pages
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I am working through a problem with path names. The previous version of a site used short codes for url paths. Coming into this for a new project and the short code based paths, while deterministic, seem user-unfriendly to me.
Example current
as1/u2/m4/s7
Example longer
assume-1/unify-2/mobile-4/sturgeon-7
The words are changed so client info isn't released. The content is linear and so numbers have meaning in context.
My question is this. Have there been any UX studies done to show whether or not this makes any difference. SEO is no consideration as all this content is behind a paywall and is internally indexed/searchable.
information-architecture urls
New contributor
add a comment
|
I am working through a problem with path names. The previous version of a site used short codes for url paths. Coming into this for a new project and the short code based paths, while deterministic, seem user-unfriendly to me.
Example current
as1/u2/m4/s7
Example longer
assume-1/unify-2/mobile-4/sturgeon-7
The words are changed so client info isn't released. The content is linear and so numbers have meaning in context.
My question is this. Have there been any UX studies done to show whether or not this makes any difference. SEO is no consideration as all this content is behind a paywall and is internally indexed/searchable.
information-architecture urls
New contributor
add a comment
|
I am working through a problem with path names. The previous version of a site used short codes for url paths. Coming into this for a new project and the short code based paths, while deterministic, seem user-unfriendly to me.
Example current
as1/u2/m4/s7
Example longer
assume-1/unify-2/mobile-4/sturgeon-7
The words are changed so client info isn't released. The content is linear and so numbers have meaning in context.
My question is this. Have there been any UX studies done to show whether or not this makes any difference. SEO is no consideration as all this content is behind a paywall and is internally indexed/searchable.
information-architecture urls
New contributor
I am working through a problem with path names. The previous version of a site used short codes for url paths. Coming into this for a new project and the short code based paths, while deterministic, seem user-unfriendly to me.
Example current
as1/u2/m4/s7
Example longer
assume-1/unify-2/mobile-4/sturgeon-7
The words are changed so client info isn't released. The content is linear and so numbers have meaning in context.
My question is this. Have there been any UX studies done to show whether or not this makes any difference. SEO is no consideration as all this content is behind a paywall and is internally indexed/searchable.
information-architecture urls
information-architecture urls
New contributor
New contributor
New contributor
asked 9 hours ago
Frank Robert AndersonFrank Robert Anderson
232 bronze badges
232 bronze badges
New contributor
New contributor
add a comment
|
add a comment
|
2 Answers
2
active
oldest
votes
Jabob Nielsen in his article URL as UI from 1999 highlights the importance of human-friendly and hackable URLs. Updates from 2005 and 2007 mentioning eye-tracking studies suggesting that people pay attention to URL.
Another article by NNGroup, Navigation: You Are Here states that:
Well-chosen, human-readable web addresses are important to sharing, credibility, recognition, and recall. A page’s web address can be used to reveal some of the information architecture to help contextualize the content.
I'm not sure how often your users will see full URL instead of link text, but I do not think there are any benefits to making links less meaningful.
For me personally, readable links are important, I assert more trust to links with information scent. Besides, then I navigate any interlinked documentation or wiki, I often mouse over the link to view URL in the bottom left corner to see if I have already visited it or have it open. In this scenario, human readable URL in much proffered as well.
add a comment
|
As a contrast to @JurjisKovzels answer, I'll say that the web-browsing public is much more used to unreadable strings of nonsense as URLs now than they have been at any point in the history of the internet. Just have a look at any link from a CDN, such as facebook's ubiquitous fbcdn or at any Google search result URL. It's all long strings of just too much to handle from a user's perspective, but, in the context of webapps, we're kind of used to it. Go to your bank's website, even, a trust-critical application, and log in. You'll find the URL is a bunch of flags and ?= options that aren't particularly human-interpretable, even if some of then are dictionary words.
Basically, in general, on a general website, URL clarity is still important, especially if you expect people to share or bookmark your pages. But in the context of an app's internal pages, URLs aren't as important. As the NNG article linked in Jurjis' answer indicates, URLs can help with You-Are-Here, but on the other hand, do you really want people trying to URL-navigate themselves to the middle of some app workflow you didn't design to be started in the middle?
Probably not.
Please cite some sources. Users rarely do what we want them to do. If they do it regardless then we should design those pages. The content that I talking about is hierarchical and linear in nature. It isn't an email app or a search page.
– Frank Robert Anderson
6 mins ago
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/4.0/"u003ecc by-sa 4.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
});
}
});
Frank Robert Anderson is a new contributor. Be nice, and check out our Code of Conduct.
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%2f129086%2fpaths-short-or-long%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
Jabob Nielsen in his article URL as UI from 1999 highlights the importance of human-friendly and hackable URLs. Updates from 2005 and 2007 mentioning eye-tracking studies suggesting that people pay attention to URL.
Another article by NNGroup, Navigation: You Are Here states that:
Well-chosen, human-readable web addresses are important to sharing, credibility, recognition, and recall. A page’s web address can be used to reveal some of the information architecture to help contextualize the content.
I'm not sure how often your users will see full URL instead of link text, but I do not think there are any benefits to making links less meaningful.
For me personally, readable links are important, I assert more trust to links with information scent. Besides, then I navigate any interlinked documentation or wiki, I often mouse over the link to view URL in the bottom left corner to see if I have already visited it or have it open. In this scenario, human readable URL in much proffered as well.
add a comment
|
Jabob Nielsen in his article URL as UI from 1999 highlights the importance of human-friendly and hackable URLs. Updates from 2005 and 2007 mentioning eye-tracking studies suggesting that people pay attention to URL.
Another article by NNGroup, Navigation: You Are Here states that:
Well-chosen, human-readable web addresses are important to sharing, credibility, recognition, and recall. A page’s web address can be used to reveal some of the information architecture to help contextualize the content.
I'm not sure how often your users will see full URL instead of link text, but I do not think there are any benefits to making links less meaningful.
For me personally, readable links are important, I assert more trust to links with information scent. Besides, then I navigate any interlinked documentation or wiki, I often mouse over the link to view URL in the bottom left corner to see if I have already visited it or have it open. In this scenario, human readable URL in much proffered as well.
add a comment
|
Jabob Nielsen in his article URL as UI from 1999 highlights the importance of human-friendly and hackable URLs. Updates from 2005 and 2007 mentioning eye-tracking studies suggesting that people pay attention to URL.
Another article by NNGroup, Navigation: You Are Here states that:
Well-chosen, human-readable web addresses are important to sharing, credibility, recognition, and recall. A page’s web address can be used to reveal some of the information architecture to help contextualize the content.
I'm not sure how often your users will see full URL instead of link text, but I do not think there are any benefits to making links less meaningful.
For me personally, readable links are important, I assert more trust to links with information scent. Besides, then I navigate any interlinked documentation or wiki, I often mouse over the link to view URL in the bottom left corner to see if I have already visited it or have it open. In this scenario, human readable URL in much proffered as well.
Jabob Nielsen in his article URL as UI from 1999 highlights the importance of human-friendly and hackable URLs. Updates from 2005 and 2007 mentioning eye-tracking studies suggesting that people pay attention to URL.
Another article by NNGroup, Navigation: You Are Here states that:
Well-chosen, human-readable web addresses are important to sharing, credibility, recognition, and recall. A page’s web address can be used to reveal some of the information architecture to help contextualize the content.
I'm not sure how often your users will see full URL instead of link text, but I do not think there are any benefits to making links less meaningful.
For me personally, readable links are important, I assert more trust to links with information scent. Besides, then I navigate any interlinked documentation or wiki, I often mouse over the link to view URL in the bottom left corner to see if I have already visited it or have it open. In this scenario, human readable URL in much proffered as well.
edited 7 hours ago
answered 7 hours ago
Jurijs KovzelsJurijs Kovzels
9481 gold badge6 silver badges18 bronze badges
9481 gold badge6 silver badges18 bronze badges
add a comment
|
add a comment
|
As a contrast to @JurjisKovzels answer, I'll say that the web-browsing public is much more used to unreadable strings of nonsense as URLs now than they have been at any point in the history of the internet. Just have a look at any link from a CDN, such as facebook's ubiquitous fbcdn or at any Google search result URL. It's all long strings of just too much to handle from a user's perspective, but, in the context of webapps, we're kind of used to it. Go to your bank's website, even, a trust-critical application, and log in. You'll find the URL is a bunch of flags and ?= options that aren't particularly human-interpretable, even if some of then are dictionary words.
Basically, in general, on a general website, URL clarity is still important, especially if you expect people to share or bookmark your pages. But in the context of an app's internal pages, URLs aren't as important. As the NNG article linked in Jurjis' answer indicates, URLs can help with You-Are-Here, but on the other hand, do you really want people trying to URL-navigate themselves to the middle of some app workflow you didn't design to be started in the middle?
Probably not.
Please cite some sources. Users rarely do what we want them to do. If they do it regardless then we should design those pages. The content that I talking about is hierarchical and linear in nature. It isn't an email app or a search page.
– Frank Robert Anderson
6 mins ago
add a comment
|
As a contrast to @JurjisKovzels answer, I'll say that the web-browsing public is much more used to unreadable strings of nonsense as URLs now than they have been at any point in the history of the internet. Just have a look at any link from a CDN, such as facebook's ubiquitous fbcdn or at any Google search result URL. It's all long strings of just too much to handle from a user's perspective, but, in the context of webapps, we're kind of used to it. Go to your bank's website, even, a trust-critical application, and log in. You'll find the URL is a bunch of flags and ?= options that aren't particularly human-interpretable, even if some of then are dictionary words.
Basically, in general, on a general website, URL clarity is still important, especially if you expect people to share or bookmark your pages. But in the context of an app's internal pages, URLs aren't as important. As the NNG article linked in Jurjis' answer indicates, URLs can help with You-Are-Here, but on the other hand, do you really want people trying to URL-navigate themselves to the middle of some app workflow you didn't design to be started in the middle?
Probably not.
Please cite some sources. Users rarely do what we want them to do. If they do it regardless then we should design those pages. The content that I talking about is hierarchical and linear in nature. It isn't an email app or a search page.
– Frank Robert Anderson
6 mins ago
add a comment
|
As a contrast to @JurjisKovzels answer, I'll say that the web-browsing public is much more used to unreadable strings of nonsense as URLs now than they have been at any point in the history of the internet. Just have a look at any link from a CDN, such as facebook's ubiquitous fbcdn or at any Google search result URL. It's all long strings of just too much to handle from a user's perspective, but, in the context of webapps, we're kind of used to it. Go to your bank's website, even, a trust-critical application, and log in. You'll find the URL is a bunch of flags and ?= options that aren't particularly human-interpretable, even if some of then are dictionary words.
Basically, in general, on a general website, URL clarity is still important, especially if you expect people to share or bookmark your pages. But in the context of an app's internal pages, URLs aren't as important. As the NNG article linked in Jurjis' answer indicates, URLs can help with You-Are-Here, but on the other hand, do you really want people trying to URL-navigate themselves to the middle of some app workflow you didn't design to be started in the middle?
Probably not.
As a contrast to @JurjisKovzels answer, I'll say that the web-browsing public is much more used to unreadable strings of nonsense as URLs now than they have been at any point in the history of the internet. Just have a look at any link from a CDN, such as facebook's ubiquitous fbcdn or at any Google search result URL. It's all long strings of just too much to handle from a user's perspective, but, in the context of webapps, we're kind of used to it. Go to your bank's website, even, a trust-critical application, and log in. You'll find the URL is a bunch of flags and ?= options that aren't particularly human-interpretable, even if some of then are dictionary words.
Basically, in general, on a general website, URL clarity is still important, especially if you expect people to share or bookmark your pages. But in the context of an app's internal pages, URLs aren't as important. As the NNG article linked in Jurjis' answer indicates, URLs can help with You-Are-Here, but on the other hand, do you really want people trying to URL-navigate themselves to the middle of some app workflow you didn't design to be started in the middle?
Probably not.
answered 2 hours ago
sintaxsintax
1,1241 gold badge2 silver badges13 bronze badges
1,1241 gold badge2 silver badges13 bronze badges
Please cite some sources. Users rarely do what we want them to do. If they do it regardless then we should design those pages. The content that I talking about is hierarchical and linear in nature. It isn't an email app or a search page.
– Frank Robert Anderson
6 mins ago
add a comment
|
Please cite some sources. Users rarely do what we want them to do. If they do it regardless then we should design those pages. The content that I talking about is hierarchical and linear in nature. It isn't an email app or a search page.
– Frank Robert Anderson
6 mins ago
Please cite some sources. Users rarely do what we want them to do. If they do it regardless then we should design those pages. The content that I talking about is hierarchical and linear in nature. It isn't an email app or a search page.
– Frank Robert Anderson
6 mins ago
Please cite some sources. Users rarely do what we want them to do. If they do it regardless then we should design those pages. The content that I talking about is hierarchical and linear in nature. It isn't an email app or a search page.
– Frank Robert Anderson
6 mins ago
add a comment
|
Frank Robert Anderson is a new contributor. Be nice, and check out our Code of Conduct.
Frank Robert Anderson is a new contributor. Be nice, and check out our Code of Conduct.
Frank Robert Anderson is a new contributor. Be nice, and check out our Code of Conduct.
Frank Robert Anderson is a new contributor. Be nice, and check out our Code of Conduct.
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.
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%2f129086%2fpaths-short-or-long%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