Friday, September 1, 2017

Should I put view and edit on the same form?


We're working on a new management console for an online service. The management console consists of about 30 forms as well as lots of reporting and various other goings-on.


My developers have moved away from my original vision for the forms, and I'm looking for the community's thoughts on their current direction. Do I need to reign them in quickly?



In my original design, everything was in "edit" mode. If you went to a page, you could read the data out of normal form widgets. If you wanted to edit anything, you just edited it and clicked save.


But the developers have now created "view" mode and made it the default on any page.


This means that when you get to a page everything is static text without the ability to edit. It's great if you're just looking for information, but if you have to edit something then it's an extra click on the "edit" button.


Are they on the right track? Should I move them back to the original vision?


If we're going with the switchable mode, where should that switch be positioned, and should it be a button, a radio group, a checkbox or an iPhone type slider?




No comments:

Post a Comment

technique - How credible is wikipedia?

I understand that this question relates more to wikipedia than it does writing but... If I was going to use wikipedia for a source for a res...