What are the most recommended colors for the UI of a mobile app that is used under sunlight?

To use the app, users have to increase the brightness of the screen and this causes the battery to run out faster and still the best experience is not perceived.

It is an app that users use daily for 6 hours under sunlight taking meter readings located in the customers’ house.

They make a tour in the street visiting around 500 houses.

Is there a recommended size for search boxes?

Do users change their search patterns if the search is shorter? Do users search less if the search box is too large?

The only article I’d found is a 2009 Smashing Magazine article:

The [Nielsen] study found that the average search box is 18-characters wide. The data showed that 27% of queries were too long to fit into it. Extending the box to 27 characters would accommodate 90% of queries. Remember, you can set widths using ems, not just pixels and points. One em is the width and height of one “m” character (using whatever font size a website is set to). So, use this measure to scale the width of the text input field to 27-characters wide.

In general, search boxes are better too wide than too short, so that users can quickly review, verify and submit the query. This guideline is very simple but unfortunately too often dismissed or ignored. Some padding in the input field can also improve the design and user experience.

Which design pattern is recommended for multiple components in web application?

The application is in PHP using Laravel Framework, so I have multiple blade components with his own Javascript code, but must of the times a component requires something that is declared, created or filled in another component in the same father template.

I have the JS objects, following OOP, but the blade components are not objects like those.

I’m looking for a good and clean solution.


Recommended research articles or best practices for UI techniques for encouraging users to explore more functions of a complex application?

I can highly recommend the recent article by Cockburn et al. “Supporting Novice to Expert Transitions in User Interfaces” (ACM Computing Surveys, Vol. 47, No. 2, Article 31, Publication date: November 2014) but the research it reviews is almost exclusively about point-and-click interfaces that are trying to make small improvements in user performance.

What if you are trying to get users to be motivated to learn a new set of functionality in the app that they didn’t even know they would want?

As well as general research in this area, I’d also like to know if there is research or best practice about when to explicitly encourage the user to try something new.

When they open the app (like a Tip of the Day?) or just as they quit? If so, every time they open or quit the app, or spaced out, or randomly?

Azure Functions with EF Core Recommended

This is a questions more about if I should more than if I can. I’ve got an existing Azure App Service which started off as a simple rest api that managed communications between mobile apps and multiple instances of an on-premise multi-tenanted ERP system. Probably due to a bit of bad design it’s kind of morphed over recent times to include file hosting, marketing websites and an unrelated web app.

So, my plan is to to pull this api out of the current app service into it’s own to keep maintenance etc a little more streamlined. I was looking at rather than using another App Service, Azure Functions. However, my current api uses a SQL DB (Again hosted in Azure) and EF to store some settings and transactional data.

Now the question is, considering Azure Functions are supposed to be stateless is it considered “Best Practice” to have Functions accessing SQL data via EF (or at all). I’ve seen lots of info telling me how, but no one really seems to say if you should. Or am I just over thinking the “Stateless” thing?

Recommended patterns for help cues/hints/documentation

I’ve been scouring the web, but haven’t been finding much with regards to different options on how to present help text and/or documentation. Obviously, there’s an established pattern of just having a Help or FAQ menu item and then linking to some giant document, but I’m looking for something a little more context-sensitive and/or integrated within the content (but non-obtrusive, of course).

Can anyone point me to some good examples of alternatives to the traditional Help menu item? I’ve got some ideas of my own but would like some inspiration or validation.

which is most recommended word-cloud for angular 7

i am looking for the most suitable word-cloud for angular 7

i need 2 thinks which i can split into 2: 1. genetaring the right array for the word cloud from a string of data – this point wants me to go to the best perfomance option, as i have a lot of data. 2. displaying a pretty wordcloud based on the array of data and words count.

i tried to search over offered solutions and was very confused. i have several questions regarding:

-i saw lot of people recommending jason davies code https://www.jasondavies.com/wordcloud/ it looks very pretty for me, and i thought of using it, but would like to know pros and cons, and if it is suitable for angular 7 in addition couln’t figure out where to download it from, and all the implemintation data. is there some good documentation?

-i also saw there is a use of angular4-word-cloud but i could not find a demo of it, is it very different from jason davies codes?

-in addition i saw a use of wordcloud2, i saw it is java script based, is there a good tutorial for this ? how hard is it for use comparing the options above?

i would like to know of any other recommended word clouds and any documentation about it

What is the recommended time before a reset password link expires?

I’m working on a financially leaning site and was curious — is there a standard amount of time to wait before expiring a reset password link once a user has forgotten his/hers and requested to reset it?

On the other hand, if there is no “standard” as such, how might a UX practitioner go about figuring out what would be a sensible and acceptable period for their use case?

What’s a recommended way to design a Multi-Brand website

I am building a shopping website that have requirement like support Multiple Brands. Ie, a common landing site and different domains for different sites (Like : Gap.com ). I looking for a recommended way on

  1. Does it is best to use a Separate Site for each Brand ?
  2. Is it best to keep a single database for all products or need to keep separate database for each brand?
  3. Is there any existing open-source CMS Frameworks available to manage this kind of solutions (Like wordpress multi site)?