Consider an angular application with many user inputs on screens A, B, and C. The C screen requires valid entries of A and B; B of A only; and A is independent. Suppose on screen B, the user enters invalid entries.
Question: Which navigation should I support for B in this case?
My current idea is to prohibit navigation to C due to data validity issues. But what about returning to B? On the one hand, there is no problem of validity and the user may wish to consult the screen A to facilitate the screen entries B. D & # 39; a on the other hand, it would complicate the management of the state of the application. Another solution is to prohibit this navigation, possibly with an option to restore the last valid entries in B.
As I lack UX experience, I would appreciate answers that help me make that compromise.
I am very new to developing system screens and have a question about what would be best from progress information. To report if the status of a process in a process list is new, running, running, canceled, or terminated with an error, would it be better to display a progress bar, icons, or something else? ?
Are there best practices for forms with HTML entry elements when they should be used on a mobile device?
On my developing web application, when you use an Android phone, the input field is often covered by the software keyboard when the field is enabled. The result is that the user has to enter the text on the fly, seeing only what has been typed after the keyboard has been ignored.
My online searches have revealed that a treatment of the problem, and this seems rather complicated (I am wary of complicated solutions: they seem fragile and tend to break in an unpredictable way).
I have some ideas, one being to always move the input field to the top of the view window when it receives the focus, the second to open a subordinate dialog with a single text element under which the keyboard should always hold. However, these also trigger my complicated solution anxiety.
With mobile phones connected to the Internet as ubiquitous as they are, I suspect that this problem of the keyboard input field has a solution. I can not find it. Help me, please. 🙁