11
broseph
70d

Looking for a second opinion/validation.

*Me: “Perhaps this simple and concise way to ensure the user doesn’t lose their data before they leave the page that requires non-zero yet minimal input from the user. (Read: ya gotta push a save/submit button)”

*Everyone else: Let’s pretend to read the user’s mind and perform relatively complicated functions behind the scenes, of which the user will most likely be unaware, that will add an undetermined amount of complexity to the development because we think it’s “where things are going,” by saving the value of a certain HTML element as it loses focus.

Edit: this is an exclusively-internally used app.

Comments
  • 1
    broseph, you know I'm on your side, man 👊
  • 2
    I guess telling someone "click on [save] before leaving" is way easier than explaining them their data is somehow saved in the background, especially to non-tech people (who probably can't even imagine what "their data" is)
  • 1
    It's actually common to have a submit button.

    On the other hand, systems like shops save the shopping cart so that it's available when the browser is restarted.

    The easiest way for saving goes via cookies, provided that changing between client devices isn't a common part of the workflow.
  • 3
    Save on losing focus sounds nice but it would require that you have a minimum number of well defined user flows so that the user can keep some expectations.
    Where does the user go from the current page? If there's a next button, it's safe to assume that next means the user wants to save and move on. It depends on your overall interaction sequence.
    Whatever you do, keep it consistent and test it with some first time users before pushing the app on everyone. 😉
    In my experience usability tests are often skipped for internal applications.

    Out of curiosity, is your team led by a Steve Jobs wannabe? "I don't want any clicks, any buttons."
Your Job Suck?
Get a Better Job
Add Comment