The particular one that you have mentioned in the question do not have a name by definition as of now it seems.
Anyways, from a technical side it is adding JS functions to document.title. Therefore maybe we can call it Dynamic Document Title. [from today haha]
Please post your answers if it actually has a defined name. Then I shall remove my answer :)
Personally I would understand the intention regardless of which wording you choose, then again I consider myself a more technical user. So let's look at it from a non-technical point of view, which is who you are trying to reach out to here.
I think the word "browse" can be misleading as it could be interpreted as the action of looking through a collection ...
Presenting a warning about data loss is always a good idea.
Ameen, one of the most important fundamental rules of good UX design, IMHO, is to make sure that users never unintentionally lose data.
With that in mind, your users will typically navigate away from your site for two reasons:
They decide not to make the purchase, after all.
Presenting the ...
These types of notifications are usually called flashing notifications or in the cases of the favicon, Notification alert.
By extension, the case of tabs can be called Flashing Tabs
Image from Create a Flashing Notification Tab
Or Browser Tab Notifications
Using the default arrow cursor over text will suggest to many users that the text isn't even selectable, let alone editable!
Text should generally be selectable, and the I-bar is the right cursor to use. Many parts of a web interface are interactive in some way other than editing, so it's understandable that the default arrow cursor is seen a lot, but ...
I'm surprised I can't see any formal UX description or testing for these anywhere. I did see a couple of articles on creating them which referred to them as Update Notifications.
Because there is no clear indication to the user on the UI that the zoom level is greater or lower than 100%.
I noticed chrome is doing this indication by displaying a magnifying glass next to the bookmark star, but to be honest I just found this now doing this research. As a user, I could have had the same issue for months I would not know about it.
I personally use this website call statcounter.
I find it quite useful to decide with the team what viewports we should support, what breakpoint we should take into account, and what's the smallest mobile display we should focus on when building mobile experiences.
You can also filter by country, region, and other interesting parameters.
Probably best thing you can do is fix the root cause (that "technical reasons"). Your application should not be worse than other sites of the Internet.
Until you resolve your CORS issue, you can help your users to set the needed settings. You know your target browser, so make a small screenshot of its Settings page displaying what exactly you want to be ...
Good thought Ricardo.
I went through some content research for about 10 mins now,
I found something like this.
If you use Browse to choose files then there must be a upload button to be given ones the files are browsed and selected.
If you use 'Upload files' then probably there is a chance of letting the internet guest appearance user let know what it ...
I've done a similar thing for a client who wanted to release a novel app. We used a landing (or branding) page as a means of onboarding the user with minimal info and maximum feel-good content, especially when you target users through classical channels or social media campaigns. We found that a landing page prepares the user for an app that doesn't convey ...
IMO, landing pages are not just for providing info. Yes, it is a way to provide info but it can also act as an user interface in case the app takes longer to load on a poor connection. It is better to user a static page instead of completely depending on dynamically loaded pages. It is a way to increase the conversion rate.
There are many more uses but i ...
Page loading status should indicate when something is in progress.
Depending on the complexity of the process, it can take from 0.000001 to several minutes (and maybe more or less)
Often the so-called lazy loading (which allows you to gradually download data from api, without loading all at once, only dividing them into smaller parts.
At the time of the ...
Page loading is a very complex process, so the first thing to take into account is that it's not owned by any "layer" (code, viewport, browser, OS, bandwidth, internet, server...), but it pertains to all. That means many layers can show loaders (web component, webpage, browser, OS...).
By Fitts's Law, the one indicator closer to the action should be the ...
Well, I'm quite sure there's no "best practice", because it's very difficult to consider all possible scenarios (on a side note, you forgot skeletons).
First of all, you're mixing at least 2 layers: the browser(s) and the apps. You have to consider that many apps you see were built before Chrome launched this, so how would these apps guess what was coming?