1. It meets or exceeds the standards set by competing and popular products. It is consistent in its navigation and nomenclature, in a way that is familiar to users.
2. It is visually up to date, appealing, and intuitive. The user always knows exactly what he can or cannot do with the application, and what comes next.
3. The application uses accepted navigational norms – such as a search box in the upper right corner and familiar “submit / next / continue” buttons. And it does so consistently across the entire application.
4. The application is tested for usability as it is created, so there isn’t that nasty, terrible surprise at the end where your users reject the entire application because “it doesn’t do what I expected it to, the way I expected it to do it.”
5. Is designed to be secure, and security is baked into all stages of development. Security is one of those “meets the standard” aspects of application development. We take this so seriously that we have even developed the security tools that other developers use.
6. The application is developed with market realities and revenue goals in mind. This is truly rare among application developers, and one of the main reason that clients come to us for development. There are so many decisions to be made that will impact the business aspect of the application, including:
7. What is the price point?
8. What is the business goal for this application?
9. What do users expect to get at that price point?
10. Are there features you absolutely must have, and features you could leave out for later – or not include at all?
11. What features/functions would really separate you from the pack, and are they worth the additional development effort?
12. What is the best development platform for this application – in terms of longevity, support, maintenance, speed of development, and cost?
13. How many different devices must this application work on, and how do you make sure that the application works well on all required devices?
14. How many users or transactions must this application support? How can we make sure it will scale?
15. What is the history of this application? Are we starting from scratch, or building on prior history?
16. How much support can the company give the development effort? How many people are involved, and what are their roles?
17. What is the target budget?