You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
16"The time it takes to get the content ready(download/decode/buffer) is not short, but not long enough to make the user navigate away. I would say around between 8~15 seconds." - on YOUR device.user11153– user111532014-08-05 13:43:50 +00:00Commented Aug 5, 2014 at 13:43
-
3A quote from the Windows UX Design Principles: "Don't provide unnecessary details. Generally users don't care about the details of the operation being performed. For example, users of a setup program don't care about the specific file being copied or that system components are being registered because they have no expectations about these details. Typically, a well-labeled progress bar alone provides sufficient information, so provide additional progress information only if users can do something with it."and31415– and314152014-08-07 15:04:36 +00:00Commented Aug 7, 2014 at 15:04
-
16@and31415 It's of no great surprise to me that the Windows design principles can be basically summed up as 'assume the user is an idiot'. It makes it an incredibly frustrating system to use if you're not an idiot.user52840– user528402014-08-08 05:28:47 +00:00Commented Aug 8, 2014 at 5:28
-
2@MilesRout Interesting proof point on opinion vs fact. I find Windows easier to use than the common alternatives which I find enormously frustrating when doing some of the heavy lifting I do, especially OSX.Simon– Simon2014-08-08 07:58:04 +00:00Commented Aug 8, 2014 at 7:58
-
3By the way, I'm fairly sure that both the description and the progress bar for launching InstallShield (then one you displayed a screenshot of) are pure BS, for no purpose other than to amuse the user.user541686– user5416862014-08-08 08:15:48 +00:00Commented Aug 8, 2014 at 8:15
|
Show 10 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. website-design), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you