Let me explain the situation.
I started transforming an "old (.Net 2.0)" Application into a webapplication.
Problem here is, that no-one here is really acquainted with the UX of a website (simple, efficient). Even though, I still have to regard that the website can be tailored to a customer needs through parameters.
I wanted to have a layout similar to Invoice Machine (as simple as possible).
- He wants a Ribbon toolbar.
Going to a supplier gives the list of supplier
- He wants to display the "Create Supplier" screen where you can use the wildcards in a certain textbox, to search for a specific Supplier and then give the list of the suppliers.
Also, I need 4 search/filter mechanisms:
- people can search per field with wildcards
- can filter the suppliers
- search a keyword through all the data of a supplier
- filter the "list Suppliers" page by the first letter of the name.
* | A | D | Z - Adam Wrincle ADD |EDIT |Delete - Damzel InDistress ADD |EDIT |Delete - Zorro ADD |EDIT |Delete
I can't seem to get through to him, that the UX of a website needs to be different than a Windows application. If he wants to bring all the logic of the windows app into a website, why build a website then? Stick to the old solution.
Am I mistaking so hard or how could I convince/show him that an online solution is something different than the offline solution.
He already "saw" online solutions of other applications to get an idea, but if I suggest something he won't listen (if it's GUI / UX related, that is).
Additional information (edit):
About the Hippo thing, i don't actually care about it. My boss does all the sales, so he is closest to the customers. Even though i read alot about webapplications and about the UX-experience and that is the difference.
The problem is, that first of all, the current Ribbon implementations that are out their, easily break and are meant for power users. The ribbon gives a user information overflow, people can search at any place (3 searches, ...) which makes the application less user-friendly.
I strongly believe in "Giving actions when they should", that means, where you can see the list of Clients, their you can click the edit/ delete / view button. For the search, I would implement one search box where you can look for everything (with an implementation like : Visual Search jQuery plugin )
Also, while a desktop implementation is easier scalable than a webapp (it doesn't need to scale), there has to be a difference. This is why I would suggest to make different roles (sales, purchase, accounting) and provide them with the tools they need (Invoicing menu, Products menu, ...).
The current desktop application can remove every single field which a client can see, based on their needs and not only that, every client has some 1000 parameters to choose from. This would create a huge overhead for every client that logs in and could give me problems on the long-term. (currently in development phase, so no caching yet)
Nothing in the application is final, I just want to know that I'm doing right by "not protesting because the boss wants it so, but I want to be sure I have a reason.
I am fairly new in the company also and I have used their desktop application and it's NOT user-friendly. Even I, with an IT background, think some things are illogical, but off course, after a while you get used to it and adapt to the situation. But that is not how it should be is it? :-)
My personal experience is that the Ribbon is good when you need a lot of functions, all the time. But 85% of the toolbar is "unusable" in a webapplication. You can create new invoice, products easier by selecting products in the menu and select new. (that is my personal opinion).
Currently, their are not a lot of users (2 and 1 client), so there are not a lot of people who can discuss the layout of it.
What I also think is unreasanable, is that some users could have only the ability to create suppliers... Which would mean the possible UX of the ribbon is also worthless :s
Good comment below, but i would like to see it adjusted to above arguments (with edit below it please), so i could get a deeper understanding what other webdevelopers think about my current situation.