Tag Info

New answers tagged

1

This is a priorities thing. There are two competing priorities. Users losing their data, and either having to retype everything, or becoming frustrated and aborting the process. This is potentially a CRITICAL ISSUE in a sales app, because "aborting the process" in this case means not paying the client. Errors creeping in due to saving unwanted data, and ...


4

I were in the same situation recently where the client didn't want to have the Save button, even tho the forms where pretty simple and were all fit into the screen with the Save and Cancel button. I managed to make a simple form with auto-save feature and conduct a test with couple of their real-world users and the conclusion was more than 30% of times ...


3

Why do you assume you're right and your customer is wrong? Either you have enough knowledge in UX field; in this case, it won't be difficult for you to find the reason why, in the particular case of the app you're working on, having a Save button is a must-have, and how to explain that in non-technical terms to the customer. For example, you may be in a ...


0

In this day and age of Google Docs auto-updating the server with data as you type, I don't think its unreasonable to have 30 textboxes being written to the server periodically (or even every time the user changes focus from one to another). You could use ajax, but my preferred solution would be to open a websocket to the server and just send the relevant ...


1

When you start discussing caching, there will be lots of opinions. No one outside your development team will be able to speak in certainties about your application. I would like to offer some guidelines to help you make your decision based on facts. How to break down your application You will have lots of different "containers" on any given web page. These ...


3

Creating a custom router page is no different than creating any other web page. You use the tools that are most appropriate for that. The real difference is that a UI for a router or other embedded device is going to be much simpler. You're not going to be using elaborate frameworks like Ruby on Rails, Angular or even jQuery. All you really need is ...


3

HTTP is a stateless protocol in that each request is an independent transaction. What came previously or what is expected to come next has no effect on an individual request. However, this doesn't mean everything you do on the internet is stateless. Sites like Amazon store states, obviously. They remember what you have done in the past and know what you ...



Top 50 recent answers are included