I have been working with diverse technologies to develop software and websites, now i would to become an expert in developing software/solutions in banking and financial industries. Is it a good idea to stick with one programming language and one frameworks to better performance ?
On a website I’m designing, users have access to a search function that lists items with potentially much content inside (they’re meant to be grammar exercises, and so multiple grammar problems can be listed in each item). The current view uses pagination (6 items per page) and looks like this:
Users should be able to enter a special mode in which they select the items to export to a file. While there could potentially be hundreds of items and multiple results pages, I want the design to be usable at no more than 40-50 items, suggesting to narrow down the search query if the result set is larger.
This leaves me with a problem: allowing users to select items for exporting from a list that doesn’t fit on a single page, because the items are so large. While there are many questions (1, 2, 3) and solutions about selecting items from a long list, those items are typically just small, simple text labels one-two words long, in which case list builders or a grid-based layout with checkboxes can be used; here, this is impractical.
The solution I thought of was to switch from using pagination to infinite scroll, and, when the user clicks the ‘export’ button, load all items from the server if the user hasn’t scrolled to the bottom yet, and then simply allow individual item selection via checkboxes (that is, a checkbox appears next to each item; if the item is to be exported, the checkbox should be checked).
- Are there any significant downsides to this approach? One problem I can see is that beyond around 10 items, there will likely be a lot of scrolling involved, because of the height of each item. How much of an issue is this?
- Is there another solution I could consider?
- I believe my solution should be usable on mobile devices as well, since it doesn’t require anything more refined than checkboxes. Are there any difficulties I’m missing?
We have an induction stove, which has a glass surface that usually only gets hot by conduction from the pan you use on it. The control panel displays H when a burner is hot but not on. My experience is that the surface never gets hot enough to be a problem wiping up spills because the wipeup cloth provides enough insulation so I ignore the warning. Presumably there is a temperature sensor in the element and a threshold for displaying the H.
I was cooking potatoes tonight and spilled some of the oil as I was flipping them. The stove duly showed H on the burners that had oil on them. I got paper towels and wiped up the oil. It didn’t burn, but it was rather hot.
It got me thinking about the choice of a warning threshold. I can see the manufacturer wanting to make it low enough that nobody could get burned at the lowest temperature it comes on. That makes it low enough that people discover it is not a serious warning and ignore it. It seems like a standard problem that should have some standard thoughts about how you choose the threshold. What are they?
I have created an App. lets say MyApp.
Now what should be url for the app?
Now name of the organisation is also same. let’s say “myapp Inc”.
So what is the best practice to display organisation info and app to put into url?
to be more clear,
should app url be like
and organisation url be like
I am faced with a challenge on the best way to help the user scan data, and make a determination about the status of their pipeline, in a flash.
What is the best way to display data for a table that has more columns than what would fit in the screen? I’m talking 30 columns.
Hoping you all can guide me with some advice.
Thanks in advance.
I have a question geared more towards UI/UX Consistency rather than Branding Consistency.
We have an ability to “Save to Lists” on our website. On our desktop site, it is a dropdown. On our mobile site, it’s a button that opens a modal (our company loves modals…).
We’re looking to add this functionality to additional pages on the site. In this instance, there are three options:
1) Have a link on both sites that says “Save items to list”. On mobile it would open a modal (consistent with other mobile page) but on desktop it would either open some type of flyout or a modal (inconsistent with other desktop page).
2) Have a dropdown on desktop (would act consistent with other desktop page) but on mobile the dropdown would be an entirely new treatment (dropdown, but pop modal only for a new list).
3) Use a dropdown on desktop (consistent with other desktop page) but a link on mobile (would be similar to other mobile page in interaction).
I hope this makes sense- tried to give a clear picture without giving an overbearing amount of information. Just trying to figure out the right path with stuff like this. Thank you!
Does anyone know of some good articles or documentation I can read for identifying the best practices to follow when designing the information architecture (forms) for allowing users to provide alternate contact information?
My objective is not gather information that is not required, such as: Do not collect phone from contacts who will not be called.
The scenarios I am looking at are:
- User does not need a secondary point of contact.
- User needs more than one secondary point of contact.
- User identifies a primary point of contact that is not themselves.
- In all scenarios the user can choose if themselves or the point of contact can receive calls or digital notifications.
The designs I have created led to a lot of yes/no questions which then showed additional form sections based on the answer. Users I have tested this with seem to enjoy this form and it captures all information they would need. however, although works well, it feels like I am reinventing the wheel or over complicating what should be a simple process.
I noticed that in many different types of products and services that offer a few different subscription plans, upgrading is easy. Downgrading, on the other hand, is a bit discreet. In most of them, you would have to contact support to downgrade or cancel your plan.
While this is a business decision, are there other negative effects if we allow users to easily downgrade to a plan? Or make canceling a plan less hidden?
And this may be uncommon – but what if a user decides to upgrade/downgrade/then upgrade again within a span of, say, an hour. In general, will that cause billing issues?
I have seen serval social media channels using Unicode to make part of their text bold or italicised on websites such as Twitter, where this sort of thing is usually not possible.
It crossed my mind that this could interfere with accessibility for screen reader users – especially since on Twitter, styled text seems to count for double the characters (e.g. “𝗛𝗲𝗹𝗹𝗼” counts as 10 characters).
Can screen readers read this sort of text as easily as regular text?
𝗛𝗲𝗹𝗹𝗼 𝘁𝗲𝘅𝘁 𝘀𝘁𝗿𝗶𝗻𝗴
𝐻𝑒𝑙𝑙𝑜 𝑡𝑒𝑥𝑡 𝑠𝑡𝑟𝑖𝑛𝑔
I have a table of this type:
So I need to make it responsive, look good on mobile devices. Several notices about table:
1) Yeah, there definitely should be some tips for every text field, it’s pretty important. “Tips” – maybe these labels in the header, or something that describes inputs (“Card number”, “Chip number”);
2) Yeah, button “Save” should be in front of every row, that’s necessary;
3) That icon on the left side has destiny too – it may be visible for some row and invisible for other rows;
Of course, the first what came to my head, was something like accordion with this look-like content:
But if there are a lot of rows (the average count should be like 20), It’s gonna be a little tough to click for each of them to collapse, then to save. So what I ask is help making this table be responsive