New answers tagged layout
Smashing has the answers http://www.smashingmagazine.com/2013/09/03/flat-and-thin-are-in/ Flat UI Colors has the colors http://flatuicolors.com/
I'd second your opinions on option #2. I see several advantages There's information to act upon right away. User gets a complete sense of this overall screen area. Various UI elements are in harmony. Action components are relevant to "available information". It saves an action...and that's a lot!
One of the factors to be considered in this is performance. If it takes the system a few extra seconds to bring up the complete result set than I would steer away from it. And even if the time it takes to bring up both screens is the same, I would go with Option 1 because the blank table acts as a type of prompt for the user to enter in some sort of search ...
In your situation, I like option 2 better. I think what you are really building is a 'Practices View'. Text based search is just one feature of this 'Practices View'. It looks like you have filtering, sorting and a few other features as well. As you mention in your question, option 2 also removes the need for the user to enter a search term before they ...
Elastic Path built a couple of years ago a one page checkout e-commerce website, they even made some A/B to check the performance of both solutions, but there was no decisive winner. Maybe these blog posts from Get Elastic blog will help you to choose better solution. http://www.getelastic.com/single-page-checkout ...
Actually it is a matter of focusing on elements and the time it takes to complete that form, the decision to split the form in multiple zones or multiple pages it depends on how long the form actually is. But you need to be careful to be completely honest and clearly show the steps or estimated time to completion. Hope it helps.
@Paolo hinted at this, but I prefer the Accordion checkout process. The interface still shows the user the steps required and where they are in the conversion funnel, while keeping all the content on a single page. Accordion is probably the solution you're looking for.
LukeW and Etre ran some tests that compared a single page, multiple page, and accordion version of the same generic e-commerce checkout form (personal, shipping, and billing info). They measured standard usability and eye-tracking data for each. The results did seem to indicate that simply porting the same questions from one long web page to several web ...
Your thoughts are right, chunking a task into smaller steps brings the perception of more easy task. Also switching to a next step is a progress feedback. Still, I think you could try to combine last two steps. You could rebias (the term from behavioral economics) the unwillingness to fill long form placing the image of purchasing item right next to form. ...
I think the design in the screenshot is next to ideal. Much of the evaluation of this relates to the pros/cons of the mega-menu pattern. Allow me to elaborate: The Mega Design The good: All options are visible to the user. This promotes: Findibility - it is easier for users to find the relevant option. Learnability - users can learn quicker the ...
I see two alternative solutions to your question: 1) Keep the the current design. It's good since you expose all settings at once. Since you have so many link groups it could take more time for the user to find out the difference between for examples Services management and Product management. Amazon is currently using this approach and since they're ...
I think your page is fine because: 1) it's clear to me what my options are 2) captions under the title tells me what I'm able to do 3) icons, from what I can see, look appropriate. Alternative suggestions if you feel like it's too cluttered is the regular title and caption itself, and the user can click on it to expand the options. I think the page looks ...
It is not necessarily an ineffective layout as is. To help understand if it is effective to your users, you can run it through a series of user tests. For example -- a Card Sort, if you wanted to see what they thought category names should be, or a Reverse Card Sort if you wanted to verify your existing structure. If you break it up into a vertical ...
It's not "friendly" in the way that the design brings me coffee in the morning, no. But it is useful, since it's a "give me all my options"-page. Now this may break general convention on giving users only the options we know they will use the most. But, this is a settings page, and as such you can have a more cluttered UI, since it's faster to use once you ...
Kompare has a nice interface for comparing rows of text. It shows different colors for insertions, deletions, and changes between the two data files. If you export your data to text, you may be able to use a visual diff tool like Kompare directly instead of writing your own software.
My thought is similar to Scott and DiH, although instead of on the left inside the footer, I think the right side in the footer might be better. I only say this because I imagine viewing the copyright and date in the bottom left inside the footer and not necessarily a logo of some kind.
I really like the approach that some companies have employed, that is, adding a small label in the footer of the page. The label could be a small version of the logo, wrapped in some neatly layout-fitting background, and not outstanding too much from the general layout color palette.
I am designing a SaaS web app that sounds very similar. I have put my company's customer branding logo in the upper left, and my company's logo in the lower left in the footer. This way my customer's branding is prominently displayed for their end users, but down below there is a subtle reminder as to who is really powering this software. I think this is ...
Top 50 recent answers are included