I believe when the user clicks on the button save and the second block is empty, don't need validation because it's not a priority for the user the fields empty. If he clicks on the button accidentally he can finish the task and if he needed the second block and forgot, he can edit this information later.
Save button on the bottom. The flow should follow natural behaviour. The user will click on the save button after filling the form and then naturally the action should be there, after form. But if you not confident about this, please add both, on the top and on the bottom.
You could create 2 stages of verification:
If any data was filled on ...
Potential disadvantages are numerous:
Application should have the access to phone camera (or it cannot work)
People are not always OK with sending their pictures
Users need to have necessary conditions for making photo (good light, absence of other people or things not for photo)
Some countries like Germany are very nervous about people's privacy (it ...
One approach is to have the default filter set to the most common search, and have users be explicit about the starting dimension.
In the sketch below, I'm suggesting some friction up front aiming for more clarity about the dependent relationships. You could make them explicitly select the starting search:
By country (which then shows only the Orgs)
100+ items is a long list, and I think it's important to make categorizing fast, and also to give the user a feeling of progress through the list. With that in mind, I would set up each item with a single tap/click control for A or B. Once selected, items would move to the relevant (maybe collapsed) list elsewhere in the page. If the user wants to change ...
As long as you provide confirmation on-page as soon as they have submitted the form, then you don't need to send the email. Typically, confirmation emails may infer that a ticket of some sort has been opened. From this email, the user can see a ticket # and can respond.
I would argue that it's very hard to know how your audience will respond to your (somewhat involved) setup process.
That being said, one of the versions you describe (the kind where each step in the process is on a single view, in sequential order), will give you feedback as to where users are struggling – either through in-person user testing, or via ...
If there's a concept of default product, have that selected (and moved to the top). Or, just have the first product selected. I don't see any viable reason for not having anything selected.
Clicking on the product shouldn't enable/disable as it isn't clear what the checkbox does. I would refrain from using the exact same pattern as the browser because ...
There is a rationale (below) for having, and showing, an image that is personal to, or at least recognizable by, the user. However, while a "selfie" will fall into this category, I can't see a reason for only allowing a selfie to be used.
One technique to guard against fake (phishing) sites is for a website to show something (e.g. an image) during the ...
In-page feedback and thank you message is absolutely necessary.
Regarding a possible email, rather than a thank you note, you could let the user decide if they want to receive a copy of their message at their email address. It's both a confirmation that their message has been sent and a copy for their own record that they might find useful (depending on the ...
A follow up email may be considered spam, but as others have said, you should provide feedback as to the state of the action within your site.
Some suggestions for the feedback:
The feedback should inform the user what happened (e.g. an email was sent to us, and probably thank them for their time/effort)
The feedback should set the users expectation (e.g. ...
As far as you showing an alert with a thank you message on submit of form no need to send an email.
1- Email gets ignored
2- I personally don't like to receive an email for a thank you message
3- you need to develop a mail template which can increase time and cost.
You can send a reply email based on the query submitted by the client and in that ...