The Stack Overflow podcast is back! Listen to an interview with our new CEO.
4

Maybe: simply just "Add folder to..."


4

I propose some improvements, based on the usability heuristics. The main issue here is the absence of clear focal point which leads to the convertion task execution. Also the task itself could be fully automated, there no man needed. Just provide FTP address and access parameters to a database. And let it run as batch process.


3

Your UX is all about "change the template". The required template may be (a) the default or (b) local file. In future say a selection from most recently used file list or a resource from a shared template library is useful. You could display this domain model this flat in the UI much as you have. But if extra capability or clarity is needed, then could ...


3

I like the term "Select parent folder", but one thing to consider would be whether or not the concept of folder creation needs to be communicated to the user. The user doesn't care that you're "creating a folder" for the project in another folder. The important high level idea is location of data. Try something like "Select location for project data." or ...


3

"Where would you like this project's folder created?" or "Location of project folder:" make it clear that I don't have to create my own sub-folder for the project, which is always a temptation for me to do. (You ever done that, or not done that when you should have? Like when extracting compressed files; I never know if I need to make a subfolder first, and ...


3

I would keep the two separate, but in the same group, because of the different location concepts the user has to grasp. Mockup example: ux.stackexchange.com is also a good example of this separation of concepts:


3

I would be inclined to keep them separate. They are different functions and the down arrow does not explain the distinct functionality very well. Also: overlap between 'upload file' and 'select file', which one could argue amount to the same thing, namely, 'selecting a file to attach with a post'. I would do this: and even then you might want to play with ...


2

I haven't seen to many apps that ask a user to select where they want a folder to be created, but the one I have seen (dare I say, Microsoft Visual Studio) has two fields everytime you create a new project: name and location. It creates a folder of the same name of the value the user enters into the "name" field at the given location. Though this doesn't ...


2

If you're using a small width then simply use the back button type functionality. Place a back button in the top left corner with a label next to it: download bmml source – Wireframes created with Balsamiq Mockups


2

Why not have 3 separate drop-areas? You seem to have horizontal real-estate to make it work. download bmml source – Wireframes created with Balsamiq Mockups It would be a challenge to make the dialog balanced, as this heavy control at the bottom will draw a lot of attention. Possible solutions: Add more contrast at the top - brighter text, brighter ...


2

Automatic uploading and deletion are consistent, no explicit submitting in both the actions. A possible solution for final delete could be as pictured: Focus user's attention on the deleted item (transition/color) Display the Undo control for some time (5 s) Delete the item and fade out the Undo control if no actions were took


2

After the multiple simultaneous file upload you could go with something similar to the approaches in the mockups below, using what you could call "cards". For mobile you have several options to manage the interaction and navigability, you could stack them vertically for users to scroll, you could add "next/previous file" actions, etc. But I guess that would ...


2

From a UX perspective, storing it as an image or in iBooks would be confusing. And users can delete iBooks, so it can't be guaranteed that they'll have it. Here's a number of alternative solutions: Cloud storage for apps such as Amazon S3 Stores data in the cloud. Would allow users to save and load with a single button press. Not free, but inexpensive. No ...


2

Rather than 'Open' and 'Save', it sounds like your need a bit of a rewording. I believe 'Source' and 'Destination' may be a better fit for the function of your app. download bmml source – Wireframes created with Balsamiq Mockups A quick wizard like this may alleviate confusion for the user. I did modify the workflow you described; I put the action in ...


1

This is a standard upload operation with extra information requested on completion.


1

I would use a single logical form (can be organized into different sections on the page) with three submit buttons: File upload picker with a submit labeled something like "Set New Avatar" A submit labeled "Remove My Avatar" Finally, a "Save Profile" button that applies to all other fields. By using different names for the buttons, the server can tell ...


1

You've pointed out two great alternatives. The first layout having mobile issues, but also if one document contained an input error; Would you submit the valid ones and leave the invalid ones or don't submit any. Personally I would vote for the last option. As file upload forms are always a two part process. Filling out form fields and finding documents on ...


1

To me, option 1 is stronger, but your default empty state still suffers from its lack of contrast. It might be mistaken for a disabled state. I suggest making the text a bit darker. Your second option gives the impression a bit too strongly that the input field is currently in focus. You should reserve border changes (color) to communicate errors and ...


1

Consistency is at the center of good UI design Unless there's a good reason to, the weight and color of the text and the thickness of the input border of a dropdown selector should be the same in all states. In your case, graying out the text in the "no value" state risks the field being mistaken for one that is disabled, and increasing the thickness of ...


1

Based on my understanding of your problem, a simple color-scheme may serve you well here. Submit in primary color to show it takes the interface forward Attach File in secondary color to show it's not required Save Draft and Cancel in secondary color as well I wouldn't worry about users accidentally touching the Attach button. Mobile operating systems ...


1

If upload is possible without Submit, then deletion should be too. You can mark the files for deletion on the server, e.g. by setting up a deletion callback that will run after 1 minute unless it will be undone... Or move the file to to-be-deleted folder on deletion and move it back on undo + make sure to garbage collect files older than 1 day or whatever is ...


1

The placement should be where the user is looking (the submit button and the form). The fact that something went wrong should be made VERY clear: the form changes color, etc... Re the wording - I'm assuming you're talking about non-techies who are asked to send PDFs (as for example) and send word docs or something else instead. The error msg itself should ...


1

Why branch to 2 different options? Just generate the "template" name automatically, and leave it up to the user if they want to immediately click save, or if they want to edit the name before saving. Workflow: User chooses folder User presented with auto generated filename in an editable field, and a save button User can edit the filename (or not) and ...


1

You might be overthinking this "problem". The functionality is simple and everything is accessible with as few clicks as possible. Only thing I would suggest is to alter the wording and say "Reset to Default" for lesser ambiguity. If you want users then to be able to (re)select their previous templates easier, you should have the field to transform to a ...


1

Pattern Tap has an example pattern of the file browser from Pixelapse. This file browser was updated recently and the Pixelapse team gave some insight into design considerations on their blog: "Browsing through projects is now much cleaner. We removed unnecessary UI chrome and slimmed down the interface to put your designs front and center. Navigating ...


1

Should the Save/Cancel buttons determine whether changes made to the file attachments are saved or discarded? Or would users expect that these changes are automatically and independently saved, since they entail file operations? It actually depends on how you will display these changes. Apply/Cancel behaviour should differentiate applied changes from ...


1

I support the answer from Myrddin Emrys. In this case an assistant or wizard-approach is a good way to lead the user through the configuration. This approach has many advantages such as: you can easily add more items to configure you can add explanation texts if some options need to be explained you can add extra options or modifiers (as example: "Same as ...


1

I would refer to the parent folder where project folders are created as the "working folder". Is there a valid use case for different project folders to be stored in different working folders? If not, or if this is a rare use case, I would have users select their working folder once as part of their user preferences and then as much as possible remove it ...


1

If the end result is for the entire project to be contained in one folder that will be maintained by your application, then why even mention that a folder is being created? That's something that the user doesn't need to know at the point you're describing, because it sounds like the project has to be contained within a folder. Therefor, I'd use the simplest ...


Only top voted, non community-wiki answers of a minimum length are eligible